Hi,
21.01.2015 12:50, Kristoffer Grönlund wrote:
Hello,
renayama19661...@ybb.ne.jp writes:
Hi All,
We confirmed a function of crmsh by the next combination.
* corosync-2.3.4
* pacemaker-Pacemaker-1.1.12
* crmsh-2.1.0
By new crmsh, does "options sort-elements no" not work?
Is there the option which does not change order elsewhere?
I second for this issue as I was just hit by it - pacemaker handles them
in the order the appear in the CIB
(http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/_which_resource_is_preferred_to_be_chosen_to_get_assigned_first.html
- "the first runnable resource listed in cib gets allocated first").
Thus it may unnecessarily allocate all globally-unique clone instances
to just one node if other node already has much more resources allocated
due to constraints.
More, I would say that due to how clone/ms resources are presented in
the XML, it would be nice not to put them after all primitive resources
in the crmsh if sorting is disabled.
I would suggest:
...
primitive p1 ...
primitive p2 ...
clone cl-p2 p2 ...
primitive p3 ...
...
instead of the current
...
primitive p1 ...
primitive p2 ...
primitive p3 ...
clone cl-p2 p2 ...
...
It would also be nice to have a way to change existing resource order in
the 'crmsh configure edit/upload'.
Best,
Vladislav
It is possible that there is a bug in crmsh, I will investigate.
Could you file an issue for this problem at
http://github.com/crmsh/crmsh/issues ? This would help me track the
problem.
Thank you!
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
