Bug 1388219 - [RFE] Add a "display-order" metadata to control the ordering of display in "pcs status"
Summary: [RFE] Add a "display-order" metadata to control the ordering of display in "p...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcs
Version: 8.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1411264 1682129
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-24 18:52 UTC by Renaud Marigny
Modified: 2022-12-30 23:21 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
: 1411264 (view as bug list)
Environment:
Last Closed:
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3554901 0 None None None 2018-08-07 17:09:18 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.