Loading howto/upgrades.md +35 −0 Original line number Diff line number Diff line Loading @@ -337,3 +337,38 @@ needs to be restarted, or a lot of processes need to, but not the kernel. This has not been tested, but could speed up some restart conditions. ## Notifying users Users should be notified when rebooting hosts. Normally, the `shutdown(1)` command noisily prints warnings on terminals which will give a heads up to connected users, but many services do not rely on interactive terminals. It is therefore important to notify users over our chat rooms (currently [irc](howto/irc)). The `reboot` script can send notifications when rebooting hosts. For that, credentials must be supplied, either through the `HTTP_USER` and `HTTP_PASSWORD` environment, or (preferably) through a `~/.netrc` file. The file should look something like this: machine kgb-bot.torproject.org login TPA password REDACTED The password (`REDACTED` in the above line) is available on the bot host (currently `chives`) in `/etc/kgb-bot/kgb.conf.d/client-repo-TPA.conf`. The users should see this in the `#tor-admin` channel: ``` 13:13:56 <KGB-TPA> scheduled reboot on host web-fsn-02.torproject.org in 10 minutes 13:24:56 <KGB-TPA> host web-fsn-02.torproject.org rebooted ``` A heads up should be (manually) relayed in the `#tor-project` channel, inviting users to follow that progress in `#tor-admin`. Ideally, we would have a map of where each server should send notifications. For example, the `tb-build-*` servers should notify `#tor-browser-dev`. This would require a rather more convoluted configuration, as each KGB "account" is bound to a single channel for the moment... Loading
howto/upgrades.md +35 −0 Original line number Diff line number Diff line Loading @@ -337,3 +337,38 @@ needs to be restarted, or a lot of processes need to, but not the kernel. This has not been tested, but could speed up some restart conditions. ## Notifying users Users should be notified when rebooting hosts. Normally, the `shutdown(1)` command noisily prints warnings on terminals which will give a heads up to connected users, but many services do not rely on interactive terminals. It is therefore important to notify users over our chat rooms (currently [irc](howto/irc)). The `reboot` script can send notifications when rebooting hosts. For that, credentials must be supplied, either through the `HTTP_USER` and `HTTP_PASSWORD` environment, or (preferably) through a `~/.netrc` file. The file should look something like this: machine kgb-bot.torproject.org login TPA password REDACTED The password (`REDACTED` in the above line) is available on the bot host (currently `chives`) in `/etc/kgb-bot/kgb.conf.d/client-repo-TPA.conf`. The users should see this in the `#tor-admin` channel: ``` 13:13:56 <KGB-TPA> scheduled reboot on host web-fsn-02.torproject.org in 10 minutes 13:24:56 <KGB-TPA> host web-fsn-02.torproject.org rebooted ``` A heads up should be (manually) relayed in the `#tor-project` channel, inviting users to follow that progress in `#tor-admin`. Ideally, we would have a map of where each server should send notifications. For example, the `tb-build-*` servers should notify `#tor-browser-dev`. This would require a rather more convoluted configuration, as each KGB "account" is bound to a single channel for the moment...
