OpenStack: Icehouse: Adding A Compute Node

From DocWiki

Jump to: navigation, search

This page describes the process for adding a second, dedicated compute node with per-tenant routers and private networks to an all-in-one (AIO) install. Before configuring this compute node, you must deploy an AIO node as described in Icehouse: All-in-One.


  • You have a working AIO node as described in Icehouse: All-in-One, with:
  • You have Ubuntu 14.04 LTS installed on the node that is to become the new compute node. This node can be a physical baremetal server (for example, Cisco UCS) or a Virtual Machine (for example, VMware ESXi).For instructions on manually installing Ubuntu 14.04 LTS on a node, see OpenStack:_Installing_Ubuntu_Linux.


Step 1: On the AIO node, modify or add an entry in the /etc/puppet/data/role_mappings.yaml file to include the name of your compute node ("compute_server01" in this example):
Step 2: On the compute node, become root:
sudo su - 
Step 3: On the compute node, install git:
apt-get install -y git
Step 4: On the compute node, clone the Cisco OpenStack Installer repository:
cd /root && git clone -b havana && cd puppet_openstack_builder && git checkout h.2
Step 5: On the compute node, export the IP address of your AIO node (which is also acting as the Puppet master/Build Server):
export build_server_ip=
Step 6: On the compute node, run the setup script.
a): Move to the install-scripts directory:
cd install-scripts/
b): Run the file:
Step 7: Start the Puppet agent (use the FQDN of your AIO node in place of "" in the example):
puppet agent -td --pluginsync

If the install script and Puppet run finish successfully, the system returns to the shell prompt with the message "Finished catalog run".

Note: the installation script generates Warning messages. These warnings are mostly harmless. If you see an error message, or a warning message that you suspect is significant, see OpenStack:_Troubleshooting for help.

Post Installation Steps

Verify that the OpenStack Nova services are running and on the compute node. On the AIO node's command line, type:
nova-manage service list
The system should display a list like the following:
Binary           Host                                 Zone             Status     State Updated_At
nova-consoleauth all-in-one                           internal         enabled    :-)   2014-03-11 19:00:52
nova-scheduler   all-in-one                           internal         enabled    :-)   2014-03-11 19:00:52
nova-conductor   all-in-one                           internal         enabled    :-)   2014-03-11 19:00:52
nova-compute     all-in-one                           nova             enabled    :-)   2014-03-11 19:00:53
nova-cert        all-in-one                           internal         enabled    :-)   2014-03-11 19:00:52
nova-compute     compute-server01                     nova             enabled    :-)   2014-03-11 19:00:50
In your web browser, connect to the OpenStack Dashboard by entering:

Log in using username admin and password Cisco123. The dashboard should show the compute node.

You can also verify that the new compute node appears in the OpenStack Nova hypervisor list. In the AIO node's command line, type:
nova hypervisor-list

The system should display a table like the following:

| ID | Hypervisor hostname          |
| 1  |       |
| 2  | |

Launch an Instance

To test that an instance successfully launches against your new compute node directly then you can identify the compute node by name when you boot an instance.

  1. Get a list of available networks. On the AIO node, type:
    neutron net-list
  2. Using a network ID from the previous command (in the "--nic net-id=" argument), type:
    nova boot --image cirros-x86_64 --flavor m1.tiny --key_name aio-key --nic net-id=42823c88-bb86-4e9a-9f7b-ef1c0631ee5e --availability-zone nova:compute-server01 test-vm2
  3. Check to see that the instance has launched against the compute node:
    nova hypervisor-servers compute-server01

    You should see a table like the following:

+--------------------------------------+-------------------+---------------+------------------------------+ | ID | Name | Hypervisor ID | Hypervisor Hostname | +--------------------------------------+-------------------+---------------+------------------------------+ | ba995773-bb1c-419c-9aa1-be67d6967345 | instance-00000006 | 2 | |


Rating: 2.0/5 (4 votes cast)

Personal tools