Pacemaker 2.0 Tool Changes
Pacemaker 2.0 changed the command-line tools as follows.
|Legacy usage (no longer supported)||Current usage|
|-i/--debug_inc and -d/--debug_dec||n/a (were ignored)|
|--node-uuid/-u||n/a (was ignored)|
|-S/--snmp-traps, -C/--snmp-community||Built-in SNMP no longer supported, use alerts instead|
|-T/--mail-to, -F/--mail-from, -H/--mail-host, -P/--mail-prefix||Built-in ESMTP no longer supported, use alerts instead|
|-c/--cman, -A/--openais, -e/--epoch, -H/--heartbeat||n/a (legacy stacks no longer supported)|
|-A/--openais, -H/--heartbeat||n/a (legacy stacks no longer supported)|
|--pending/-j||n/a (now always in effect)|
|tool has been completely removed (was only built with heartbeat)|
|--ais, --hae, --heartbeat, --lha||n/a (legacy stacks no longer supported)|
|HBDummy test resource agent||n/a (heartbeat-class agents no longer supported)|
|cluster-init (in "extra", not installed by default)|
|--cman, -h/--heartbeat, -o/--openais, -p/--plugin||n/a (legacy stacks no longer supported)|
|fence agent has been completely removed (was only used with CMAN)|
|pacemaker plugin for corosync 1|
|completely removed (was only used with corosync 1)|
Reliable exit codes
Prior to 2.0, Pacemaker daemons and command-line tools returned an unreliable mishmash of exit status codes, sometimes including negative numbers (which would get bitwise-remapped to the 0-255 range) and/or C library errno codes (which could potentially vary across OSes).
Now, everything returns a well-defined set of reliable exit status codes. These codes can be viewed using the existing crm_error tool with the --exit parameter. For example:
crm_error --exit --listto list all possible exit statuses
crm_error --exit 124to show a textual description of what exit status 124 means
- Output from -X/--as-xml will no longer show expected_votes
- This now always goes through the cluster to obtain information, rather than talk to the cluster layer directly. As a result, the -n/--name, -q/--quorum, and -i/--cluster-id options now work when run on Pacemaker Remote nodes, even if the node name in the cluster is different from local hostname. The -C/--corosync option is deprecated, since the cluster layer interface is no longer needed.
- Data from the heartbeat package is no longer collected
- The --cleanup option now cleans up only resources with failures; the previous behavior of cleaning up all resources can still be achieved with the --refresh option.