Revision 5ac3214f README
b/README | ||
---|---|---|
8 | 8 |
(e.g. more than five or ten machines); at lower sizes, the |
9 | 9 |
computations they do can also be done manually. |
10 | 10 |
|
11 |
Most of the tools revolve around the concept of keeping the cluster |
|
12 |
N+1 compliant: this means that in case of failure of any node, the |
|
13 |
instances affected can be failed over (via ``gnt-node failover`` or |
|
14 |
``gnt-instance failover``) to their secondary node, and there is |
|
15 |
enough memory reserved for this operation without needing to shutdown |
|
16 |
other instances or rebalance the cluster. |
|
17 |
|
|
11 | 18 |
Available tools |
12 | 19 |
--------------- |
13 | 20 |
|
... | ... | |
42 | 49 |
path—usually ``/usr/lib/ganeti/iallocators`` or |
43 | 50 |
``/usr/local/lib/ganeti/iallocators``. See the man page hail(1). |
44 | 51 |
|
52 |
Cluster capacity estimator |
|
53 |
~~~~~~~~~~~~~~~~~~~~~~~~~~ |
|
54 |
|
|
55 |
The ``hspace`` program will, given an input instance specification, |
|
56 |
estimate how many instances of those type can be place on the cluster |
|
57 |
before it will become full (as in any new allocation would fail N+1 |
|
58 |
checks). For more details, see the man page hspace(1). |
|
59 |
|
|
60 |
|
|
45 | 61 |
Integration with Ganeti |
46 | 62 |
----------------------- |
47 | 63 |
|
Also available in: Unified diff