Scroll to navigation

PACEMAKER(8) System Administration Utilities PACEMAKER(8)

NAME

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
Display only essentialoutput
Increase debug output

Operations:

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

Show allocation scores

-U, --show-utilization Show utilization information

Run all tests in the named directory to create profiling data

Synthetic Cluster Events:

Bring a node online
Take a node offline
Mark a node as failed
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@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
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@bart.example.com=1
Save the result with --save-output and re-run with --xml-file
Set date/time
Specify a value for quorum
Assume a watchdog device is active
Grant a ticket
Revoke a ticket
Make a ticket standby
Activate a ticket

Output Options:

Save the input configuration to the named file
Save the output configuration to the named file
Save the transition graph (XML format) to the named file
Save the transition graph (DOT format) to the named file
Display all possible actions in the DOT graph - even ones not part of the transition

Data Source:

Connect to the CIB and use the current contents as input
Retrieve XML from the named file
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@bart.example.com=7 --op-fail memcached:0_stop_0@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 users@clusterlabs.org

June 2018 Pacemaker 1.1.18-3.el6