nova will terminate. It may take a while for nova to finish cleaning up. If you exit the process before it is done because there were some problems in your build, you may have to clean up the nova processes manually. If you had any instances running, you can attempt to kill them through the api:

./nova.sh terminate

Then you can destroy the screen:

./nova.sh clean

If things get particularly messed up, you might need to do some more intense cleanup. Be careful, the following command will manually destroy all runnning virsh instances and attempt to delete all vlans and bridges.

./nova.sh scrub

You can edit files in the install directory or do a bzr pull to pick up new versions. You only need to do

./nova.sh run

to run nova after the first install. The database should be cleaned up on each run.

Notes

A sample image should be downloaded by the script, but if necessary you can download it by hand:

wget http://c2477062.cdn.cloudfiles.rackspacecloud.com/images.tgz

untar the file to create a usable images directory

tar -zxf /path/to/images.tgz

If you want to be able to contact the metadata server and route to the outside world from instances, you will need to make sure $HOST_IP is set properly. The script attemps to grab it from ifconfig, but if you have multiple adapters set up, it may fail. Fix it with export HOST_IP="":

If you want to use volumes, you will need to create a volume group called nova-volumes before starting the workers. If you have a spare hard disk attached to your dev box at /dev/sdb (virtual or otherwise), you can create a logical volume with one command:

sudo vgcreate nova-volumes /dev/sdb

If you don't have a spare drive, you can create a flat file to back the volume group. Here is an example for a 100G volume store: