How to persist OpenStack / DevStack configurations across rebooting of the hosting machine
This page documents the instructions on how to persist OpenStack / DevStack configurations across rebooting of the hosting machine, and tips on troubleshooting OpenStack / DevStack from Rui's experience.
Chad and Rob helped Rui set up a Ubuntu 12.04 VM named "devstack.ncsa.illinois.edu", to host the DevStack server that is used in the VM Elasticity work. Rui installed a running cloud / stack on it using DevStack. Later Rob requested Rui to reboot it to update the OS.
...
- Run "./unstack.sh".
This cleanly stops the stack services and screen processes. - Reboot the machine.
- Manually start the RabbitMQ server.
Somehow the RabbitMQ server is not automatically started. Do "sudo service rabbitmq-server start". This takes a while, about 2 minutes. Use Then do "sudo service rabbitmq-server status" to verify that it is started successfully. - After reboot, do NOT use Run "./rejoin-stack.sh" to start the stack, but , do NOT use "./rejoin-stack.sh" to start the stack.
This will use the "stack-screenrc" file, restart the stack, and keep all the configurations that have been made, such as uploaded images, VM instances in suspended (or shelved, but Rui did not test the shelved state) state, and uploaded key pairs.
For example, the VM instances can be seen both in the "nova list" result and the web UI, and "nova resume ..." of suspended VM instances work.
...