PaaS, IaaS and the Code-to-Cloud Toolchain
out of 17
Post on 24-Apr-2015
Embed Size (px)
DESCRIPTIONCloud Open API - Wall Street User Community, June 12th 2014 Luncheon and Working Sessions. Deck to outline the potential PaaS path on OpenStack, illustrating the PaaS space and talking about the components that could be combined to provide a contiguous toolchain for code build, test, package and deployment.
<ul><li> 1. MIRANTIS 2014 PAGE # MIRANTIS 2014 PaaS, IaaS and the Code-to- Cloud Toolchain Christopher Aedo Chief Product Architect </li> <li> 2. MIRANTIS 2014 PAGE # Welcome! Cloud Open API Wall Street User Community </li> <li> 3. 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 using programming languages, libraries, services, and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, or storage, but has control over the deployed applications and possibly configuration settings for the application-hosting environment. </li> <li> 4. 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. </li> <li> 5. MIRANTIS 2014 PAGE # Whats Needed? What should a PaaS deliver? Integrated framework to: Build Package Deploy </li> <li> 6. MIRANTIS 2014 PAGE # Whats Needed? What else should a PaaS deliver? Ease of use? Portability? Catalog of available components? Distance from infrastructure? </li> <li> 7. MIRANTIS 2014 PAGE # Existing Examples Cloud Formation (AWS) Cloud Foundry (Pivotal) OpenShift (RedHat) APS (Parallels) Heroku (PaaS-as-a-service?) Azure (PaaS-ish components) </li> <li> 8. 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) </li> <li> 9. MIRANTIS 2014 PAGE # OpenStack! Why? Perfect platform: open source IaaS Focused on App Dev Enablement Tool chain exists Its constantly improving </li> <li> 10. MIRANTIS 2014 PAGE # Heat OpenStack Orchestration Engine Inspired by Cloud Formation Foundation for other OpenStack components </li> <li> 11. MIRANTIS 2014 PAGE # Mistral Workflow as a service Intelligent task manager </li> <li> 12. MIRANTIS 2014 PAGE # Murano Application catalog project Embed complicated deployment rules Simpler for developers </li> <li> 13. MIRANTIS 2014 PAGE # Solum Convert code to managed application (a build pipeline) Delivers application artifacts Pre-incubation OpenStack project </li> <li> 14. MIRANTIS 2014 PAGE # Sounds familiar TOSCA Topology and Orchestration Specification for Cloud Applications Very thorough spec </li> <li> 15. 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) </li> <li> 16. 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) </li> <li> 17. MIRANTIS 2014 PAGE # Now Lets talk! </li> </ul>
View more >