Revision 45cb5963
| b/man/hspace.rst | ||
|---|---|---|
| 333 | 333 |
--simulate *description* |
| 334 | 334 |
Instead of using actual data, build an empty cluster given a node |
| 335 | 335 |
description. The *description* parameter must be a comma-separated |
| 336 |
list of four elements, describing in order:
|
|
| 336 |
list of five elements, describing in order:
|
|
| 337 | 337 |
|
| 338 |
- the allocation policy for this node group |
|
| 338 | 339 |
- the number of nodes in the cluster |
| 339 | 340 |
- the disk size of the nodes, in mebibytes |
| 340 | 341 |
- the memory size of the nodes, in mebibytes |
| 341 | 342 |
- the cpu core count for the nodes |
| 342 | 343 |
|
| 343 |
An example description would be **B20,102400,16384,4** describing a |
|
| 344 |
20-node cluster where each node has 100GiB of disk space, 16GiB of |
|
| 345 |
memory and 4 CPU cores. Note that all nodes must have the same specs |
|
| 346 |
currently. |
|
| 344 |
An example description would be **preferred,B20,102400,16384,4** |
|
| 345 |
describing a 20-node cluster where each node has 100GiB of disk |
|
| 346 |
space, 16GiB of memory and 4 CPU cores. Note that all nodes must |
|
| 347 |
have the same specs currently. |
|
| 348 |
|
|
| 349 |
This option can be given multiple times, and each new use defines a |
|
| 350 |
new node group. Hence different node groups can have different |
|
| 351 |
allocation policies and node count/specifications. |
|
| 347 | 352 |
|
| 348 | 353 |
--tiered-alloc *spec* |
| 349 | 354 |
Besides the standard, fixed-size allocation, also do a tiered |
Also available in: Unified diff