Revision d7731f51
b/man/hail.rst | ||
---|---|---|
54 | 54 |
The options that can be passed to the program are as follows: |
55 | 55 |
|
56 | 56 |
-p, --print-nodes |
57 |
Prints the before and after node status, in a format designed to |
|
58 |
allow the user to understand the node's most important |
|
59 |
parameters. See the man page **hbal**(1) for more details about this |
|
60 |
field. |
|
57 |
Prints the before and after node status, in a format designed to allow |
|
58 |
the user to understand the node's most important parameters. See the |
|
59 |
man page **htools**(1) for more details about this option. |
|
61 | 60 |
|
62 | 61 |
-t *datafile*, --text-data=*datafile* |
63 | 62 |
The name of the file holding cluster information, to override the |
b/man/hbal.rst | ||
---|---|---|
217 | 217 |
new jobset. |
218 | 218 |
|
219 | 219 |
-p, --print-nodes |
220 |
Prints the before and after node status, in a format designed to |
|
221 |
allow the user to understand the node's most important parameters. |
|
222 |
|
|
223 |
It is possible to customise the listed information by passing a |
|
224 |
comma-separated list of field names to this option (the field list |
|
225 |
is currently undocumented), or to extend the default field list by |
|
226 |
prefixing the additional field list with a plus sign. By default, |
|
227 |
the node list will contain the following information: |
|
228 |
|
|
229 |
F |
|
230 |
a character denoting the status of the node, with '-' meaning an |
|
231 |
offline node, '*' meaning N+1 failure and blank meaning a good |
|
232 |
node |
|
233 |
|
|
234 |
Name |
|
235 |
the node name |
|
236 |
|
|
237 |
t_mem |
|
238 |
the total node memory |
|
239 |
|
|
240 |
n_mem |
|
241 |
the memory used by the node itself |
|
242 |
|
|
243 |
i_mem |
|
244 |
the memory used by instances |
|
245 |
|
|
246 |
x_mem |
|
247 |
amount memory which seems to be in use but cannot be determined |
|
248 |
why or by which instance; usually this means that the hypervisor |
|
249 |
has some overhead or that there are other reporting errors |
|
250 |
|
|
251 |
f_mem |
|
252 |
the free node memory |
|
253 |
|
|
254 |
r_mem |
|
255 |
the reserved node memory, which is the amount of free memory |
|
256 |
needed for N+1 compliance |
|
257 |
|
|
258 |
t_dsk |
|
259 |
total disk |
|
260 |
|
|
261 |
f_dsk |
|
262 |
free disk |
|
263 |
|
|
264 |
pcpu |
|
265 |
the number of physical cpus on the node |
|
266 |
|
|
267 |
vcpu |
|
268 |
the number of virtual cpus allocated to primary instances |
|
269 |
|
|
270 |
pcnt |
|
271 |
number of primary instances |
|
272 |
|
|
273 |
scnt |
|
274 |
number of secondary instances |
|
275 |
|
|
276 |
p_fmem |
|
277 |
percent of free memory |
|
278 |
|
|
279 |
p_fdsk |
|
280 |
percent of free disk |
|
281 |
|
|
282 |
r_cpu |
|
283 |
ratio of virtual to physical cpus |
|
284 |
|
|
285 |
lCpu |
|
286 |
the dynamic CPU load (if the information is available) |
|
287 |
|
|
288 |
lMem |
|
289 |
the dynamic memory load (if the information is available) |
|
290 |
|
|
291 |
lDsk |
|
292 |
the dynamic disk load (if the information is available) |
|
293 |
|
|
294 |
lNet |
|
295 |
the dynamic net load (if the information is available) |
|
220 |
Prints the before and after node status, in a format designed to allow |
|
221 |
the user to understand the node's most important parameters. See the |
|
222 |
man page **htools**(1) for more details about this option. |
|
296 | 223 |
|
297 | 224 |
--print-instances |
298 | 225 |
Prints the before and after instance map. This is less useful as the |
b/man/hscan.rst | ||
---|---|---|
75 | 75 |
Prints the node status for each cluster after the cluster's one-line |
76 | 76 |
status display, in a format designed to allow the user to understand |
77 | 77 |
the node's most important parameters. For details, see the man page |
78 |
for **hbal**(1).
|
|
78 |
for **htools**(1).
|
|
79 | 79 |
|
80 | 80 |
-d *path* |
81 | 81 |
Save the node and instance data for each cluster under *path*, |
b/man/hspace.rst | ||
---|---|---|
221 | 221 |
at least one quarter of disk space should be left free on nodes. |
222 | 222 |
|
223 | 223 |
-p, --print-nodes |
224 |
Prints the before and after node status, in a format designed to |
|
225 |
allow the user to understand the node's most important parameters. |
|
226 |
|
|
227 |
It is possible to customise the listed information by passing a |
|
228 |
comma-separated list of field names to this option (the field list |
|
229 |
is currently undocumented), or to extend the default field list by |
|
230 |
prefixing the additional field list with a plus sign. By default, |
|
231 |
the node list will contain the following information: |
|
232 |
|
|
233 |
F |
|
234 |
a character denoting the status of the node, with '-' meaning an |
|
235 |
offline node, '*' meaning N+1 failure and blank meaning a good |
|
236 |
node |
|
237 |
|
|
238 |
Name |
|
239 |
the node name |
|
240 |
|
|
241 |
t_mem |
|
242 |
the total node memory |
|
243 |
|
|
244 |
n_mem |
|
245 |
the memory used by the node itself |
|
246 |
|
|
247 |
i_mem |
|
248 |
the memory used by instances |
|
249 |
|
|
250 |
x_mem |
|
251 |
amount memory which seems to be in use but cannot be determined |
|
252 |
why or by which instance; usually this means that the hypervisor |
|
253 |
has some overhead or that there are other reporting errors |
|
254 |
|
|
255 |
f_mem |
|
256 |
the free node memory |
|
257 |
|
|
258 |
r_mem |
|
259 |
the reserved node memory, which is the amount of free memory |
|
260 |
needed for N+1 compliance |
|
261 |
|
|
262 |
t_dsk |
|
263 |
total disk |
|
264 |
|
|
265 |
f_dsk |
|
266 |
free disk |
|
267 |
|
|
268 |
pcpu |
|
269 |
the number of physical cpus on the node |
|
270 |
|
|
271 |
vcpu |
|
272 |
the number of virtual cpus allocated to primary instances |
|
273 |
|
|
274 |
pcnt |
|
275 |
number of primary instances |
|
276 |
|
|
277 |
scnt |
|
278 |
number of secondary instances |
|
279 |
|
|
280 |
p_fmem |
|
281 |
percent of free memory |
|
282 |
|
|
283 |
p_fdsk |
|
284 |
percent of free disk |
|
285 |
|
|
286 |
r_cpu |
|
287 |
ratio of virtual to physical cpus |
|
288 |
|
|
289 |
lCpu |
|
290 |
the dynamic CPU load (if the information is available) |
|
291 |
|
|
292 |
lMem |
|
293 |
the dynamic memory load (if the information is available) |
|
294 |
|
|
295 |
lDsk |
|
296 |
the dynamic disk load (if the information is available) |
|
297 |
|
|
298 |
lNet |
|
299 |
the dynamic net load (if the information is available) |
|
224 |
Prints the before and after node status, in a format designed to allow |
|
225 |
the user to understand the node's most important parameters. See the |
|
226 |
man page **htools**(1) for more details about this option. |
|
300 | 227 |
|
301 | 228 |
-O *name* |
302 | 229 |
This option (which can be given multiple times) will mark nodes as |
b/man/htools.rst | ||
---|---|---|
51 | 51 |
Options behave the same in all program modes, but not all program modes |
52 | 52 |
support all options. Some common options are: |
53 | 53 |
|
54 |
-p, --print-nodes |
|
55 |
Prints the node status, in a format designed to allow the user to |
|
56 |
understand the node's most important parameters. If the command in |
|
57 |
question makes a cluster transition (e.g. balancing or allocation), |
|
58 |
then usually both the initial and final node status is printed. |
|
59 |
|
|
60 |
It is possible to customise the listed information by passing a |
|
61 |
comma-separated list of field names to this option (the field list |
|
62 |
is currently undocumented), or to extend the default field list by |
|
63 |
prefixing the additional field list with a plus sign. By default, |
|
64 |
the node list will contain the following information: |
|
65 |
|
|
66 |
F |
|
67 |
a character denoting the status of the node, with '-' meaning an |
|
68 |
offline node, '*' meaning N+1 failure and blank meaning a good |
|
69 |
node |
|
70 |
|
|
71 |
Name |
|
72 |
the node name |
|
73 |
|
|
74 |
t_mem |
|
75 |
the total node memory |
|
76 |
|
|
77 |
n_mem |
|
78 |
the memory used by the node itself |
|
79 |
|
|
80 |
i_mem |
|
81 |
the memory used by instances |
|
82 |
|
|
83 |
x_mem |
|
84 |
amount memory which seems to be in use but cannot be determined |
|
85 |
why or by which instance; usually this means that the hypervisor |
|
86 |
has some overhead or that there are other reporting errors |
|
87 |
|
|
88 |
f_mem |
|
89 |
the free node memory |
|
90 |
|
|
91 |
r_mem |
|
92 |
the reserved node memory, which is the amount of free memory |
|
93 |
needed for N+1 compliance |
|
94 |
|
|
95 |
t_dsk |
|
96 |
total disk |
|
97 |
|
|
98 |
f_dsk |
|
99 |
free disk |
|
100 |
|
|
101 |
pcpu |
|
102 |
the number of physical cpus on the node |
|
103 |
|
|
104 |
vcpu |
|
105 |
the number of virtual cpus allocated to primary instances |
|
106 |
|
|
107 |
pcnt |
|
108 |
number of primary instances |
|
109 |
|
|
110 |
scnt |
|
111 |
number of secondary instances |
|
112 |
|
|
113 |
p_fmem |
|
114 |
percent of free memory |
|
115 |
|
|
116 |
p_fdsk |
|
117 |
percent of free disk |
|
118 |
|
|
119 |
r_cpu |
|
120 |
ratio of virtual to physical cpus |
|
121 |
|
|
122 |
lCpu |
|
123 |
the dynamic CPU load (if the information is available) |
|
124 |
|
|
125 |
lMem |
|
126 |
the dynamic memory load (if the information is available) |
|
127 |
|
|
128 |
lDsk |
|
129 |
the dynamic disk load (if the information is available) |
|
130 |
|
|
131 |
lNet |
|
132 |
the dynamic net load (if the information is available) |
|
133 |
|
|
54 | 134 |
-v, --verbose |
55 | 135 |
Increase the output verbosity. Each usage of this option will |
56 | 136 |
increase the verbosity (currently more than 2 doesn't make sense) |
Also available in: Unified diff