Mirantis is a pure play OpenStack company that provides the technology, integration, training and support needed for companies to succeed with production-grade open source cloud. The document discusses Platform as a Service (PaaS) and how OpenStack components like Heat, Murano, Solum, Mistral, Trove and Manila can provide an integrated framework for building, packaging, deploying and managing applications in a cloud environment, enabling continuous software innovation. Existing commercial PaaS examples are mentioned along with how the emerging TOSCA standard maps to various OpenStack components, demonstrating that a powerful PaaS can be built using OpenStack.

1. © MIRANTIS 2014 PAGE ‹#›© MIRANTIS 2014
OpenStack, PaaS
and the Code-to-
Cloud Toolchain
Christopher AedoProduct
Architect

2. © MIRANTIS 2014 PAGE ‹#›
Introduction
About Mirantis
Mirantis is the number one pure play OpenStack Company. We deliver
all the technology, integration, training and support required for
companies to succeed with production-grade open source cloud. More
customers rely on Mirantis than any other company to scale out
OpenStack without the compromises of vendor lock-in. Our bench of
400+ open source infrastructure experts helped make us one of top 5
contributors to OpenStack’s upstream codebase.
About Christopher Aedo
A 20+ year IT veteran for consulting, design and technology companies.
Before joining Mirantis he was CIO for a social analytics startup, and most
recently CTO of Morphlabs. He is also an outspoken public advocate for
OpenStack, cloud computing, software defined networking and software
defined storage. He can frequently be found speaking at OpenStack and
Open Source related conferences around the world.

3. © MIRANTIS 2014 PAGE ‹#›
PaaS and the Software
Defined Economy
“organizations are realizing that
continuous software innovation is
critical in terms of building and
preserving competitive advantage.
Companies are trying to figure out how
to leverage their developers to make
this happen.”
-Jonathan Bryce
http://www.openstack.org/blog/2014/05/taking-stock-of-openstacks-
rapid-growth/

4. © MIRANTIS 2014 PAGE ‹#›
PaaS Defined
NIST: The capability provided to the
consumer
is to deploy onto the cloud infrastructure
consumer-created or acquired applicationscreated
using programming languages, libraries,services, and tools
supported by the provider. Theconsumer does not manage or
control theunderlying cloud infrastructure includingnetwork,
servers, operating systems,or storage, but has control over thedeployed
applications and possiblyconfiguration settings for theapplication-hostingenvironment.

5. © MIRANTIS 2014 PAGE ‹#›
An abstraction layer above your infrastructure
providing a framework to address that
infrastructure, along with a standard way to
package, distribute and deploy your code.
PaaS Defined

6. © MIRANTIS 2014 PAGE ‹#›
What’s Needed?
At its core, a PaaS should deliver an integrated
framework to:
• Build
• Package
• Deploy

7. © MIRANTIS 2014 PAGE ‹#›
What’s Needed?
What else should a PaaS deliver?
• IDE integration?
• CI/CD integration?
• Ease of use?
• Portability?
• Catalog of available components?
• Short distance from infrastructure?

8. © MIRANTIS 2014 PAGE ‹#›
Existing Examples
• Cloud Formation (AWS)
• Cloud Foundry (Pivotal)
• OpenShift (RedHat)
• APS (Parallels)
• Heroku (PaaS-as-a-service?)
• Google App Engine
• Azure (PaaS-ish components)
• Docker (emerging key piece)

9. © MIRANTIS 2014 PAGE ‹#›
Cloud Foundry

10. © MIRANTIS 2014 PAGE ‹#›
PaaS Friendly Foundation
YOUR PaaS RUNS HERE

11. © MIRANTIS 2014 PAGE ‹#›
OpenStack works for App &
PaaS Dev
• Perfect platform: open source IaaS
• Standardized interfaces that abstract APIs for
drivers across infrastructure components
• Focused on App Dev Enablement
• Tool chain exists
(and it’s constantly improving!)

12. © MIRANTIS 2014 PAGE ‹#›
Heat
Provides declarative configuration for your
packaged app components
• OpenStack Instantiation Engine
• Inspired by Cloud Formation
• Foundation for other OpenStack components

13. © MIRANTIS 2014 PAGE ‹#›
Murano
A catalog of things already built, reuse entire
components instead of starting from scratch
• Application catalog project
• Embed complicated deployment rules
• Simpler than Heat for developers

14. © MIRANTIS 2014 PAGE ‹#›
Solum
Set the build environment to extrude packaged
code ready to deploy
• Convert code to managed application (a build
pipeline)
• Delivers application artifacts
• Pre-incubation OpenStackproject
• Work in progress, moving fast

15. © MIRANTIS 2014 PAGE ‹#›
Mistral
A way to sequence and organize the steps you
need to get those distributed components running
together
• Workflow as a service
• Intelligent task manager

16. © MIRANTIS 2014 PAGE ‹#›
Enablers
• Trove
•Database-as-a-Service
•Highly performant DB abstraction for a PaaS
• Manila
•Shared filesystem
•Pre-incubation OpenStack project

17. © MIRANTIS 2014 PAGE ‹#›
Sounds familiar…
TOSCA
• Topology and Orchestration Specification for
Cloud Applications
• Very thorough spec

18. © MIRANTIS 2014 PAGE ‹#›
OpenStack mapping
TOSCA term OpenStack component
Deployment Manager Heat
Components, relations,
requirements,
capabilities
Murano
Workflows/plans Mistral
Artifacts Glance(More details: https://blueprints.launchpad.net/heat/+spec/tosca-support)

19. © MIRANTIS 2014 PAGE ‹#›
In summary
• “Software defined” businesses need faster
iteration
• The right PaaS can dramatically speed
development cycle
• Some good open and commercial options
worth considering
• Some even better options can be built with and
on OpenStack

20. © MIRANTIS 2014 PAGE ‹#›
Thank you!
caedo@mirantis.com
Twitter: @docaedo
IRC: christopheraedo
(and yes, Mirantis is hiring!)