OpenStack Tour de Force

Florian's tutorial at OSCON 2013. This page contains important information for tutorial attendees, and will be updated iteratively in the run-up to the conference.

Please note: If you are a tutorial attendee, you might want to subscribe to this page (scroll to the bottom and check Subscribe to → This page, then hit Update). That way, you will get a quick email any time this post is updated, or someone adds a comment. You must be logged in to subscribe.

All the important basic details for this tutorial are on the OSCON website. Please make sure you take a peek.

Expect the tutorial to be crowded. There were over 130 registrations two weeks prior to OSCON, and it's safe to assume that the number will still go up. You might want to be there early, too, to make sure you get your preferred seat.

The VirtualBox images are available via Ubuntu One. It would be great if you could bring these with you to the tutorial, preferably installed, all fired up and ready to go. There are two images:

  • A Puppet master box, which also doubles as a pre-populated proxy so we don't hit the network with any package installations, openstack-puppet.ova (approx. 600M).
  • One template OpenStack node machine, openstack.ova (approx. 300M).

(In addition, there's also an MD5SUMS file).

You'll need only one incarnation of the Puppet master, but three of the OpenStack nodes.

The OpenStack nodes also rely on the availability of a total of 3 host-only networks for internal communications. You'll need to configure them in VirtualBox.

To create the host-only networks, you can either open the VirtualBox Manager, go to File → Preferences and then the Network tab, and create vboxnet0, vboxnet1 and vboxnet2. Or you can run the following steps using the VBoxManage utility from a terminal:

$ VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'vboxnet0' was successfully created
$ VBoxManage hostonlyif ipconfig vboxnet0 \
  --ip 192.168.122.1 --netmask 255.255.255.0
$ VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'vboxnet1' was successfully created
$ VBoxManage hostonlyif ipconfig vboxnet1 \
  --ip 192.168.133.1 --netmask 255.255.255.0
$ VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'vboxnet2' was successfully created
$ VBoxManage hostonlyif ipconfig vboxnet2 \
  --ip 192.168.144.1 --netmask 255.255.255.0

Then, when you import the appliances into your VirtualBox, do make sure that you reinitialize the machines' MAC addresses. Then,

  1. Boot up each OpenStack node
  2. Log in as root with the password openstack
  3. Run ./fixup-host alice, ./fixup-host bob and ./fixup-host charlie, respectively, on the three OpenStack nodes. Then reboot them and you're good to go. No changes are necessary to the Puppet node.

RAM on the machines is deliberately configured on the low side, such as to make the VMs run on laptops without copious amounts of memory. If your laptop does have a good amount of memory, turning RAM up to 2G for the nodes puppet, alice and bob won't hurt.

If you turn up early for the tutorial (around 1pm), you can still grab a USB key containing the VM images from Florian.

The tutorial is in room Portland 255, on the upper level next to the grand ballroom where Ignite and the OSCON keynotes take place.

Comments

openstack-puppet.ova alternate location?

The link returns "Could not locate object"

Keystone itself errors

Hi florine, I am getting below error for alice vm when I try to add kickstart auth.

Please help.

Error: /Stage[main]/Keystone::Endpoint/Keystone_service[keystone]: Could not evaluate: Execution of '/usr/bin/keystone --endpoint http://127.0.0.1:35357/v2.0/ service-list' returned 1: Invalid OpenStack Identity credentials.

Notice: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[kickstack/keystone]: Dependency Keystone_service[keystone] has failures: trueWarning: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[kickstack/keystone]: Skipping because of failed dependenciesNotice: /Stage[main]/Kickstack::Keystone::Api/Kickstack::Exportfact::Export[keystone_internal_address]/Exportfact::Export[kickstack_keystone_internal_address]/Augeas[fact_kickstack_keystone_internal_address]: Dependency Keystone_service[keystone] has failures: trueWarning: /Stage[main]/Kickstack::Keystone::Api/Kickstack::Exportfact::Export[keystone_internal_address]/Exportfact::Export[kickstack_keystone_internal_address]/Augeas[fact_kickstack_keystone_internal_address]: Skipping because of failed dependenciesNotice: /Stage[main]/Keystone::Roles::Admin/Keystone_role[_member_]: Dependency Keystone_service[keystone] has failures: trueWarning: /Stage[main]/Keystone::Roles::Admin/Keystone_role[_member_]: Skipping because of failed dependenciesNotice: /Stage[main]/Keystone::Roles::Admin/Keystone_role[Member]: Dependency Keystone_service[keystone] has failures: trueWarning: /Stage[main]/Keystone::Roles::Admin/Keystone_role[Member]: Skipping because of failed dependenciesNotice: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[services]: Dependency Keystone_service[keystone] has failures: trueWarning: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[services]: Skipping because of failed dependenciesNotice: /Stage[main]/Keystone::Roles::Admin/Keystone_role[admin]: Dependency Keystone_service[keystone] has failures: trueWarning: /Stage[main]/Keystone::Roles::Admin/Keystone_role[admin]: Skipping because of failed dependenciesNotice: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[openstack]: Dependency Keystone_service[keystone] has failures: trueWarning: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[openstack]: Skipping because of failed dependenciesNotice: /Stage[main]/Keystone::Roles::Admin/Keystone_user[admin]: Dependency Keystone_service[keystone] has failures: trueWarning: /Stage[main]/Keystone::Roles::Admin/Keystone_user[admin]: Skipping because of failed dependenciesNotice: /Stage[main]/Keystone::Roles::Admin/Keystone_user_role[admin@openstack]: Dependency Keystone_service[keystone] has failures: trueWarning: /Stage[main]/Keystone::Roles::Admin/Keystone_user_role[admin@openstack]: Skipping because of failed dependencies

linuxcon 2013

Forst off thanks for doing this talk I just caught it at linuxcon the other day but didnt have my computer with me, so I'm doing my homework now. 

Ive gotten up to the run the network script part and I sorta remember there was something I needed to do first. So when I run the create-quantum-networks it's failing. 

it says I must provide a username via either

 

Source the openstack rc file

Hi, you'll need to source the /root/openstackrc file that is being created for you when Kickstack sets up the Keystone admin user and role. Suppose alice is your auth node, then on alice, do

. /root/openstackrc

Then run the network creation script.

You can also check out the screencast at http://youtu.be/8-_4AjBhb50.

Let us know if that helps!

Still need a VM image?

For all of you who still need VM images and don't want to install at the last minute, I am in the hallway just outside the speaker lounge during the morning break. I'm sitting on a bench across the hallway from the speaker lounge, wearing a blue shirt with my name on it. So I should be easy to spot. :)

Cheers,

Florian

vboxnet0

Hi Florian,

It's tricky to setup the VirtualBox network "vboxnet0" in Windows, because the default VirtualBox network name in Windows is "VirtualBox Host-Only Ethernet Adapter". This is a known issue and I posted an article below. I tried to follow the directions, but cannot edit the network name in my registry. Does the network need to be named "vboxnet0", and how can I fix?

Best,Galen

 http://www.fidian.com/problems-only-tyler-has/renaming-windows-network-adapter

vboxnet0 on Windows

Hi Galen,

sorry, I wasn't aware that the default VirtualBox network on Windows is a host-only one (on both Linux and Mac, vboxnet0 is a NAT network). I think it's not a problem if your networks are named vboxnet1 through vboxnet3 instead, but if you want to be sure, please meet me outside the speaker lounge during the morning break and let me take a look. Thanks!

Cheers,

Florian

Download links updated

All download links have now been moved to Ubuntu One.

Unable to start puppet VM after import

After downloading the openstack-puppet VM, importing the .ova file, and checking the box to reinitialize the MAC addresses, I got the following error when starting up the machine:Could not start the machine puppet because the following physical network interfaces were not found: vboxnet0 (adapter 2), vboxnet2 (adapter 4) You can either change the machine's network settings or stop the machine.

This problem exists with the plain openstack.ova file also. Can you please help me figure out how to fix this (preferably without redownloading the .ova files?

Thanks.

David Hancock

Fixed.

Hi David,

no need to re-download the images. Thanks for the reminder to include the information on how to create the required host-only networks. Please follow the updated instructions, and you should be good to go.

(Also, I've taken the liberty to edit out your email address from your comment.)

Cheers,

Florian

Still having trouble with alice/bob/charlie

Thanks. I've followed the additional instructions and was able to get openstack-puppet running. For the alice/bob/charlie VMs, though, I'm still getting flaky results. I've done the following about three times each for the openstack.ova imports, and all but one time, I've never gotten a root prompt. In one case, I got the root prompt and ran "fixup-host bob" and rebooted, and then got the black screen, no prompt.

1. Import appliance, point to openstack.ova file

2. Change name to bob, alice, charlie (or don't change names, same result)

3. Check "reinitialize MAC address" box

4. Import (then most times a black screen results, one time, got a root prompt)

I apologize for being so needy here. If there's more troubleshooting or assistance I can provide from this side, please let me know.

Ubuntu/VirtualBox glitch

Hi David,

that seems to be a video glitch that occurs only with VirtualBox in combination with Ubuntu, and even then only intermittently. I've seen the issue myself, and had hoped it was a local issue on my box. Evidently it's not; here's a workaround though:

  • When you boot, click into the console window and hold down the Shift key.
  • This brings up the (otherwise hidden) GRUB menu.
  • Rather than just hitting the Enter key on the default entry, hit e to enter the GRUB menu editor.
  • Remove the quiet splash boot options.

Ubuntu then boots in text mode without the splash screen, normally completing the bootup process hitch-free.

Once booted, you can of course open /etc/default/grub, remove quiet splash from GRUB_CMDLINE_LINUX_DEFAULT, close the file, and then run update-grub2 to disable the boot splash screen permanently.

Let me know if you run into any other issues.

Media