Skip to content

Instantly share code, notes, and snippets.

@JCallicoat
Last active December 11, 2015 20:59
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save JCallicoat/4659160 to your computer and use it in GitHub Desktop.
Save JCallicoat/4659160 to your computer and use it in GitHub Desktop.
Images Talk
- Who are we?
Rackspace Private Cloud. We install and operate Openstack clusters, both locally in our datacenters, and remotely in customer datacenters.
<pending>Reference Alamo v3?</pending>
- 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?)
* all of them create virtual machines via kvm
* some support other hypervisors
- What advantages and disadvantages are there to each?
oz
- few good points
- few bad points
veewee
- ...
etc
- How easy is it to customize images with each?
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?
image build + ci system
- jenkins builds images using veewee
- pushes to cloud files CDN - open to public
- 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment