Rack power off
How to turn a rack off and on
To turn a rack off (e.g. for scheduled maintenance):
- Log into boss and disable remote access:
- Cleanly shutdown all of the containers on the shared hosts so that they reboot properly when the physical node is powered back on. Note that this can take a while if there are lots of containers:
- Now shutdown each of shared hosts:
- On boss shutdown the testbed daemons:
- Log in to the control node and shut it (and its VMs) down:
- If you like, cleanly shut down the rest of the experimental nodes, too. However, these hosts can easily be reimaged on demand, and (depending what current experiments have modified on the machines) you might not have permission to log in anyway.
- Unplug the nodes at the bottom of the rack. We do this to ensure that the experimental nodes do not reboot until the infrastructure nodes are up and running.
- Power the entire rack down.
boss> wap webcontrol -l nologin
boss> sudo shutdown-shared
vhost-1> sudo shutdown -H now
boss> sudo testbed-control shutdown
ssh control sudo xm shutdown -a -w
After the VMs are gone, shut down the physical host:
ssh control sudo halt
To power a rack back on (e.g. when power returns, or when maintenance is complete):
- Turn on the switches, and wait until they are ready (steady green lights on the "Status" and "Modules" sections of the panels).
- Turn on the control node.
- AFter a while, log into boss and restart the daemons:
- Plug in and turn on the rest of the nodes. Wait a few minutes.
- Optionally, verify that the experimental nodes are running correctly. If not, you might want to force them to restart/reload by logging in to the boss VM and using the node_reboot and os_load commands.
boss> sudo testbed-control boot