SysTutorials

Linux Manual Pages › Section 8

crm_simulate(8)

Pacemaker – Part of the Pacemaker cluster resource manager

Synopsis

crm_simulate datasource operation [additional options]

Description

crm_simulate – Tool for simulating the cluster’s response to events

Options

-?, –help
This text
-$, –version
Version information
-Q, –quiet
Display only essentialoutput
-V, –verbose
Increase debug output

Operations:

-R, –run
Determine the cluster’s response to the given configuration and status
-S, –simulate Simulate the transition’s execution and display the resulting cluster status
-X, –in-place Simulate the transition’s execution and store the result back to the input file
-s, –show-scores
Show allocation scores
-U, –show-utilization Show utilization information
-P, –profile=value
Run all tests in the named directory to create profiling data
-j, –pending
Display pending state if ‘record-pending’ is enabled

Synthetic Cluster Events:

-u, –node-up=value
Bring a node online
-d, –node-down=value
Take a node offline
-f, –node-fail=value
Mark a node as failed
-i, –op-inject=value
Generate a failure for the cluster to react to in the simulation
Value is of the form ${resource}_${task}_${interval}@${node}=${rc}. Eg. memcached_monitor_20000 [at] bart.example.com=7 For more information on OCF return codes, refer to: http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-ocf-return-codes.html
-F, –op-fail=value
If the specified task occurs during the simulation, have it fail with return code ${rc}
Value is of the form ${resource}_${task}_${interval}@${node}=${rc}. Eg. memcached_stop_0 [at] bart.example.com=1
The transition will normally stop at the failed action.
Save the result with –save-output and re-run with –xml-file
-t, –set-datetime=value
Set date/time
-q, –quorum=value
Specify a value for quorum
-w, –watchdog=value
Assume a watchdog device is active
-g, –ticket-grant=value
Grant a ticket
-r, –ticket-revoke=value
Revoke a ticket
-b, –ticket-standby=value
Make a ticket standby
-e, –ticket-activate=value
Activate a ticket

Output Options:

-I, –save-input=value
Save the input configuration to the named file
-O, –save-output=value
Save the output configuration to the named file
-G, –save-graph=value
Save the transition graph (XML format) to the named file
-D, –save-dotfile=value
Save the transition graph (DOT format) to the named file
-a, –all-actions
Display all possible actions in the DOT graph – even ones not part of the transition

Data Source:

-L, –live-check
Connect to the CIB and use the current contents as input
-x, –xml-file=value
Retrieve XML from the named file
-p, –xml-pipe
Retrieve XML from stdin

Examples

Pretend a recurring monitor action found memcached stopped on node fred.example.com and, during recovery, that the memcached stop action failed

# crm_simulate -LS –op-inject memcached:0_monitor_20000 [at] bart.example.com=7 –op-fail memcached:0_stop_0 [at] fred.example.com=1 –save-output /tmp/memcached-test.xml

Now see what the reaction to the stop failure would be

# crm_simulate -S –xml-file /tmp/memcached-test.xml

Author

Written by Andrew Beekhof

Reporting Bugs

Report bugs to pacemaker [at] oss.clusterlabs.org