In this guide we’ll explain how you can setup a simple OpenStack all in one installation using puppet. In this guide we’ll be using a virtual machine to simulate the hardware. We’ll use the same network configration as was used [in the article on Foreman](http:\/\/www.cloudcomp.ch\/2012\/06\/automating-the-icclab-part-one\/). We’ll also be using Ubuntu 12.04.<\/p>\n
By default, nameserver and domain settings are automatically managed by `resolvconf` (this is due to the primary adapter being managed by DHCP). As puppet relies on the fully qualified host name of nodes its installed on, you should, if not using other means, configure `resolvconf` so that it does not overwrite your domain and nameserver settings. To do this edit `\/etc\/resolvconf\/resolv.conf.d\/head` and place the following content:<\/p>\n
[gist id=3029170]<\/p>\n
Of course feel free to use what ever other values you like to use. Performing this configuration will ensure that resolvconf always generates settings with your values.<\/p>\n
If you are not using your own managed DNS server then you should place IP-host aliases in your `\/etc\/hosts` file. Here’s the relevant file entries used in this article:<\/p>\n
[gist id=3029172]<\/p>\n
Once you have the virtual machine installed, it might help you if you take a snapshot of the it at this stage so that you can roll-back to a fresh state.<\/p>\n
## Install Puppet<\/p>\n
Execute the following:<\/p>\n
[gist id=3029174]<\/p>\n
## Configure Puppet
\nIn order to deploy OpenStack, we will be using puppet in both agent and master mode.<\/p>\n
### Agent Configuration
\nConfigure puppet agent. Edit `\/etc\/puppet\/puppet.conf` so that it the `[agent]` section has the set values of:<\/p>\n
[gist id=3029176]<\/p>\n
### Master Configuration
\nConfigure puppet master. Edit `\/etc\/puppet\/puppet.conf` so that it the `[master]` section has the set values of:<\/p>\n
[gist id=3029177]<\/p>\n
***Note*** that this particular configuration will change when we integrate with Foreman in the article describing Foreman, puppet and OpenStack integration.<\/p>\n
## Select Puppet Modules<\/p>\n
We’ll use the [official Puppetlabs OpenStack modules](https:\/\/github.com\/puppetlabs\/puppetlabs-openstack). Install the prerequisites and checkout the OpenStack modules from Github:<\/p>\n
[gist id=3029179]<\/p>\n
Once done you’ll need to follow the setup instructions (they’re repeated here for completeness):<\/p>\n
[gist id=3029180]<\/p>\n
After executing these steps, the rake script will have placed other required puppet modules in `\/etc\/puppet\/modules\/`<\/p>\n
## Assign the OpenStack Role
\nWe now have to tell puppet that the current VM is to run as a complete OpenStack instance. To do this copy the example `site.pp` file to `\/etc\/puppet\/manifests\/` and then edit so that:<\/p>\n
1. the node definition for the VM reads as `node \/controller.cloudcomplab.ch\/ {`
\n2. `libvirt_type` is set to `qemu`
\n3. if you want further logging information to help you, then set `$verbose` to `true`
\n4. you might want to specify a floating (i.e. static) IP range. For this setup you can add and set `floating_range` to `’192.168.56.128\/25’`<\/p>\n
Once done, wait! This setup will run perfectly fine until you attempt to invoke the services of `nova-volume`. `nova-volume` is not fully setup as there is no LVM group (`nova-volumes`) setup. To set this up manually execute these steps as root:<\/p>\n
1. `truncate -s 2052M \/root\/nova-vol-file`
\n 2. Find the loop-back device associated with `nova-vol-fil`:<\/p>\n
`losetup -f –show \/root\/nova-vol-file`<\/p>\n
In this setup the value is `\/dev\/loop1`<\/p>\n
3. Now, finally, create the LVM volume group:<\/p>\n
`vgcreate nova-volumes \/dev\/loop1`<\/p>\n
You may need to install the LVM tools: `apt-get -y install lvm2`<\/p>\n
**Note** that this LVM mapping is reset on reboot. <\/p>\n
Now that you have setup LVM and puppet to install OpenStack, do just that! Execute:<\/p>\n
`puppet agent –no-daemonize –verbose`<\/p>\n
You’ll see alot of output as puppet installs OpenStack but at the end of the process you will be able to access your OpenStack installation at `http:\/\/192.168.56.2`<\/p>\n
## Using OpenStack
\nNow that you’ve seen the shiny UI of OpenStack you will have noticed that there are no VM images to run. To get a VM image into OpenStack do the following:<\/p>\n
1. Import the authentication credentials into your shell (puppet was kind enough to create these for you)<\/p>\n
`source \/root\/openrc`<\/p>\n
2. Download a VM image, CirrOS in this case:<\/p>\n
`wget https:\/\/launchpad.net\/cirros\/trunk\/0.3.0\/+download\/cirros-0.3.0-x86_64-disk.img`<\/p>\n
3. Import the CirrOS image into glance:<\/p>\n
`glance add name=”CirrOS 0.3 VM Image” disk_format=qcow2 container_format=ovf < cirros-0.3.0-x86_64-disk.img`<\/p>\n
4. Go back to your web user interface and you will see that there is now a VM image to instantiate and execute.<\/p>\n
By the way, the puppetlabs OpenStack github repository [has some decent documentation](https:\/\/github.com\/puppetlabs\/puppetlabs-openstack).<\/p>\n
# Next up
\nWe've now successfully installed an "all-in-one" OpenStack using puppet. In the next article we'll look at expanding this to a multi-node scenario. Stay tuned!<\/p>\n
In this guide we’ll explain how you can setup a simple OpenStack all in one installation using puppet. In this guide we’ll be using a virtual machine to simulate the hardware and the official puppetlabs’ OpenStack module.<\/p>\n","protected":false},"author":72,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"footnotes":""},"categories":[5],"tags":[51,110,195,240,271],"features":[],"class_list":["post-564","post","type-post","status-publish","format-standard","hentry","category-articles","tag-automation","tag-deploy","tag-install","tag-openstack","tag-puppet"],"yoast_head":"\n