Revision 7e2f08ba
| b/doc/admin.rst | ||
|---|---|---|
| 46 | 46 |
Node can be added and removed (if they host no instances) at will from |
| 47 | 47 |
the cluster. In a HA cluster and only with HA instances, the loss of any |
| 48 | 48 |
single node will not cause disk data loss for any instance; of course, |
| 49 |
a node crash will cause the crash of the its primary instances.
|
|
| 49 |
a node crash will cause the crash of its primary instances. |
|
| 50 | 50 |
|
| 51 | 51 |
A node belonging to a cluster can be in one of the following roles at a |
| 52 | 52 |
given time: |
| ... | ... | |
| 300 | 300 |
|
| 301 | 301 |
Ganeti will start an instance with up to its maximum instance memory. If |
| 302 | 302 |
not enough memory is available Ganeti will use all the available memory |
| 303 |
down to the instance minumum memory. If not even that amount of memory
|
|
| 303 |
down to the instance minimum memory. If not even that amount of memory
|
|
| 304 | 304 |
is free Ganeti will refuse to start the instance. |
| 305 | 305 |
|
| 306 | 306 |
Note, that this will not work when an instance is in a permanently |
| ... | ... | |
| 529 | 529 |
~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 530 | 530 |
|
| 531 | 531 |
If an instance is built in highly available mode, it currently runs and |
| 532 |
both its nodes are running fine, you can at migrate it over to its
|
|
| 532 |
both its nodes are running fine, you can migrate it over to its |
|
| 533 | 533 |
secondary node, without downtime. On the master node you need to run:: |
| 534 | 534 |
|
| 535 | 535 |
$ gnt-instance migrate %INSTANCE_NAME% |
Also available in: Unified diff