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

Code to-cloud toolchain-LA OpenStack meet up-20140626

  • Upload
    aedocw

  • View
    274

  • Download
    0

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: Code to-cloud toolchain-LA OpenStack meet up-20140626

© MIRANTIS 2014 PAGE ‹#›© MIRANTIS 2014

OpenStack, PaaS and the Code-to-Cloud Toolchain

Christopher AedoProduct Architect

David Fishman
Mike Wilson gave me a great discussion of what it takes to deploy a WP environment on containers (PHPwad+DBMS+Nginx+Varnish+...) which if you had one box, you'd just throw it all at Linux; in the cloud, you can containerize each for parallelization (multiple NGINXs, DB-slaves, etc.). But even if you don't containerize it, running each of these on its own VM across a VLAN would be a useful exercise to illustrate.
David Fishman
Are you talking about building 'with' a PaaS or building a PaaS on your own? I think you've made a big intuitive leap from 'a PaaS is great' to 'you need IaaS'. Why wouldn't I just go to Heroku? or do CF on EC2?
Michelle Yakura
For visual interest, make these bullets into a table. Use some color.
Christopher Aedo
I like it, SMRT! https://www.youtube.com/watch?v=tcGQpjCztgA
Christopher Aedo
not 100% sure about the image on this slide - might use something like this instead: http://gemsres.com/story/jul08/609938/Sheehan1.png
Michelle Yakura
Simpler is better
Page 2: Code to-cloud toolchain-LA OpenStack meet up-20140626

© MIRANTIS 2014 PAGE ‹#›

Introduction

About MirantisMirantis 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 AedoA 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.

Page 3: Code to-cloud toolchain-LA OpenStack meet up-20140626

© 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 Brycehttp://www.openstack.org/blog/2014/05/taking-stock-of-openstacks-rapid-growth/

Page 4: Code to-cloud toolchain-LA OpenStack meet up-20140626

© MIRANTIS 2014 PAGE ‹#›

PaaS Defined

NIST: The capability provided to the consumer

is to deploy onto the cloud infrastructureconsumer-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.

Page 5: Code to-cloud toolchain-LA OpenStack meet up-20140626

© 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

Page 6: Code to-cloud toolchain-LA OpenStack meet up-20140626

© MIRANTIS 2014 PAGE ‹#›

What’s Needed?

At its core, a PaaS should deliver an integrated framework to:

•Build

•Package

•Deploy

Page 7: Code to-cloud toolchain-LA OpenStack meet up-20140626

© 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?

Page 8: Code to-cloud toolchain-LA OpenStack meet up-20140626

© 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)

Page 9: Code to-cloud toolchain-LA OpenStack meet up-20140626

© MIRANTIS 2014 PAGE ‹#›

Cloud Foundry

Page 10: Code to-cloud toolchain-LA OpenStack meet up-20140626

© MIRANTIS 2014 PAGE ‹#›

PaaS Friendly Foundation

YOUR PaaS RUNS HERE

Page 11: Code to-cloud toolchain-LA OpenStack meet up-20140626

© 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!)

Page 12: Code to-cloud toolchain-LA OpenStack meet up-20140626

© MIRANTIS 2014 PAGE ‹#›

Heat

Provides declarative configuration for your packaged app components

•OpenStack Instantiation Engine

•Inspired by Cloud Formation

•Foundation for other OpenStack components

Page 13: Code to-cloud toolchain-LA OpenStack meet up-20140626

© 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

Page 14: Code to-cloud toolchain-LA OpenStack meet up-20140626

© 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

Page 15: Code to-cloud toolchain-LA OpenStack meet up-20140626

© 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

Page 16: Code to-cloud toolchain-LA OpenStack meet up-20140626

© MIRANTIS 2014 PAGE ‹#›

Enablers

•Trove•Database-as-a-Service•Highly performant DB abstraction for a PaaS

•Manila•Shared filesystem•Pre-incubation OpenStack project

Page 17: Code to-cloud toolchain-LA OpenStack meet up-20140626

© MIRANTIS 2014 PAGE ‹#›

Sounds familiar…

TOSCA

•Topology and Orchestration Specification for Cloud Applications

•Very thorough spec

Page 18: Code to-cloud toolchain-LA OpenStack meet up-20140626

© 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)

Page 19: Code to-cloud toolchain-LA OpenStack meet up-20140626

© 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

Christopher Aedo
Ignore this, need new more betterer summary...
Page 20: Code to-cloud toolchain-LA OpenStack meet up-20140626

© MIRANTIS 2014 PAGE ‹#›

Thank [email protected]

Twitter: @docaedoIRC: christopheraedo

(and yes, Mirantis is hiring!)