1PACEMAKER(8) System Administration Utilities PACEMAKER(8)
2
6 Pacemaker - Part of the Pacemaker cluster resource manager
7
9 crm_simulate datasource operation [additional options]
10
12 crm_simulate - Tool for simulating the cluster's response to events
13
15 -?, --help
16 This text
17 -$, --version
19 Version information
20 -Q, --quiet
22 Display only essentialoutput
23 -V, --verbose
25 Increase debug output
26 Operations:
28 -R, --run
29 Determine the cluster's response to the given configuration and
30 status
31 -S, --simulate Simulate the transition's execution and display the
33 resulting cluster status
34 -X, --in-place Simulate the transition's execution and store the result
36 back to the input file
37 -s, --show-scores
39 Show allocation scores
40 -U, --show-utilization Show utilization information
42 -P, --profile=value
44 Run all tests in the named directory to create profiling data
45 Synthetic Cluster Events:
47 -u, --node-up=value
48 Bring a node online
49 -d, --node-down=value
51 Take a node offline
52 -f, --node-fail=value
54 Mark a node as failed
55 -i, --op-inject=value
57 Generate a failure for the cluster to react to in the simulation
58 Value is of the form ${resource}_${task}_${inter‐
60 val_in_ms}@${node}=${rc}. Eg. memcached_moni‐
61 tor_20000@bart.example.com=7 For more information on OCF return
62 codes, refer to: https://clusterlabs.org/pace‐
63 maker/doc/en-US/Pacemaker/2.0/html/Pacemaker_Administra‐
64 tion/ch07.html#s-ocf-return-codes
65 -F, --op-fail=value
67 If the specified task occurs during the simulation, have it fail
68 with return code ${rc}
69 Value is of the form ${resource}_${task}_${inter‐
71 val_in_ms}@${node}=${rc}. Eg. memcached_stop_0@bart.exam‐
72 ple.com=1
73 The transition will normally stop at the failed action.
75 Save the result with --save-output and re-run with --xml-file
76 -t, --set-datetime=value
78 Set date/time (ISO 8601 format, see
79 https://en.wikipedia.org/wiki/ISO_8601)
80 -q, --quorum=value
82 Specify a value for quorum
83 -w, --watchdog=value
85 Assume a watchdog device is active
86 -g, --ticket-grant=value
88 Grant a ticket
89 -r, --ticket-revoke=value
91 Revoke a ticket
92 -b, --ticket-standby=value
94 Make a ticket standby
95 -e, --ticket-activate=value
97 Activate a ticket
98 Output Options:
100 -I, --save-input=value
101 Save the input configuration to the named file
102 -O, --save-output=value
104 Save the output configuration to the named file
105 -G, --save-graph=value
107 Save the transition graph (XML format) to the named file
108 -D, --save-dotfile=value
110 Save the transition graph (DOT format) to the named file
111 -a, --all-actions
113 Display all possible actions in the DOT graph - even ones not
114 part of the transition
115 Data Source:
117 -L, --live-check
118 Connect to the CIB mamager and use the current CIB contents as
119 input
120 -x, --xml-file=value
122 Retrieve XML from the named file
123 -p, --xml-pipe
125 Retrieve XML from stdin
126
128 Pretend a recurring monitor action found memcached stopped on node
129 fred.example.com and, during recovery, that the memcached stop action
130 failed
131 # crm_simulate -LS --op-inject memcached:0_moni‐
133 tor_20000@bart.example.com=7 --op-fail mem‐
134 cached:0_stop_0@fred.example.com=1 --save-output /tmp/mem‐
135 cached-test.xml
136 Now see what the reaction to the stop failure would be
138 # crm_simulate -S --xml-file /tmp/memcached-test.xml
140
142 Written by Andrew Beekhof
143
145 Report bugs to users@clusterlabs.org
146Pacemaker 2.0.1-2.fc30 April 2019 PACEMAKER(8)