diff --git a/howto/ganeti.md b/howto/ganeti.md index e548f4c8793f1a6a86fa4a4e525385b3ca6ed1cd..cac104311a960f6023a0eda4629940687a5a997c 100644 --- a/howto/ganeti.md +++ b/howto/ganeti.md @@ -1313,11 +1313,11 @@ This command will reboot the entire Ganeti fleets, including the hosted VMs, use this when (for example) you have kernel upgrades to deploy everywhere: - fab -H $(echo fsn-node-0{1,2,3,4,5,6,7,8}.torproject.org | sed 's/ /,/g') reboot-host --no-ganeti-migrate + fab -H $(echo fsn-node-0{1,2,3,4,5,6,7,8}.torproject.org | sed 's/ /,/g') fleet.reboot-host --no-ganeti-migrate In parallel, you can probably also run: - fab -H $(echo dal-node-0{1,2,3}.torproject.org | sed 's/ /,/g') reboot-host --no-ganeti-migrate + fab -H $(echo dal-node-0{1,2,3}.torproject.org | sed 's/ /,/g') fleet.reboot-host --no-ganeti-migrate Watch out for nodes that hold redundant mirrors however. @@ -1330,7 +1330,7 @@ Note that you can cancel a node reboot with `--kind` cancel. For example, say you were currently rebooting node `fsn-node-05`, you can hit <kbd>control-c</kbd> and do: - fab -H fsn-node-05.torproject.org reboot-host --kind=cancel + fab -H fsn-node-05.torproject.org fleet.reboot-host --kind=cancel ... to cancel the reboot of the node and its instances. This can be done when the following message is showing: @@ -1346,7 +1346,7 @@ need a reboot, and not the instances. In that case, you want to reboot the nodes but before that, migrate the instances off the node and then migrate it back when done. This incantation should do so: - fab -H $(echo fsn-node-0{1,2,3,4,5,6,7,8}.torproject.org | sed 's/ /,/g') reboot-host --reason 'Open vSwitch upgrade' + fab -H $(echo fsn-node-0{1,2,3,4,5,6,7,8}.torproject.org | sed 's/ /,/g') fleet.reboot-host --reason 'Open vSwitch upgrade' This should cause no user-visible disruption. @@ -1361,7 +1361,7 @@ upgraded, for example `libxml` or OpenSSL. This will only migrate the VMs without rebooting the hosts: fab -H $(echo fsn-node-0{1,2,3,4,5,6,7,8}.torproject.org | sed 's/ /,/g') \ - reboot-host --kind=cancel --reason 'qemu flagged in needrestart' + fleet.reboot-host --kind=cancel --reason 'qemu flagged in needrestart' This should cause no user-visible disruption, as it migrates all the VMs around and back. @@ -1373,7 +1373,7 @@ If you actually need to restart the instances in place (and not migrate them), you need to use the `--skip-ganeti-empty` flag instead: fab -H $(echo dal-node-0{1,2,3}.torproject.org | sed 's/ /,/g') \ - reboot-host --skip-ganeti-empty --kind=cancel --reason 'qemu flagged in needrestart' + fleet.reboot-host --skip-ganeti-empty --kind=cancel --reason 'qemu flagged in needrestart' ## Rebalancing a cluster