1PACEMAKER(8)            System Administration Utilities           PACEMAKER(8)
2
3
4

NAME

6       Pacemaker - Part of the Pacemaker cluster resource manager
7

SYNOPSIS

9       crm_simulate <data source> <operation> [options]
10

DESCRIPTION

12       crm_simulate - simulate a Pacemaker cluster's response to events
13

OPTIONS

15   Help Options:
16       -h, --help
17              Show help options
18
19       --help-all
20              Show all help options
21
22       --help-output
23              Show output help
24
25       --help-operations
26              Show operations options
27
28       --help-synthetic
29              Show synthetic cluster event options
30
31       --help-artifact
32              Show artifact options
33
34       --help-source
35              Show data source options
36
37   Output Options:
38       --output-as=FORMAT
39              Specify output format as one of: text (default), xml
40
41       --output-to=DEST
42              Specify file name for output (or "-" for stdout)
43
44       --text-fancy
45              Use more highly formatted output (requires --output-as=text)
46
47   Operations:
48       -R, --run
49              Process  the  supplied  input  and show what actions the cluster
50              will take in response
51
52       -S, --simulate
53              Like --run, but also simulate taking those actions and show  the
54              resulting new status
55
56       -X, --in-place
57              Like  --simulate,  but  also store the results back to the input
58              file
59
60       -A, --show-attrs
61              Show node attributes
62
63       -c, --show-failcounts
64              Show resource fail counts
65
66       -s, --show-scores
67              Show allocation scores
68
69       -U, --show-utilization
70              Show utilization information
71
72       -P, --profile=DIR
73              Process all the XML files in the named directory to create  pro‐
74              filing data
75
76       -N, --repeat=N
77              With --profile, repeat each test N times and print timings
78
79   Synthetic Cluster Events:
80       -u, --node-up=NODE
81              Simulate bringing a node online
82
83       -d, --node-down=NODE
84              Simulate taking a node offline
85
86       -f, --node-fail=NODE
87              Simulate a node failing
88
89       -i, --op-inject=OPSPEC
90              Generate  a  failure  for the cluster to react to in the simula‐
91              tion.  See `Operation Specification` help for more information.
92
93       -F, --op-fail=OPSPEC
94              If the specified task occurs during the simulation, have it fail
95              with  return  code  ${rc}.  The transition will normally stop at
96              the failed action.   Save  the  result  with  --save-output  and
97              re-run  with --xml-file.  See `Operation Specification` help for
98              more information.
99
100       -t, --set-datetime=DATETIME
101              Set      date/time       (ISO       8601       format,       see
102              https://en.wikipedia.org/wiki/ISO_8601)
103
104       -q, --quorum=QUORUM
105              Set to '1' (or 'true') to indicate cluster has quorum
106
107       -w, --watchdog=DEVICE
108              Set  to '1' (or 'true') to indicate cluster has an active watch‐
109              dog device
110
111       -g, --ticket-grant=TICKET
112              Simulate granting a ticket
113
114       -r, --ticket-revoke=TICKET
115              Simulate revoking a ticket
116
117       -b, --ticket-standby=TICKET
118              Simulate making a ticket standby
119
120       -e, --ticket-activate=TICKET
121              Simulate activating a ticket
122
123   Artifact Options:
124       -I, --save-input=FILE
125              Save the input configuration to the named file
126
127       -O, --save-output=FILE
128              Save the output configuration to the named file
129
130       -G, --save-graph=FILE
131              Save the transition graph (XML format) to the named file
132
133       -D, --save-dotfile=FILE
134              Save the transition graph (DOT format) to the named file
135
136       -a, --all-actions
137              Display all possible actions in DOT graph (even if not  part  of
138              transition)
139
140   Data Source:
141       -L, --live-check
142              Connect to CIB manager and use the current CIB contents as input
143
144       -x, --xml-file=FILE
145              Retrieve XML from the named file
146
147       -p, --xml-pipe
148              Retrieve XML from stdin
149
150   Application Options:
151       -$, --version
152              Display software version and exit
153
154       -V, --verbose
155              Increase debug output (may be specified multiple times)
156
157       -Q, --quiet
158              Display only essential output
159

OPERATION SPECIFICATION

161       The   OPSPEC   in  any  command  line  option  is  of  the  form  ${re‐
162       source}_${task}_${interval_in_ms}@${node}=${rc}        (memcached_moni‐
163       tor_20000@bart.example.com=7,  for  example).   ${rc}  is an OCF return
164       code.   For  more  information  on  these  return   codes,   refer   to
165       https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html/Pace‐
166       maker_Administration/s-ocf-return-codes.html
167

EXAMPLES

169       Pretend a recurring monitor action  found  memcached  stopped  on  node
170       fred.example.com  and,  during recovery, that the memcached stop action
171       failed:
172
173              crm_simulate -LS --op-inject  memcached:0_monitor_20000@bart.ex‐
174              ample.com=7    --op-fail   memcached:0_stop_0@fred.example.com=1
175              --save-output /tmp/memcached-test.xml
176
177       Now see what the reaction to the stop failed would be:
178
179              crm_simulate -S --xml-file /tmp/memcached-test.xml
180

AUTHOR

182       Written by Andrew Beekhof
183
184
185
186Pacemaker 2.1.0-0.2.rc1.fc34       May 2021                       PACEMAKER(8)