Roger Zhou
Roger Zhou
You may want to add bsc#1176441 into the bug list for tracking too.
@aleksei-burlakov, BTW, I do want to clarify the general purpose of the use case PED-139 is to maintain the full fledged crmsh functionalities. With that, we should call out to...
Yeah, I like `crm configure show related:*foo* related:*bar*`. But, it stays within "the resource name" makes the usage limited. Example, I may want to show all resources based on ocf:hearbeat:Filesystem....
Agree, this Use case is valid to improve User Experience. From the design wise, the code could be generic and flexible to avoid maintenance burden if any. We could add...
From the conceptual level, I do read it as a cusmetic issue. I found another cusmetic one as below very recently. No sure if the root cause is same, at...
From my impression, I prefer to change the commit title to make the use case it a little more clear, something like, From `Dev: parse: Populate some default operations when...
POC in https://github.com/ClusterLabs/crmsh/pull/1009 is trying to extend it to non-root, eg. sudoer, hacluster. Currently, "root" is required for the full-fledged functionalities of a) `crm report` b) `crm cluster init/join` The...
Thanks for the idea of `crm corosync status cpg`
> Do we have pacemaker 3.0 package available now? If not, how to test this for now? FYI, This aims for PED-8016 pacemaker 2.1.8 as well, which will be released...
Hmm, I see what you mean. However, DLM isn't versatile enough for the pacemaker/corosync cluster stack. Out of my head, I lack the suitable user interface to integrate it.