Closed kskmori closed 12 years ago
"Instead I would suggest to modify for crm_mon and sort them only when it is displayed."
That sounds like a very good idea :)
Migration summary should be sorted too:
============
Last updated: Tue Aug 21 20:03:51 2012
Stack: Heartbeat
Current DC: 11-sl6 (51266a31-10ba-4fdb-92b7-a33b3e7ceefd) - partition with quorum
Version: 1.0.12-607b226
2 Nodes configured, unknown expected votes
0 Resources configured.
============
Online: [ 10-sl6 11-sl6 ]
Node Attributes:
* Node 10-sl6:
* Node 11-sl6:
Migration summary:
* Node 11-sl6:
* Node 10-sl6:
Andrew,
I've pushed two additional changes for this, and for the sake of printing clone resources with sorted nodes I have added 'pe_print_sort' option for clone_print(). Are you comfortable with this change?
f9e5006 Low: tools: crm_mon display nodes in sorted order (clone resources) 657c51d Low: tools: crm_mon display nodes in sorted order (Migration summary)
Sure, both patches look good :-)
Thank you. I confirmed it in environment of RHEL6.2-x86_64.
Thanks for your comfirmation!
I would like to backport this too, but the patch will result a big behavior change; regression.sh fails with 23 dot files differences (listed below) at least. It seems that it affects to the default location of nodes when scores are equal. For clones tests indexes such as :0 and :1 are exchanged. For some tests a resource would be migrated. I would hesitate to change like those in 1.0.
Instead I would suggest to modify for crm_mon and sort them only when it is displayed. The reported issue is only related for operators and we do not have to change the internal behavior.
How do you think about it?
PEND, 7be61e6 ,2012-07-30,"Low: PE: Sort nodes alphabetically so that they display consistently in CLI tools (update regression test)" PEND, af407b9 ,2012-07-30,"Low: PE: Sort nodes alphabetically so that they display consistently in CLI tools"