Skip to main content

Deploying Devstack with Ironic

Devstack with Ironic


 Openstack is a cloud operating system which manages pools of resources like storage, newtorking, computing and provisions cloud solutions which is massively scalable. Openstack is an free and open source project. Openstack's mission is to provide ubiquitous cloud computing platform which serves as Infrastructure As A Service (IAAS) to meet the needs of public, private cloud and hybrid cloud.


Devstack is an all in one installer for Openstack. Openstack is getting bigger and bigger day by day. Many new projects have been added to it and it is getting more complicated. To make things easy, Devstack offers a way to install all components of Openstack with out much fuss. These are the key components of Openstack :
  1. Compute ( Code name 'Nova') : Nova is responsible for creation and management of virtual machines. It has support for different types of Hypervisors like KVM, Xen, QEMU, Vmware-vsphere, Hyper-V, Baremetal
  2. Object Storage (Code name 'Swift) : Swift provides Object storage. Swift is used to store Objects and files and Openstack is responsible for data replication and ensuring integrity in cluster.
  3.  Block Storage (Code name 'Cinder') : Cinder is used to provide storage for compute instances. It manages creation, attaching, detaching of the block storage to the servers. In addition to this, it can use many storage like Ceph, IBM Storage, NetApp etc
  4. Networking ( Code name ' Neutron'): Neutron is used to provide network as a service to the compute instances. It is responsible for allocating IP addresses and for managing networks inside openstack
  5. Dashboard (Code name 'Horizon') : Horizon is a web interface to manage all the services in openstack. It can be used to spin up a virtual machine , assign a floating IP to it, access its console.
  6. Identity(Code name 'Keystone') : Keystone is the identity service which provides authentication to all the services running inside openstack. It has capabilities to integrate with LDAP.
  7. Image service(Code name 'Glance') : Glance is used to provide images for the virtual machines. It can also be used to store backups. It has the capability to use stored images as templates.
  8. Telemetry(Code name 'Ceilometer') : Ceilometer provides features like Billing for customers. 
  9. Orchestration(Code name 'Heat') : Heat is used to orchestrate different cloud applications using templates
  10. Database(Code name 'Trove'): Trove is relatively new project as of today. It is used to provide Database As A Service. It uses openstack as a black box to provide database as a service
Openstack also consists of many other projects like Ironic which is now a separate project for provisioning of Baremetal instances, Sahara which is used to provision Hadoop cluster on top of Openstack, Fuel which is an all-in-one control plane for automated hardware discovery, network verification, operating systems provisioning and deployment of OpenStack, Marconi which is message queue as a service, TripleO which is openstack on top of openstack, Rally which is benchmarking as a service and many more will be added in future.

Deploying Devstack with Ironic

Devstack can be used to configure all the services that we are interested in deploying in openstack. To know more about devstack, you can refer here.

Lets begin the deployment process. I would prefer trying out this deployment in virtual box which gives me the flexibility to take snapshots of working devstack,  create new virtual machines to try out different configurations. You can download virtual box and follow this guide for creating a clean installation of Ubuntu 12.04 LTS 64 bit vm with atleast 2 gigs of ram. If in case you dont see 64 bit option in the second step, enable virtualization in your Bios.
Now that you have your vm with Ubuntu 12.04 LTS, its time to install Devstack. Start the virtual machine. Open a terminal (ctrl + shift + t) , run an update

sudo apt-get update

All the code of openstack is hosted on github so install git using this command,

sudo apt-get install git

Check if git has installed successfully by checking its version,

git --version

Once git has been installed, its time to clone the devstack from openstack github repository. You can have a look at the repo that we are going to clone here . Click on the branch, you will notice stable/havana and stable/icehouse . To install openstack havana clone the devstack by checking out the stable/havana branch. To install openstack icehouse (latest as of now), clone the devstack by checking out the stable/icehouse. 

For devstack with Icehouse use this command

git clone -b stable/icehouse

For devstack with Havana use this command

git clone -b stable/havana

If you are facing errors with ssl certificate verification , use http instead of https. If this doesn't work , change sslVerify to false using 

git config --global http.sslVerify false
Once the download is done , change to the directory, devstack using
cd devstack

Check the contents of that folder using 
ls -la

You can notice few shell scripts like,,,,, is a shell script which downloads all the components from the respective openstack repositories and clients in /opt/stack. Besure to run this command as a normal user not root . is used to stop the openstack services. is used to join the already running openstack , it will start all the stopped services and screen logs will be appended. does its best to remove mysql, rabbitmq and other openstack configuration files.

Important step

create a new file while you are in devstack's directory named localrc using your favorite editor. I am using vi editor so I would do something like this

vi localrc

Paste this contents to enable all the services and Ironic.

######## From here #######
# Enable Ironic API and Ironic Conductor
enable_service ironic
enable_service ir-api
enable_service ir-cond

# Enable Neutron which is required by Ironic and disable nova-network.

disable_service n-net
enable_service q-svc
enable_service q-agt
enable_service q-dhcp
enable_service q-l3
enable_service q-meta
enable_service neutron

# You can replace "password" with your own one

# Create 3 virtual machines with 512M memory and 10G disk to
# pose as Ironic's baremetal nodes.

# Size of the ephemeral partition in GB. Use 0 for no ephemeral partition.


# By default, DevStack creates a network for instances.
# If this overlaps with the hosts network, you may adjust with the
# following.

# Log all devstack output to a log file

######### Till here########

Save the file. 

Now run 


This will take around 20 minutes. I will clone all the required repositories of all the components that are enabled in the localrc file. As it takes place, let understand what this file means.

 Reclone = yes makes to clone the repo at each run. If this is set to no, is going to clone only if its not in the $dest directory. Second line signifies to make a log of the Since it will run for several minutes, it would be handy to check whats going on and in case of failures to track which component has failed.Once completes, we can see screen with terminals of all the services. Its better to log the screens for the same purpose as stated above. enable_service ironic tells to enable ironic and download the necessary files related to it. Similarly other enable_service commands do the same. Ironic requires neutron so we have to disable the nova network. 

Subsequent lines deal with the password for the database, rabbitmq server, admin password, service token password.

Lines starting with Ironic are used to create 3 vm's with ram 512 mb and with 10 gb space. These three vm's will act as fake baremetal nodes for Ironic.

In case of normal openstack installation, the harware is virtualized using different hypervisors which create virtual machines. Ironic on the other side picks the bare metal servers and PXE (Pre Execution Environment) boots them and deploys the image. Hardware is not virtualized in this case. With Ironic we get the flexibility of cloud with bare metal. Imagine you have 5 servers and you want them to spin up just like you can do spin up a vm in openstack. Ironic does that. 

Rest of the file deals with the network configuration for vm's. What class of IP address will be allocated, what would be their gateway.

Once the completes succesfully (I know it wont happen the first time, if it does, you are very lucky
:-D ), its time to login to Horizon.

check your network interface using ifconfig and note down the Ip address in eth0 interface. Open your browser and go to http://IP. My Ip adress of eth0 interface was x.x.x.x  so my horizon would be http://x.x.x.x  Login credentials would be admin/password . If you have changed the password for ADMIN_PASSWORD, use that password to login.

Once you login, you can see collapsible tiles on the left hand side if you have installed Icehouse. Familiarize yourself with it. We haven't created any instances yet.

Time to check the screens. use "screen -x stack" to see the screens which are consists of different parts of openstack interacting with each other with the help of API. To jump to the next screen use "ctrl +a +n" and to jump to previous screen use "ctrl + a + p". To detach from the screens use "ctrl + a +d".
To list the screens use ctrl + "

Change your working directory to devstack and source the openrc file using this command

source openrc admin admin

This helps us to use the clients python-novaclient. You can also do this using the API's. Get a token from keystone, use curl to get instances using Nova API. Lets stick to the first method.

Query the image id of the default cirros-0.3.1-x86_64-uec image using this command.

nova image-list

Cirros is the OS that we are going to boot in our baremetal instance. You should get something like this

| ID                                                                    | Name                                        | Status | Server |
| a5627443-6d18-4719-866e-62dcde0dd2b9   | bm-deploy.initramfs                   | ACTIVE |        |
| 38d47e4a-13cc-40d8-b16c-b52933a8558b    | bm-deploy.kernel                      | ACTIVE |        |
| 2224b2f2-8a71-4755-a90a-f2c7945a5357     | cirros-0.3.1-x86_64-uec           | ACTIVE |        |
| 919d95f7-8517-4759-b901-cba302d038ba    | cirros-0.3.1-x86_64-uec           | ACTIVE |        |
| 14760c82-d960-448d-80d6-d83302f0234c    | cirros-0.3.1-x86_64-uec-kernel | ACTIVE |        |
| ce8b75e6-94e5-42bf-8a08-140a54468ec4     | cirros-0.3.1-x86_64-uec-kernel | ACTIVE |        |
| 8df7830c-f979-4ee3-b065-f8126f69fdc1        | cirros-0.3.1-x86_64-uec-ramdisk| ACTIVE |        |
| b46e49c3-7a31-4c2e-b870-7570e0dd4ba5    | cirros-0.3.1-x86_64-uec-ramdisk | ACTIVE |        |

Copy the ID of cirros-0.3.1-x86_64-uec . Create a keypair using ssh. Use ssh-keygen -t rsa to create ssh keys. Follow the onscreen instructions. The keys will be stored in a hidden directory starting with .ssh. It would contain the public and private keys, know hosts .

Add the keypair to nova so that we can boot the baremetal instance.

nova keypair-add default --pub-key ~/.ssh/

Lets boot the instance

nova boot --flavor baremetal --image "paste the Id of cirros here" --key-name default testing

The vm we are booting is of flavour baremetal with the image corresponding to the image id of cirros and the keypair corresponding to the default. You would get something like this:

| ID                                   | Name        | Status  | Task State | Power State | Networks          |
| 2aabb512-796b-4178-a67f-cfbdce058190 | testing | Build | Spawing      | No State    |    |

Since we have created three vm which were acting as three fake baremetals, we have powered on one baremetal out of them. Now check the state of baremetal instances using 

ironic node-list

| UUID                                 | Instance UUID                        | Power State | Provisioning State |
| a89a107d-63b4-4412-b3f1-0241fb3b0edb | None                                 | power off   | None               |
| f51ca8a4-c262-40b2-ad6c-288ec2a0b71a | None                                 | power off   | None               |
| add9a19c-6991-4bc5-8744-fd43e9f0720a | 2aabb512-796b-4178-a67f-cfbdce058190 | power on   |wait call-back       |

Note that one of the baremetal instance is powered on and its in wait call-back state.

Check your baremetal instance status by 

ironic node-list

| ID                                   | Name        | Status  | Task State | Power State | Networks          |
| 2aabb512-796b-4178-a67f-cfbdce058190 | testing | Active | -    | No State    | Running   | private =

Problem with SSH
If you are facing any problem with ssh, edit the /etc/sshd_config file and uncomment the ListenAddress. Save the file and restart the service ssh.

You have succesfully deployed Ironic with devstack :) 


  1. This comment has been removed by a blog administrator.

  2. I am reading your post from the beginning, it was so interesting to read & I feel thanks to you for posting such a good blog, keep updates regularly.
    informatica training in chennai

  3. Really awesome blog. Your blog is really useful for me. Thanks for sharing this informative blog. Keep update your blog.
    QTP Training in Chennai

  4. Hi, Thank you very much for this guide. But I am installing openstack infras (network, compute...) on a node and ironic on another node with devsack. Could you please help to give any idea?

    1. Hey, glad you like it. I am not working on Openstack anymore and I am afraid that I cannot help you there. If you need help, please join IRC channel #openstack-101 where you can get help. Openstack-101 IRC channel is for first timers. You could also try

  5. Haryana HSSC Steno Typist Recruitment 2016

    I am actually grateful to the holder of this web page who has shared this wonderful piece of writing at here............


Post a Comment

Popular posts from this blog

How to contribute to Openstack

How to contribute to OpenstackMy contribution : link

First of all lets answer the question who can contribute to Openstack. Anyone. Yes, anyone can contribute to Openstack. Whether you are interested in developing new feature in Openstack  or in Documentation or in fixing Bugs , you are welcome. That's how Open source projects work.
Lets answer another question . Why should anyone contribute to Openstack. The answer would be :  To learn more about the project. By contributing you learn a lot of things. You are making the system better and helping others all over the world who use Openstack.
Let's begin This  is where you should start. The link has all the information on How to contribute. All the commands used here are from that link. In case if you want more info please use the link provided in the beginning. My mentor suggested me to fix a Bug in Openstack. Bug can be a very small one like fixing a typo in the code message or it can be a critical  one. Both are considered as co…

My contribution to Openstack

Contribution to Openstack Stackalytics: Stackalytics is one stop for looking at some one's contribution to Openstack. It has great user interface where we can find the modules user has contributed to, timeline of his contributions. Here is my Stackalytics page link. I have mainly contributed for Openstack-manuals, documentation for Openstack projects about installation, user guides, admin guides and Openstack-API which hosts the documentation related to the API of several Openstack components.