TripleO PTL, James Slagle, shares project updates from Kilo to Liberty

1. TripleO
Liberty Update
James Slagle
slagle@redhat.com
@slagle
July 1, 2015

2. TripleO
● TripleO mission…
o Develop and maintain tooling and infrastructure able
to deploy OpenStack in production, using
OpenStack itself wherever possible.
o Big Tent impact
▪ Lots of new services to deploy
▪ Lots of new tooling/infrastructure to deploy *with*

3. Liberty overview...
● Full puppet based implementation complete
o Using PuppetOpenStack
o puppet-tripleo - lightweight composition layer
● Heat investment
o Complete declarative model of the deployed cloud
o Environments
o Resource Mapping (resource_registry)
● Ironic investment
o Baremetal provisioning, ready state configuration
o ironic-inspector (formerly ironic-discoverd)

4. tripleo-heat-templates
● resource_registry
o allows mapping Heat resources to different implementations
o enable/disable features on demand:
▪ pacemaker
▪ network isolation
▪ container deployment
● parameter_defaults
o set parameters in the different implementations (nested stacks)
without modifying the top level templates
● Heat Environments
o saved yaml files combining parameters, parameter_defaults, and
resource_registry sections into recommended configurations

5. Deployment overview...

6. Template overview...

7. Network Isolation
● Dedicated networks based on traffic type
● Provide needed network isolation (tenant,
storage, internal api, etc)
● Additional networks are defined in Neutron
(undercloud), created via Heat and all
template driven.

9. HA/Pacemaker
● HA/pacemaker is optional, and enabled via
the resource-registry
● Set OS:TripleO::ControllerConfig to
overcloud-controller-pacemaker.yaml in the
Heat environment.

10. Package based Upgrades
● UpdateDeployment (SoftwareDeployment resource)
runs yum/apt update.
● packages managed by PuppetOpenStack manifest are
excluded by UpdateDeployment
● Subsequent runs of ‘puppet apply’ with ensure=>latest
lets PuppetOpenStack update puppet managed
packages.

11. Containerization
● Deploy an OpenStack cloud where the
services are containerized
● Using container content from the Kolla
project
● Patches posted for compute nodes,
controller nodes to follow

12. Wrap Up
Connect with us …
[TripleO] on openstack-dev
#tripleo on freenode
James Slagle
slagle@redhat.com
@slagle
July 1, 2015