Install the nova-components and dependencies.
sudo apt-get install -y nova-common python-nova nova-compute vlan
Install euca tools, for command line tools
sudo apt-get install -y euca2ools
Install unzip for extracting archives
sudo apt-get install -y unzip
Edit the /etc/nova/nova.conf file to look like this. This file is essentially similar to the configuration file (/etc/nova/nova.conf) of Server1
--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 --state_path=/var/lib/nova --verbose --s3_host=10.10.10.2 --rabbit_host=10.10.10.2 --cc_host=10.10.10.2 --network_size=8 --routing_source_ip=10.10.10.2 --sql_connection=mysql://novadbadmin:novasecret@10.10.10.2/nova --glance_api_servers=192.168.3.1:9292 --image_service=nova.image.glance.GlanceImageService --iscsi_ip_prefix=192.168. --vlan_interface=br100
Restart nova-compute on Server2.
sudo service restart nova-compute
On Server1, check if the second compute node (Server2) is detected by running:
euca-describe-availability-zones verbose
If you see something like the following with all components happy, it means that the set up is ready to be used.
AVAILABILITYZONE nova available AVAILABILITYZONE |- server1 AVAILABILITYZONE | |- nova-compute enabled :-) 2011-09-30 09:26:04 AVAILABILITYZONE | |- nova-scheduler enabled :-) 2011-09-30 09:26:04 AVAILABILITYZONE | |- nova-network enabled :-) 2011-09-30 09:26:07 AVAILABILITYZONE | |- nova-volume enabled :-) 2011-09-30 09:26:06 AVAILABILITYZONE |- server2 AVAILABILITYZONE | |- nova-compute enabled :-) 2011-09-30 09:26:05
Sometimes you may have XXX instead of the smiley. The XXX are displayed when the components are not time-synced. Ensure time synchronization across all components of your OpenStack deployment.
