... | ... | @@ -352,6 +352,15 @@ to the `/etc/network/interfaces*` files: |
|
|
|
|
|
gnt-instance modify --net 0:modify,ip=116.202.120.175 test1.torproject.org
|
|
|
gnt-instance stop test1.torproject.org
|
|
|
|
|
|
The renumbering can be done with Fabric, with:
|
|
|
|
|
|
./ganeti -v -H test1.torproject.org renumber-instance --ganeti-node $PRIMARY_NODE
|
|
|
|
|
|
Note that the `$PRIMARY_NODE` must be passed here, not the "master"!
|
|
|
|
|
|
Alternatively, it can also be done by hand:
|
|
|
|
|
|
gnt-instance start test1.torproject.org
|
|
|
gnt-instance console test1.torproject.org
|
|
|
|
... | ... | @@ -1792,11 +1801,18 @@ will move *one* VM, in this example the `test-01` VM from the |
|
|
|
|
|
tsa-misc$ ./ganeti -H test-01.torproject.org -v renumber-instance dal-node-02.torproject.org
|
|
|
|
|
|
Note how we use the name of the Ganeti node where the VM resides.
|
|
|
Note how we use the name of the Ganeti node where the VM resides,
|
|
|
*not* the master.
|
|
|
|
|
|
Also note that this will give you a bunch of instructions on how
|
|
|
to complete the renumbering. Do *not* follow those steps yet! Wait
|
|
|
for confirmation that the new VM works *before* changing DNS so we
|
|
|
have a chance to catch problems.
|
|
|
|
|
|
4. test the new VM
|
|
|
|
|
|
5. if satisfied, change DNS to new VM
|
|
|
5. if satisfied, change DNS to new VM in LDAP, Nagios, and everywhere
|
|
|
else the above `renumber-instance` command suggests looking.
|
|
|
|
|
|
6. schedule destruction of the old VM (7 days)
|
|
|
|
... | ... | |