Many of the settings for Compute services are stored in the /etc/nova/nova.conf file by default. Here are the relevant settings for getting a minimal install running. Refer to the OpenStack Compute Admin Manual for guidance on more configuration options.
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. 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.
sudo groupadd nova sudo usermod -g nova nova sudo chown -R root:nova /etc/nova sudo chmod 640 /etc/nova/nova.conf
The hypervisor is set either by editing /etc/nova/nova.conf or referring to nova-compute.conf in the nova.conf file. The hypervisor defaults to "kvm", but if you are working within a VM already, switch to "qemu" on the --libvirt_type= line.
Ensure the database connection defines your backend data store by adding a --sql_connection line to nova.conf: "--sql_connection=mysql://[ user ]:[ pass ]@[ primary IP ]/[ db name ]", such as --sql_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 flag settings, see the output of running /bin/nova-api --help.
--network_manager=nova.network.manager.FlatDHCPManager --fixed_range=192.168.100.0/24 --flat_network_dhcp_start=192.168.100.2 --public_interface=eth0 --flat_interface=eth0 --flat_network_bridge=br100
Here is an example nova.conf with commented sections:
# DATABASE --sql_connection=mysql://nova:yourpassword@192.168.206.130/nova # LOGS/STATE --verbose --dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova # RABBITMQ --rabbit_password=guest --rabbit_port=5672 --rabbit_host=192.168.206.130 # SCHEDULER --scheduler_driver=nova.scheduler.simple.SimpleScheduler # NETWORK --network_manager=nova.network.manager.FlatDHCPManager --fixed_range=192.168.100.0/24 --flat_network_dhcp_start=192.168.100.2 --public_interface=eth0 --flat_interface=eth0 --flat_network_bridge=br100 # GLANCE --image_service=nova.image.glance.GlanceImageService --glance_api_servers=192.168.206.130:9292 # COMPUTE --compute_manager=nova.compute.manager.ComputeManager --libvirt_type=qemu # VNCPROXY --vncproxy_url=http://192.168.206.130:6080 --vncproxy_wwwroot=/var/lib/nova/noVNC # MISC --use_deprecated_auth=false --allow_admin_api=true --enable_zone_routing=true # KEYSTONE --keystone_ec2_url=http://192.168.206.130:5000/v2.0/ec2tokens
You also need to configure the api-paste.ini file to enable Keystone as the Identity service. An example api-paste.ini file is included in the Appendix. Update the /etc/nova/api-paste.ini file according to the sample file.
Restart the nova- services prior to running db sync.
sudo restart nova-api sudo restart nova-compute sudo restart nova-network sudo restart nova-scheduler sudo restart nova-vncproxy
