This section describes the relevant nova.conf settings for getting a minimal install running. Refer to the OpenStack Compute Administration Manual for guidance on more configuration options. In general, you can use the same nova.conf file across the controller and compute nodes. However, the following configuration options need to be changed on each compute host: my_ip vncserver_listen vncserver_proxyclient_address For the above configuration options, you must use the IP address of the specific compute host, not the cloud controller. The packages automatically do these steps for a user named nova, but if you are installing as another user you should ensure that the nova.conf file should have its owner set to root:nova, and mode set to 0640, since the file contains your MySQL server’s username and password. If you are installing as another user, you should set permissions correctly. This packaged install ensures that the nova user belongs to the nova group and that the .conf file permissions are set, but here are the manual commands, which should be run as root: # groupadd nova # usermod -g nova nova # chown -R nova:nova /etc/nova # chmod 640 /etc/nova/nova.conf The hypervisor is set by editing /etc/nova/nova.conf. The hypervisor defaults to kvm, but if you are working within a VM already, switch to qemu on the libvirt_type= line. To use Xen, refer to the overview in this book for where to install nova components. You can also configure the nova-compute service (and, for example configure a hypervisor-per-compute-node) with a separate nova-compute.conf file and then referring to nova-compute.conf in the nova.conf file. Ensure the database connection defines your backend data store by adding a connection line to the [database] section in nova.conf: connection=mysql://[user]:[pass]@[primary IP]/[db name], such as connection=mysql://nova:yourpassword@192.168.206.130/nova. Add these settings to /etc/nova/nova.conf for the network configuration assumptions made for this installation scenario. You can place comments in the nova.conf file by entering a new line with a # sign at the beginning of the line. To see a listing of all possible configuration option settings, see the reference in the OpenStack Configuration Reference. auth_strategy=keystone network_manager=nova.network.manager.FlatDHCPManager public_interface=eth0 flat_interface=eth0 flat_network_bridge=br100 Here is an example nova.conf with commented sections: The my_ip configuration option will be different for each host, edit it accordingly. The controller node will run the nova-api, nova-scheduler, nova-cert, nova-consoleauth, nova-conductor and optionally nova-network services. The compute node will run the nova-compute and nova-network services. Stop the nova- services prior to running db sync, by running stop commands as root. Otherwise your logs show errors because the database has not yet been populated. On the controller node run: # stop nova-api # stop nova-conductor # stop nova-network # stop nova-scheduler # stop nova-novncproxy $ for svc in api objectstore conductor network volume scheduler cert; do sudo service openstack-nova-$svc stop ; sudo chkconfig openstack-nova-$svc on ; done On the compute node run: # stop nova-compute # stop nova-network $> for svc in api compute network; do sudo service openstack-nova-$svc stop ; sudo chkconfig openstack-nova-$svc on ; done