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}@${node}=${rc}. Eg. memcached_monitor_20000@bart.exam‐
61 ple.com=7 For more information on OCF return codes, refer to:
62 http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pace‐
63 maker_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}@${node}=${rc}. Eg. memcached_stop_0@bart.example.com=1
71
72 The transition will normally stop at the failed action.
73 Save the result with --save-output and re-run with --xml-file
74
75 -t, --set-datetime=value
76 Set date/time
77
78 -q, --quorum=value
79 Specify a value for quorum
80
81 -w, --watchdog=value
82 Assume a watchdog device is active
83
84 -g, --ticket-grant=value
85 Grant a ticket
86
87 -r, --ticket-revoke=value
88 Revoke a ticket
89
90 -b, --ticket-standby=value
91 Make a ticket standby
92
93 -e, --ticket-activate=value
94 Activate a ticket
95
96 Output Options:
97 -I, --save-input=value
98 Save the input configuration to the named file
99
100 -O, --save-output=value
101 Save the output configuration to the named file
102
103 -G, --save-graph=value
104 Save the transition graph (XML format) to the named file
105
106 -D, --save-dotfile=value
107 Save the transition graph (DOT format) to the named file
108
109 -a, --all-actions
110 Display all possible actions in the DOT graph - even ones not
111 part of the transition
112
113 Data Source:
114 -L, --live-check
115 Connect to the CIB and use the current contents as input
116
117 -x, --xml-file=value
118 Retrieve XML from the named file
119
120 -p, --xml-pipe
121 Retrieve XML from stdin
122
124 Pretend a recurring monitor action found memcached stopped on node
125 fred.example.com and, during recovery, that the memcached stop action
126 failed
127
128 # crm_simulate -LS --op-inject memcached:0_moni‐
129 tor_20000@bart.example.com=7 --op-fail mem‐
130 cached:0_stop_0@fred.example.com=1 --save-output /tmp/mem‐
131 cached-test.xml
132
133 Now see what the reaction to the stop failure would be
134
135 # crm_simulate -S --xml-file /tmp/memcached-test.xml
136
138 Written by Andrew Beekhof
139
141 Report bugs to users@clusterlabs.org
142
143
144
145Pacemaker 1.1.19-8.el7_6.4 January 2019 PACEMAKER(8)