1
2ccs_test(8) System Manager's Manual ccs_test(8)
3
4
5
7 ccs_test - The diagnostic tool for a running Cluster Configuration Sys‐
8 tem.
9
10
12 ccs_test [options] <command>
13
14
16 ccs_test is part of the Cluster Configuration System (CCS). It is a
17 diagnostic tool designed to validate the correct operation of a running
18 CCS system. It will communicate with the CCS daemon - ccsd - to obtain
19 any information stored in the system.
20
21
23 -h Help. Print out the usage syntax and exit.
24
25 -V Print the version information and exit.
26
27
29 connect [force] [block] [cluster name]
30 This command creates a connection to ccsd. It returns a
31 descriptor, which is used as an parameter to other commands.
32
33 The 'force' key-word is used to establish a connection to ccsd
34 in the absence of a quorate cluster manager.
35
36 The 'block' key-word is used (with the 'force' key-word) to tell
37 ccsd to keep broadcasting for a valid configuration file until
38 one is found.
39
40 The 'cluster name' is used (with the 'force' key-word) to spec‐
41 ify that only configuration files containing the given cluster
42 name are valid possibilities.
43
44
45 get <desc> <request>
46 Get the results of a given request. The 'desc' is the number
47 returned from the connect command. The 'request' is a valid
48 Xpath request.
49
50 If 'request' results in multiple matches, the first will be
51 returned. Subsequent calls with the same 'request' will result
52 in the subsequent matches. Once all the matches have been
53 returned, a subsequent call will begin again with the first
54 result.
55
56
57 get_list <desc> <request>
58 Similar to the get command. However, issuing subsequent calls
59 with the same 'request' will result in all matches being
60 returned (one at a time), then null, then starting over with the
61 first result.
62
63
64 set <desc> <path> <value>
65 Sets a particular 'path' to the given 'value'. Not yet imple‐
66 mented.
67
68
69 get_state <desc>
70 Get the state associated with a given connection.
71
72
73 set_state <desc> <ncwp>
74 Set the current working path (cwp) to 'ncwp' for a given connec‐
75 tion.
76
77
79 To connect to ccsd:
80 > ccs_test connect
81
82 Connect successful.
83 Connection descriptor = 0
84
85 Or, if the cluster is not yet quorate and the name of the cluster is
86 'mycluster':
87
88 > ccs_test connect force block mycluster
89
90 Connect successful.
91 Connection descriptor = 0
92
93
94 To get the cluster name from ccsd:
95 > ccs_test get 0 /cluster/@name
96
97 Get successful.
98 Value = <mycluster>
99
100
101 To get the connection state:
102 > ccs_test get_state 0
103
104 Get state successful.
105 Current working path:
106 Previous query : /cluster/@name
107
108
109
110 To set the connection state:
111 > ccs_test set_state 0 /cluster
112
113 Set state successful.
114
115
116
117 After setting the connection state, note the change:
118 > ccs_test get_state 0
119
120 Get state successful.
121 Current working path: /cluster
122 Previous query : /cluster/@name
123
124
125 After setting the connection state, you can now query with an absolute or
126 relative path:
127 > ccs_test get 0 @name
128
129 Get successful.
130 Value = <brassow>
131
132 > ccs_test get 0 /cluster/@name
133
134 Get successful.
135 Value = <brassow>
136
137
138 To disconnect:
139 > ccs_test disconnect 0
140
141 Disconnect successful.
142
143
145 ccs(7), ccsd(8), cluster.conf(5)
146
147
148
149 ccs_test(8)