Bug 1388219

Summary: [RFE] Add a "display-order" metadata to control the ordering of display in "pcs status"
Product: Red Hat Enterprise Linux 8 Reporter: Renaud Marigny <rmarigny>
Component: pcsAssignee: Tomas Jelinek <tojeline>
Status: NEW --- QA Contact: cluster-qe <cluster-qe>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: cluster-maint, idevat, igreen, kgaillot, michele, mlisik, ngore, omular, rmarigny, tojeline
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 1411264 (view as bug list) Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1411264, 1682129    
Bug Blocks:    

Comment 5 Ken Gaillot 2016-11-01 16:01:11 UTC 
Most of the implementation would likely need to be on the pacemaker end.

There is nothing like this currently, although these crm_mon options are somewhat related to ordering:

* --group-by-node shows the resources running on each node

* --brief summarizes resources by agent/node

If I understand the request correctly, a new "display-order" resource meta-data attribute would be a number, and crm_mon would show any resource(s) with display-order=1, followed by any resource(s) with display-order=2, etc.

Alternatively, maybe crm_mon could have an --order-by option with the possible values config (= default = current behavior), name, or agent.

I'm not sure at this point how intrusive or difficult either would be to implement. There might be a significant overhead from copying the resource list and sorting it.
Comment 8 Tomas Jelinek 2017-03-16 10:51:03 UTC 
The pacemaker feature we depend on got postponed to 7.5.