1PACEMAKER(8) System Administration Utilities PACEMAKER(8)
2
3
4
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
18 -$, --version
19 Version information
20
21 -Q, --quiet
22 Display only essentialoutput
23
24 -V, --verbose
25 Increase debug output
26
27 Operations:
28 -R, --run
29 Determine the cluster's response to the given configuration and
30 status
31
32 -S, --simulate Simulate the transition's execution and display the
33 resulting cluster status
34
35 -X, --in-place Simulate the transition's execution and store the result
36 back to the input file
37
38 -s, --show-scores
39 Show allocation scores
40
41 -U, --show-utilization Show utilization information
42
43 -P, --profile=value
44 Run all tests in the named directory to create profiling data
45
46 Synthetic Cluster Events:
47 -u, --node-up=value
48 Bring a node online
49
50 -d, --node-down=value
51 Take a node offline
52
53 -f, --node-fail=value
54 Mark a node as failed
55
56 -i, --op-inject=value
57 Generate a failure for the cluster to react to in the simulation
58
59 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: http://www.clusterlabs.org/doc/en-US/Pace‐
63 maker/1.1/html/Pacemaker_Explained/s-ocf-return-codes.html
64
65 -F, --op-fail=value
66 If the specified task occurs during the simulation, have it fail
67 with return code ${rc}
68
69 Value is of the form ${resource}_${task}_${inter‐
70 val_in_ms}@${node}=${rc}. Eg. memcached_stop_0@bart.exam‐
71 ple.com=1
72
73 The transition will normally stop at the failed action.
74 Save the result with --save-output and re-run with --xml-file
75
76 -t, --set-datetime=value
77 Set date/time
78
79 -q, --quorum=value
80 Specify a value for quorum
81
82 -w, --watchdog=value
83 Assume a watchdog device is active
84
85 -g, --ticket-grant=value
86 Grant a ticket
87
88 -r, --ticket-revoke=value
89 Revoke a ticket
90
91 -b, --ticket-standby=value
92 Make a ticket standby
93
94 -e, --ticket-activate=value
95 Activate a ticket
96
97 Output Options:
98 -I, --save-input=value
99 Save the input configuration to the named file
100
101 -O, --save-output=value
102 Save the output configuration to the named file
103
104 -G, --save-graph=value
105 Save the transition graph (XML format) to the named file
106
107 -D, --save-dotfile=value
108 Save the transition graph (DOT format) to the named file
109
110 -a, --all-actions
111 Display all possible actions in the DOT graph - even ones not
112 part of the transition
113
114 Data Source:
115 -L, --live-check
116 Connect to the CIB mamager and use the current CIB contents as
117 input
118
119 -x, --xml-file=value
120 Retrieve XML from the named file
121
122 -p, --xml-pipe
123 Retrieve XML from stdin
124
126 Pretend a recurring monitor action found memcached stopped on node
127 fred.example.com and, during recovery, that the memcached stop action
128 failed
129
130 # crm_simulate -LS --op-inject memcached:0_moni‐
131 tor_20000@bart.example.com=7 --op-fail mem‐
132 cached:0_stop_0@fred.example.com=1 --save-output /tmp/mem‐
133 cached-test.xml
134
135 Now see what the reaction to the stop failure would be
136
137 # crm_simulate -S --xml-file /tmp/memcached-test.xml
138
140 Written by Andrew Beekhof
141
143 Report bugs to users@clusterlabs.org
144
145
146
147Pacemaker 2.0.0-5.fc29 April 2019 PACEMAKER(8)