-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathccs.8
267 lines (264 loc) · 9.9 KB
/
ccs.8
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
.TH CCS 8
.SH NAME
ccs \- Cluster Configuration System
.SH SYNOPSIS
.B ccs [-h hostname | -f filename] [options]
.SH DESCRIPTION
.B ccs
allows an administrator to create, modify and view a cluster configuration
file on a remote node through ricci or on a local file system. Using
.B ccs
an administrator can also start and stop the cluster services on one or
all of the nodes in a configured cluster.
.SH OPTIONS
Generally all command lines must specify either a hostname or filename to act
upon.
.SS "MAIN OPTIONS"
.IP --help
Display this help and exit
.IP "-h, --host host"
Cluster node to perform actions on
.IP "--usealt"
If primary node name is unavailable, attempt to connect to ricci on the alt interface (only works from a cluster member)
.IP "-f, --file file"
File to perform actions on
.IP "-i, --ignore"
Ignore validation errors in cluster.conf file
.IP "-p, --password"
Ricci user password for node running ricci
.IP "--getconf"
Print current cluster.conf file
.IP "--setconf"
Use the file specified by '-f' to send to the host
specified with '-h'
.IP "--checkconf"
If file is specified, verify that all the nodes in the
file have the same cluster.conf as the file. If a
host is specified then verify that all nodes in the
host's cluster.conf file have the identical
.IP "--getschema"
Print current cluster schema file (if using -h use
schema from network, if using -f use local schema)
.IP "--sync" ["--activate"]
Sync config file to all nodes and optionally activating that configuration on all nodes
.IP "--activate"
Activate config on node (use this option with --sync
to activate config on all nodes)
.IP "-b, --backup"
Backup cluster.conf file before changes in ~/.ccs/backup directory
.IP "-d, --debug"
Display debugging information to help troubleshoot connection issues with ricci
.IP "--exp tag [location] [options]
Expert mode to add elements not currently defined in ccs
.IP "--exprm location
Expert mode to remove elements not currently defined in ccs
.SS "CLUSTER OPERATIONS"
.IP "--createcluster cluster"
Create a new cluster.conf (removing old one if it
exists)
.IP "--getversion"
Get the current cluster.conf version
.IP "--setversion <n>
Set the cluster.conf version
.IP "--incversion
Increment the cluster.conf version by 1
.IP "--startall [--noenable|--nodisable]
Start *AND* enable cluster services on reboot on all nodes (if --noenable or --nodisable is specified cluster services will only be started)
.IP "--stopall [--noenable|--nodisable]
Stop *AND* disable cluster services on reboot for all nodes (if --noenable or --nodisable is specified cluster services will only be stopped)
.IP "--start [--noenable|--nodisable]
Start *AND* enable cluster services on reboot for host specified with -h or localhost if no host is provided (if --noenable or --nodisable is specified cluster services will only be started)
.IP "--stop [--noenable|--nodisable]
Stop *AND* disable cluster services on reboot for host specified with -h or localhost if no host is provided (if --noenable or --nodisable is specified cluster services will only be stopped)
.SS "NODE OPERATIONS"
.IP "--lsnodes
List all nodes in the cluster
.IP "--addnode <node>
Add node <node> to the cluster
.IP "--rmnode <node>
Remove a node from the cluster
.IP "--nodeid <nodeid>
Specify nodeid when adding a node
.IP "--votes <votes>
Specify number of votes when adding a node
.IP "--addalt <node name> <alt name> [alt options]
Add an altname to a node for RRP
.IP "--rmalt <node name>
Remove an altname from a node for RRP
.SS "FENCING OPERATIONS"
.IP "--lsfenceopts [fence type]
List available fence devices. If a fence type is
specified, then list options for the specified
fence type
.IP "--lsfencedev
List all of the fence devices configured
.IP "--lsfenceinst [<node>]
List all of the fence methods and instances on the
specified node or all nodes if no node is specified
.IP "--addmethod <method> <node>
Add a fence method to a specific node
.IP "--rmmethod <method> <node>
Remove a fence method from a specific node
.IP "--addfencedev <device name> [fence device options]
Add fence device. Fence devices and parameters can be found in online documentation in 'Fence Device Parameters'
.IP "--rmfencedev <fence device name>
Remove fence device
.IP "--addfenceinst <fence device name> <node> <method> [options] [--nounfence]
Add fence instance. Fence instance parameters can be found in online documentation in 'Fence Device Parameters'.
Using --nounfence prevents ccs from automatically
including an unfencing section for agents that require
unfencing (ie. fence_scsi, fence_sanlock, etc.)
.IP "--rmfenceinst <fence device name> <node> <method>
Remove all instances of the fence device listed from
the given method and node
.IP "--addunfenceinst <fence device name> <node> [options]
Add an unfence instance
.IP "--rmunfenceinst <fence device name> <node>
Remove all instances of the fence device listed from
the unfence section of the node
.SS "FAILOVER DOMAIN OPERATIONS"
.IP "--lsfailoverdomain
Lists all of the failover domains and failover domain
nodes configured in the cluster
.IP "--addfailoverdomain <name> [restricted] [ordered] [nofailback]
Add failover domain
.IP "--rmfailoverdomain <name>
Remove failover domain
.IP "--addfailoverdomainnode <failover domain> <node> [priority]
Add node to given failover domain
.IP "--rmfailoverdomainnode <failover domain> <node>
Remove node from failover domain
.SS "SERVICE OPERATIONS"
.IP "--lsserviceopts [service type]
List available services. If a service type is
specified, then list options for the specified
service type
.IP "--lsresourceopts [service type]
An alias to --lsserviceopts
.IP "--lsservices
List currently configured services and resources in
the cluster
.IP "--addresource <resource type> [resource options] ...
Add global cluster resources to the cluster
Resource types and variables can be found in the
online documentation under 'HA Resource Parameters'
.IP "--rmresource <resource type> [resource options]
Remove specified resource with resource options
.IP "--addservice <servicename> [service options] ...
Add service to cluster
.IP "--rmservice <servicename>
Removes a service and all of its subservices
.IP "--addaction <resource/name> <action_name> <action_option=val>
Add an action to the specified resource.
.IP "--rmaction <resource name> [<action_name> [action options]]
Remove all actions from resource, or actions matching action name and options specified
.IP "--addvm <virtual machine name> [vm options] ...
Adds a virtual machine to the cluster
.IP "--rmvm <virtual machine name>
Removes named virtual machine from the cluster
.IP "--addsubservice <servicename> <subservice> [service options] ...
Add individual subservices, if adding child services,
use ':' to separate parent and child subservices
and brackets to identify subservices of the same type
.br
Subservice types and variables can be found in the
online documentation under 'HA Resource Parameters'
.br
To add a nfsclient subservice as a child of the 2nd
nfsclient subservice in the 'service_a' service use
the following example:
.br
ccs <...> --addsubservice service_a nfsclient[1]:nfsclient ref=/test
.IP "--rmsubservice <servicename> <subservice>
Removes a specific subservice specified by the
subservice, using ':' to separate elements and
brackets to identify between subservices of the
same type.
.br
To remove the 1st nfsclient child subservice
of the 2nd nfsclient subservice in the 'service_a'
service, use the following example:
.br
ccs <...> --rmsubservice service_a nfsclient[1]:nfsclient
.SS "QUORUM OPERATIONS"
.IP "--lsquorum
List quorum options and heuristics
.IP "--setquorumd [quorumd options] ...
Add quorumd options
.IP "--addheuristic [heuristic options] ...
Add heuristics to quorumd
.IP "--rmheuristic [heuristic options] ...
Remove heuristic specified by heurstic options
.SS "MISC OPTIONS"
.IP "--lsmisc
List all of the misc options
.IP "--settotem [totem options]
Set totem options
.IP "--setuidgid uid=<uid> gid=<gid>
Set uidgid options
.IP "--rmuidgid uid=<uid> gid=<gid>
Remove uidgid entry matching specified uid/gid
.IP "--setdlm [dlm options]
Set dlm options
.IP "--setrm [resource manager options]
Set resource manager options
.IP "--setcman [cman options]
Set cman options
.IP "--setmulticast [multicast address] [multicast options]
Sets the multicast address to use (or removes it
if no multicast address is given)
.IP "--setaltmulticast [alt multicast address] [alt multicast options]
Sets the alt multicast address to use (or removes it
if no alt multicast address is given)
.IP "--setfencedaemon [fence daemon options]
Set fence daemon options
.IP "--setlogging [logging options]
Set logging options
.IP "--addlogging [logging daemon options]
Add a logging daemon (see cluster.conf for options)
.IP "--rmlogging [logging daemon options]
Remove the logging daemon with the specified options
.SH FILES
.I ~/.ccs/cacert.config ~/.ccs/cacert.pem ~/.ccs/privkey.pem
.RS
Automatically generated certificate files used to authenticate with ricci.
.SH EXAMPLES
.B Create and start a 3 node cluster with apc fencing:
.br
ccs -h host1 --createcluster mycluster
.br
ccs -h host1 --addnode host1
.br
ccs -h host1 --addnode host2
.br
ccs -h host1 --addnode host3
.br
ccs -h host1 --addmethod primary host1
.br
ccs -h host1 --addmethod primary host2
.br
ccs -h host1 --addmethod primary host3
.br
ccs -h host1 --addfencedev myfence agent=fence_apc ipaddr=192.168.0.200 login=apc passwd=apc
.br
ccs -h host1 --addfenceinst myfence host1 primary port=1
.br
ccs -h host1 --addfenceinst myfence host2 primary port=2
.br
ccs -h host1 --addfenceinst myfence host3 primary port=3
.br
ccs -h host1 --sync --activate
.br
ccs -h host1 --startall
.SH AUTHOR
Chris Feist <cfeist@redhat.com>
.SH "SEE ALSO"
.BR ricci (8),
.BR cluster.conf (5),
.BR ccs_tool (8)
.SH NOTES
Fence Device Parameters
\fIhttp://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Cluster_Administration/ap-fence-device-param-CA.html\fP
.br
HA Resource Parameters
\fIhttp://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Cluster_Administration/ap-ha-resource-params-CA.html\fP