Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.
TripleO:


OpenStack on OpenStack
Chris Jones
IRC: Ng (Freenode)
Twitter: @cmsj
Email:

cmsj@tenshu.net

© Copyright 2013 ...
What is TripleO (OpenStack On OpenStack)?

➡ Using OpenStack to deploy OpenStack on real hardware

© Copyright 2013 Hewlet...
Why?

➡ Lots of existing tools/methods for deploying OpenStack
➡ Few prioritise deployment speed
➡ Few leverage OpenStack’...
What is TripleO made of?
➡ OpenStack components:
➡ nova-baremetal
➡ neutron
➡ heat
➡ Original components:
➡ diskimage-buil...
How does a TripleO deployment work?
➡ Heat drives “seed” VM to deploy an "undercloud" image to bare metal
➡ nova-baremetal...
How do changes/upgrades work?

➡ Configuration changes can be applied by config management
➡ Beware entropy!
➡ Image upgra...
Why use images for deployment?

➡ Speed (dd vs OS installer)
➡ Also applies to rollbacks
➡ Reproducibility (e.g. package v...
Why is speed so important?

➡ Continuous Delivery gives you control and flexibility
➡ Why wait for an OpenStack release if...
How can I try it out?

➡ “tripleo-incubator” git repo on git.openstack.org
➡ devtest.sh
➡ Creates 4 VMs to emulate real ha...
How can I find out more?

➡ http://wiki.openstack.org/wiki/TripleO
➡ #tripleo on Freenode
➡ Come talk to me

© Copyright 2...
Thank you

➡ Questions?

© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is su...
Nächste SlideShare
Wird geladen in …5
×

TripleO Lightning Talk

981 Aufrufe

Veröffentlicht am

A 10 minute introduction to OpenStack's TripleO deployment project

Veröffentlicht in: Technologie, Business
  • Als Erste(r) kommentieren

TripleO Lightning Talk

  1. 1. TripleO:
 OpenStack on OpenStack Chris Jones IRC: Ng (Freenode) Twitter: @cmsj Email: cmsj@tenshu.net © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  2. 2. What is TripleO (OpenStack On OpenStack)? ➡ Using OpenStack to deploy OpenStack on real hardware © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  3. 3. Why? ➡ Lots of existing tools/methods for deploying OpenStack ➡ Few prioritise deployment speed ➡ Few leverage OpenStack’s inherent ability to provision machine resources ➡ Standard OpenStack APIs for infrastructure is awesome © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  4. 4. What is TripleO made of? ➡ OpenStack components: ➡ nova-baremetal ➡ neutron ➡ heat ➡ Original components: ➡ diskimage-builder ➡ configuration management tools © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  5. 5. How does a TripleO deployment work? ➡ Heat drives “seed” VM to deploy an "undercloud" image to bare metal ➡ nova-baremetal switches on a suitable machine via IPMI ➡ machine netboots into ramdisk to write image to disk, then reboots ➡ config management tools configure machine and start service daemons ➡ repeat until “undercloud” is functional ➡ Heat drives “undercloud” to repeat entire process until “overcloud” is functional © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  6. 6. How do changes/upgrades work? ➡ Configuration changes can be applied by config management ➡ Beware entropy! ➡ Image upgrades are driven by “nova rebuild” and the deployment ramdisk ➡ (Ask me afterwards if you want to know how data persists the rebuild) © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  7. 7. Why use images for deployment? ➡ Speed (dd vs OS installer) ➡ Also applies to rollbacks ➡ Reproducibility (e.g. package version skew) © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  8. 8. Why is speed so important? ➡ Continuous Delivery gives you control and flexibility ➡ Why wait for an OpenStack release if trunk passes tests? ➡ Quicker bug fixes ➡ Quicker feature addition © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  9. 9. How can I try it out? ➡ “tripleo-incubator” git repo on git.openstack.org ➡ devtest.sh ➡ Creates 4 VMs to emulate real hardware ➡ Deploys full (but non-HA) seed/undercloud/overcloud environment © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  10. 10. How can I find out more? ➡ http://wiki.openstack.org/wiki/TripleO ➡ #tripleo on Freenode ➡ Come talk to me © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
  11. 11. Thank you ➡ Questions? © Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

×