gistfile1.md

OpenStack Summit Images Talk

Who we are

Rackspace Private Cloud. We install and operate Openstack clusters, both locally in our datacenters, and remotely in customer datacenters.

Reference Alamo v3?

What are we talking about?

Automating base image builds for OpenStack private clouds.

Why should you care?

Blah blah benefits of providing automated, homogenous, patched base images to your customers Functionally tested

What options are available "off-the-shelf" for building images?

• oz
• veewee
• boxgrinder
• others we won't directly address (the rhel thing? others?)

What advantages and disadvantages are there to each?

• All of them create virtual machines via KVM
• some support other hypervisors

oz

• few good points
• few bad points

veewee

• ...
• ...

etc

How are images customized?

oz

• sample config / template

veewee

• ...

What might you care about customizing

Post-boot stuff like cloud-init and config-drive, registering instance with LDAP, etc.

etc

How are build errors handled / logged?

oz

• what happens on build failure in general
• any specific quirks

veewee

• ...

etc

How do we automate image builds for customers at Rackspace?

1. image build + ci system
2. jenkins builds images using veewee
3. pushes to cloud files CDN - open to public
4. images functionally tested against Openstack tempest suite for basic errors -- just nose tests, write your own if you need them (e.g, to test that some service is up on the instance to pass the gate for the image build)

how we customize images

what images we provide

Q/A