1PACEMAKER(8) System Administration Utilities PACEMAKER(8)
2
6 Pacemaker - Part of the Pacemaker cluster resource manager
7
9 crm_simulate <data source> <operation> [options]
10
12 crm_simulate - simulate a Pacemaker cluster's response to events
13
15 Help Options:
16 -h, --help
17 Show help options
18 --help-all
20 Show all help options
21 --help-operations
23 Show operations options
24 --help-synthetic
26 Show synthetic cluster event options
27 --help-output
29 Show output options
30 --help-source
32 Show data source options
33 Operations:
35 -R, --run
36 Determine cluster's response to the given configuration and sta‐
37 tus
38 -S, --simulate
40 Simulate transition's execution and display resulting cluster
41 status
42 -X, --in-place
44 Simulate transition's execution and store result back to input
45 file
46 -s, --show-scores
48 Show allocation scores
49 -U, --show-utilization
51 Show utilization information
52 -P, --profile
54 Run all tests in the named directory to create profiling data
55 -N, --repeat=N
57 With --profile, repeat each test N times and print timings
58 -j, --pending
60 Display pending state if 'record-pending' is enabled
61 Synthetic Cluster Events:
63 -u, --node-up=NODE
64 Bring a node online
65 -d, --node-down=NODE
67 Take a node offline
68 -f, --node-fail=NODE
70 Mark a node as failed
71 -i, --op-inject=OPSPEC
73 Generate a failure for the cluster to react to in the simula‐
74 tion. See `Operation Specification` help for more information.
75 -F, --op-fail=OPSPEC
77 If the specified task occurs during the simulation, have it fail
78 with return code ${rc}. The transition will normally stop at
79 the failed action. Save the result with --save-output and
80 re-run with --xml-file. See `Operation Specification` help for
81 more information.
82 -t, --set-datetime=DATETIME
84 Set date/time (ISO 8601 format, see
85 https://en.wikipedia.org/wiki/ISO_8601)
86 -q, --quorum=QUORUM
88 Specify a value for quorum
89 -w, --watchdog=DEVICE
91 Assume a watchdog device is active
92 -g, --ticket-grant=TICKET
94 Grant a ticket
95 -r, --ticket-revoke=TICKET
97 Revoke a ticket
98 -b, --ticket-standby=TICKET
100 Make a ticket standby
101 -e, --ticket-activate=TICKET
103 Activate a ticket
104 Output Options:
106 -I, --save-input=FILE
107 Save the input configuration to the named file
108 -O, --save-output=FILE
110 Save the output configuration to the named file
111 -G, --save-graph=FILE
113 Save the transition graph (XML format) to the named file
114 -D, --save-dotfile=FILE
116 Save the transition graph (DOT format) to the named file
117 -a, --all-actions
119 Display all possible actions in DOT graph (even if not part of
120 transition)
121 Data Source:
123 -L, --live-check
124 Connect to CIB manager and use the current CIB contents as input
125 -x, --xml-file=FILE
127 Retrieve XML from the named file
128 -p, --xml-pipe
130 Retrieve XML from stdin
131 Application Options:
133 -$, --version
134 Display software version and exit
135 -V, --verbose
137 Increase debug output (may be specified multiple times)
138 -Q, --quiet
140 Display only essential output
141
143 The OPSPEC in any command line option is of the form
144 ${resource}_${task}_${interval_in_ms}@${node}=${rc} memcached_moni‐
145 tor_20000@bart.example.com=7, for example). ${rc} is an OCF return
146 code. For more information on these return codes, refer to
147 https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html/Pace‐
148 maker_Administration/s-ocf-return-codes.html
149
151 Pretend a recurring monitor action found memcached stopped on node
152 fred.example.com and, during recovery, that the memcached stop action
153 failed:
154 crm_simulate -LS --op-inject memcached:0_moni‐
156 tor_20000@bart.example.com=7 --op-fail mem‐
157 cached:0_stop_0@fred.example.com=1 --save-output /tmp/mem‐
158 cached-test.xml
159 Now see what the reaction to the stop failed would be:
161 crm_simulate -S --xml-file /tmp/memcached-test.xml
163
165 Written by Andrew Beekhof
166Pacemaker 2.0.5-10.fc33 December 2020 PACEMAKER(8)