Hello everybody
This is my first post on this mailing list and I am only using Pacemaker since fall 2015 ... please be gentle :-) and I will do the same.
Our cluster is using multiple resource agents that update various node attributes (via RAs like sysinfo, healthcpu, etc.) in the form of #health.* and we rely on the mechanism enabled via the property node-health-strategy=migrate-on-red to trigger a resource migrations.
In Pacemaker version 1.1.12 crm_mon -A or -XA would still display these #health.* attributes, but not since we have moved up to 1.1.14 and I am not sure why this needed to be changed :
root@ys0-resiliency-test-1:~# crm node status-attr pg1 show \#health-cpu
scope=status name=#health-cpu value=green
root@ys0-resiliency-test-1:~# crm_mon -XrRAf1 | grep -i '#health' ; echo $?
1
This seems to be due to this part of the crm_mon.c code:
/* Never display node attributes whose name starts with one of these prefixes */
#define FILTER_STR { "shutdown", "terminate", "standby", "fail-count", \
"last-failure", "probe_complete", "#", NULL }
I would like to know if anybody is sharing my opinions on that:
1. From an operations point of view it would be easier to get crm_mon to include #health.* in the general output or at least in the XML output via crm_mon -XA, so that I can get a comprehensive status view in one shot.
2. Because the node attributes list can be extensive and clutters up the output it would make sense to allow a user-defined filter for node attributes in general
Regards,
Martin Schlegel
_______________________________________________ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
