Joe Gordon
But...
It's hard to deploy and upgrade
OpenStack was easier to deploy
"TripleO is the use of a self hosted OpenStack infrastructure - that is OpenStack bare metal (nova and cinder) + Heat + diskimage-builder + in-image orchestration such as Chef or Puppet - to install, maintain and upgrade itself."
Combines metadata delivered to instance from cloud with templates shipped with image to produce usable configuration files.
Small utility designed specifically to move Tripleo forward without tying reference implementation to specific configuration management solution.
You can use chef/puppet/salt here instead if you prefer.
Triggered when when metadata is updated: responsible for restarting services, coordinating data migration, and signalling completion to Heat.
pre-configure
configure
migration
post-configure
When events occur that change our state, heat triggers will fire causing the system to respond appropriately.
Rolling backwards becomes as simple as rolling forward: simply deploy the old image.
Prevent entropy by managing your cloud the cloud way:
Store data and persistent state in persistent volume.
Integrate this as a part of CI/CD infrastructure - deploy and test entire cloud in production-like environment on every commit.
What problems are left to solve?
github.com/openstack/tripleo-incubator
wiki.openstack.org/wiki/TripleO
#tripleo on freenode
Powered by reveal.js