OpenStack is often deployed using a traditional application approach. However, it's possible to treat OpenStack as a native cloud application. TripleO is a project aimed at exactly that: using one OpenStack cloud to deploy and manage another.
Applications designed for the cloud often share some common properties: microservices architecture, elasticity, multi-tenancy, and scalability. Traditional data center applications also have their own set of requirements: physical storage, heterogeneous hardware, and existing management tools. These two sets of requirements often contrast with one other.
In this talk, we'll discuss how TripleO balances these approaches and bridges the gap between these two methods. We'll discuss how the TripleO feature set meets the needs of deploying OpenStack as both a cloud and traditional
application. We'll cover how TripleO uses Heat, Ironic, and Neutron, and we’ll highlight some of the recent additions to OpenStack that could be integrated into TripleO.
Attendees can expect to learn how TripleO deploys OpenStack as a native cloud application, and how that approach is balanced with traditional datacenter operational needs.
Advanced usage of OpenStack projects, primarily Heat and Ironic will be demonstrated in showing how TripleO works. Advanced features in TripleO itself will also be shown. These features would include using predictable baremetal
configurations, static IP addresses, network interface configurations, physical storage configurations, template composability, and integration with existing provisioning systems.
Attendees will also learn about:
- How TripleO takes a microservices approach to deploying OpenStack
- Orchestrating those microservices across clusters
- Taking advantage of hybrid infrastructure (virtual infrastructure, public/private cloud, baremetal) for OpenStack deployment and development
- How Tripleo can abstract it's deployment model so it can be used to deploy OpenStack anywhere
