Download - PaaS, IaaS and the Code-to-Cloud Toolchain
© MIRANTIS 2014 PAGE ‹#›© MIRANTIS 2014
PaaS, IaaS and the Code-to-Cloud Toolchain
Christopher AedoChief Product Architect
© MIRANTIS 2014 PAGE ‹#›
Welcome!
Cloud Open APIWall Street User
Community
© MIRANTIS 2014 PAGE ‹#›
PaaS Defined
NIST: The capability provided to the consumer is
to deploy onto the cloud infrastructure consumer-
created or acquired applications created usingprogramming languages, libraries, services, and
tools supported by the provider. The consumerdoes not manage or control the underlying cloudinfrastructure including network, servers, operating
systems, or storage, but has control over thedeployed applications and possibly configuration
settings for the application-hosting environment.
© MIRANTIS 2014 PAGE ‹#›
PaaS Defined
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.
© MIRANTIS 2014 PAGE ‹#›
What’s Needed?
What should a PaaS deliver?
• Integrated framework to:
• Build
• Package
• Deploy
© MIRANTIS 2014 PAGE ‹#›
What’s Needed?
What else should a PaaS deliver?
• Ease of use?
• Portability?
• Catalog of available components?
• Distance from infrastructure?
© MIRANTIS 2014 PAGE ‹#›
Existing Examples
• Cloud Formation (AWS)
• Cloud Foundry (Pivotal)
• OpenShift (RedHat)
• APS (Parallels)
• Heroku (PaaS-as-a-service?)
• Azure (PaaS-ish components)
© MIRANTIS 2014 PAGE ‹#›
What Next?
Building a PaaS requires:
• Open tooling (for transparent contiguity)
• Open platform
• Open community
• (building your own from scratch could be difficult)
© MIRANTIS 2014 PAGE ‹#›
OpenStack! Why?
• Perfect platform: open source IaaS
• Focused on App Dev Enablement
• Tool chain exists
• It’s constantly improving
© MIRANTIS 2014 PAGE ‹#›
Heat
• OpenStack Orchestration Engine
• Inspired by Cloud Formation
• Foundation for other OpenStack components
© MIRANTIS 2014 PAGE ‹#›
Mistral
•Workflow as a service
• Intelligent task manager
© MIRANTIS 2014 PAGE ‹#›
Murano
• Application catalog project
• Embed complicated deployment rules
• Simpler for developers
© MIRANTIS 2014 PAGE ‹#›
Solum
• Convert code to managed application (a build pipeline)
• Delivers application artifacts
• Pre-incubation OpenStack project
© MIRANTIS 2014 PAGE ‹#›
Sounds familiar…
TOSCA
• Topology and Orchestration Specification for Cloud Applications
• Very thorough spec
© MIRANTIS 2014 PAGE ‹#›
OpenStack mapping
TOSCA translation
• Deployment -> Heat
• Components, relations, requirements, capabilities -> Murano
• Workflows-Plans -> Mistral Workflow
• Artifacts -> Glance
• (No build process in TOSCA)
© MIRANTIS 2014 PAGE ‹#›
In summary
A good PaaS needs:
• Big, engaged community
• Transparent development and growth
• Should enable agility throughout (dev, test, package, deploy, manage)
© MIRANTIS 2014 PAGE ‹#›
Now…
Let’s talk!