Revision 79829d23 doc/admin.rst
b/doc/admin.rst | ||
---|---|---|
912 | 912 |
This will deconfigure the node, stop the ganeti daemons on it and leave |
913 | 913 |
it hopefully like before it joined to the cluster. |
914 | 914 |
|
915 |
Replication network changes |
|
916 |
+++++++++++++++++++++++++++ |
|
917 |
|
|
918 |
The :command:`gnt-node modify -s` command can be used to change the |
|
919 |
secondary IP of a node. This operation can only be performed if: |
|
920 |
|
|
921 |
- No instance is active on the target node |
|
922 |
- The new target IP is reachable from the master's secondary IP |
|
923 |
|
|
924 |
Also this operation will not allow to change a node from single-homed |
|
925 |
(same primary and secondary ip) to multi-homed (separate replication |
|
926 |
network) or vice versa, unless: |
|
927 |
|
|
928 |
- The target node is the master node and `--force` is passed. |
|
929 |
- The target cluster is single-homed and the new primary ip is a change |
|
930 |
to single homed for a particular node. |
|
931 |
- The target cluster is multi-homed and the new primary ip is a change |
|
932 |
to multi homed for a particular node. |
|
933 |
|
|
934 |
For example to do a single-homed to multi-homed conversion:: |
|
935 |
|
|
936 |
$ gnt-node modify --force -s %SECONDARY_IP% %MASTER_NAME% |
|
937 |
$ gnt-node modify -s %SECONDARY_IP% %NODE1_NAME% |
|
938 |
$ gnt-node modify -s %SECONDARY_IP% %NODE2_NAME% |
|
939 |
$ gnt-node modify -s %SECONDARY_IP% %NODE3_NAME% |
|
940 |
... |
|
941 |
|
|
942 |
The same commands can be used for multi-homed to single-homed except the |
|
943 |
secondary IPs should be the same as the primaries for each node, for |
|
944 |
that case. |
|
945 |
|
|
915 | 946 |
Storage handling |
916 | 947 |
++++++++++++++++ |
917 | 948 |
|
Also available in: Unified diff