OpenStack: Why Is It Gaining So Much Traction?


Published on

This is a presentation I gave at the combined Minnesota OpenStack and DevOps Meetup.

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Looking for content!A chance to meet OpenStack enthusiastsLearn about how existing technologies interface with OpenStackPlanning to start hackathons this summer
  • A great crowd, diverse peopleIf we have WebEx, people from multiple countries, multiple states
  • Just a quick note about the agenda here
  • Give people time to read thisMake a note of Amazon hereAt the end of the day, it’s made up of the core componentsA Linux Analogy
  • NASA contributed compute controller (Nova) it had built to control the NASA Nebula cloud (think Amazon EC2)Rackspace contributed the object storage controller (Swift) that it built to run it’s CloudFiles service offering (think Amazon S3)Releases: Austin (Oct. 2010), Bexar (Feb 2011), Cactus (Apr 2011), Diablo (Sep 2011), Essex (Apr 2012), Folsom (Sept 2012), Grizzly (Apr 2013)OS/HyperVisor Vendors: Citrix, Red Hat, Canonical, SuSE, VMwareCloud service/tools/SaaS/valure-add vendors: Puppet Labs, RightScale, FathomDB, OpsCode, ServiceMesh, New Relic, Scalr, EnstratiusEquipment Vendors: Cisco, IBM, HP, Intel, NetApp, EMC, Brocade, Dell, AcerOpenStack Software and Services: Piston, Nebula, Mirantis, CloudScaling
  • OpenStack FoundationMembership free for individualsPlatinum, Gold, and Corporate memberships paid for by member companiesBoard of directors comprised of Platinum, Gold, and elected membersTechnical CommitteeLeads software direction and development8 project Technical Leaders elected by project contributors5 additional members elected by active technical contributorsUser CommitteeRepresents users with the Technical Committee and Board of directors
  • Social Networking: Twitter, LinkedIn, Facebook,OhlohCode: Over 54,000 commits by over 850 contributorsDesign SummitUpcoming in 1.5 weeks in PortlandConference plus Design eventUnique, but modeled after UDS (Ubuntu Developer Summit)
  • There was an early attempt at adding some Java code, but because no one knew Java, it was abandonded.Traits of Cloud OS:Abstraction layers (examples: multiple hypervisors, networks, storage)Multi-tenancyRich API’s, portals, clientsOn demand resource allocationResource pooling and schedulingPublic/Private/HybridUsed to tout cloud freedom to some extentRun your workloads on a OpenStack cloud, make them easily portable
  • Some things to note here:Mention Amazon hereMake a distinct note of “Your Application” on the topWith regards to HW: Standard x86/x86_64 as well as ARMApplications running on top are the real item of importance here
  • All of these things show how large the community isRoom for everyone to contributeIncubated Projects:A new project starts out as incubated.Allows for a gestation period as the project is vetted by the community and begins to function like other OpenStack projectsThis includes weekly meetings, involvement with the Technical Committee, and project integration (mailing lists, bugs, etc.)
  • Important for this slide:Deployment is a challenge.Most of the “low-hanging fruit” of OpenStack integration is at this level.Upgrades? Who worries about upgrades?
  • Mention Cisco’s use of OpenStack by our WebEx groupMention the Best Buy presentation given by Steve as users
  • Some notes on devstack:Meant for developers.Typically the first taste of OpenStack for most people.Works on Fedora/Ubuntu, supports single and multi-node installs, works with all the major components.OpenStack powered clouds:RackspaceHP (x86 and ARM running Essex)
  • Lessons learned while working with any open source community:Alternatively: It’s hard to turn down an idea with solid code behind it.Be vocal about your ideas. Doesn’t matter if you’re a developer or a user.
  • Join the mailing listsJoin the IRC channelsParticipate in a local MeetupInstall it and give it a shot!
  • Note how webscale apps and deployments are migrating into enterprise datacenters and applicationsNote how the flow of innovation is from web to enterpriseNote the surge in open source software usageTie it together with DevOps (e.g. DevOps is tieing open source software development together with deployment)DevOps is custom fit for Open Source development.
  • These are happening all over the worldPeople are sharing ideas and helping each other outFosters growth in not only OpenStack, but in the participation level of people who are using, deploying, and developing OpenStack
  • IRC, Mailing lists, Meetup Groups, Bi-annual conferencesPlenty of places to get help
  • Cloud APIs:NativeOpenStack API (helps with workloads across OpenStack public and private clouds)Amazon Web Services APIGoogle Compute Engine API (Cloudscaling)<Your fancy Cloud API here>Regarding lock-in:Perception is realityIs it really preventing lock-in?
  • Commoditization of the cloud provider.Commoditization of the cloud userMeet in the middle somewhere
  • This is the biggest reason OpenStack is Gaining MomentumAmazon has shown everyone how to run a public cloud
  • Notes:The conversation started as “I want to run on AWS.”Now the conversation is “I want to run AWS in my own datacenter.”Natural evolution of the Virtualization experience: Cloud.
  • OpenStack Gaining Momentum Because:Community is important.The threat of Cloud Provider Lock-InAmazon Web ServicesLets remember what the cloud is supposed to offer: Freedom and Openness
  • OpenStack: Why Is It Gaining So Much Traction?

    1. OpenStack: Why Is It Gaining So Much Traction?Kyle Mestery (@mestery)Technical Leader, Office of the Cloud CTO, Cisco© 2010 Cisco and/or its affiliates. All rights reserved. 1
    2.  Minnesota OpenStack Meetup  We meet every 4-6 weeks and discuss all things OpenStack Growing community, not limited only to the Twin Cities  Have members from all over the US (CA, MA, NC, TX) and all over the world (China, France, India) We are looking for presenters!  Get in touch with me to schedule your own presentation!
    3.  The audience: • Work for AMD, Best Buy, Cisco, Dell, Enstratius, Huawei, IBM, Kroll Ontrack, Lifetouch, Qlogic, Raytheon BBN, Super Go Faster, Target, UnitedHealth Group, and others • Are OpenStack/DevOps developers, OpenStack deployers, and/or OpenStack newbies
    4.  What is OpenStack? What’s the community like? What’s the software like? Why Is OpenStack Getting So Much Traction?
    5. “OpenStack is a global collaboration of developers and cloud computingtechnologists producing the ubiquitous open source cloud computingplatform for public and private clouds. The project aims to deliversolutions for all types of clouds by being simple to implement, massivelyscalable, and feature rich. The technology consists of a series ofinterrelated projects delivering various components for a cloudinfrastructure solution.”--  Basically, it’s software to run cloud services and the community behind that software.
    6.  Founded in July 2010 by Rackspace Hosting, NASA, and partners. • Nasa and Rackspace contributed the beginning code• 7th release (Grizzly) due out in April • OpenStack has a 6-month time-based release cycle• Over 169 companies have now joined the community • OS/Hypervisor makers • Public cloud/service providers • Equipment Vendors • OpenStack Software & Services
    7.  The OpenStack Foundation Board of Directors• Technical Committee• User Committee• More details here.
    8.  IRC Channels and Mailing Lists User/Meetup Groups Social Networking Code on GitHub, Bugs/Milestones in Launchpad Two Annual Design Summit/Conferences (coinciding roughly w/releases) Want to contribute? Start here.
    9.  OpenStack is written primarily in Python Licensed under the Apache Public License 2.0 Has traits typical of cloud OS’s: Can be used to build public, private, or hybrid clouds
    10. HorizonAWS Management Console Quantum Nova Swift (Object Storage) VPC EC2 S3 Cinder (Block storage) EBS Glance Keystone (VM Image Service) (Identity Service)
    11. Supporting Projects Incubated Projects (may become coreDocumentation components in the future)CI & Infrastructure Ceilometer (metering/billing/monitoring)Library Projects Heat (AWS CloudFormation compliant resourceClient libraries templating)Oslo (common code libraries)Gating ProjectsDevStack (deployment script)Tempest (integration test)
    12.  Deployment & Configuration Management • Puppet • Chef • Juju • Crowbar Multi-cloud abstraction layers • jClouds • Dasein-cloud • Deltacloud
    13.  Packaging, distributing, productizing:  Red Hat, Canonical, SuSE, Fedora, Debian, Piston, StackOps, Cloudscaling, SwiftStack, others Services and Training:  Mirantis, Rackspace, Cloudscaling, Grid Dynamics, Hastexo, StackOps, others Deploying:  Rackspace, HP, DreamHost, Cisco, Mercado Libre, Canonical, AT&T, eNovance, San Diego Supercomputer Center, Argonne National Lab, NeCTAR, eBay, Paypal, Comcast, CERN, Intel, Deutsche Telekom, Sina, ISI, many more  User stories:
    14.  Developers can get started fast with DevStack. Most major Linux distributions and some vendors offer packages. Start using an OpenStack-powered public cloud immediately.
    15.  Putting your best foot forward means putting your code where your mouth is.  Ideas are more readily accepted when there’s effort to back them up.
    16.  Don’t be intimidated. • HolycrapthingsmovereallyreallyfastinOpenStack • Jump in feet first: be agile and flexible.
    17. Today’s ArchitecturalWeb Battle EnterpriseApproach ApproachScale-out Vertical scalingArchitecture HA failover modelDesign for Failure TransactionalInformation-centric Application specificCommodity Infrastructuresystems CommercialOpen Source Software Innovation
    18. 3 Reasons for OpenStack Momentum
    19.  Whether you’re a developer, deployer, or a user, there’s a place for you in OpenStack Ask a question, get many answers! Have some code, contribute it upstream! Most importantly: Have fun!
    20. You are here
    21.  OpenStack Supports multiple cloud API sets Provides a comfort level about preventing lock-in for your cloud workloads  Perception is reality
    22.  If everyone is offering the same cloud, where is the value for the operator? If everyone offers extensions to the same underlying cloud, does the customer feel the threat of lock-in? Ultimately it’s a level of comfort compared to vendor specific clouds
    23.  Allowed an entire ecosystem of startups to proliferate Allowed enterprise users to dip their toes into this brave new world Opened people’s eyes to Commodity Web Scale Compute …• And Fostered Cloud Computing Envy!
    24. • And most importantly has caused many conversations like this to take place between CxOs and their IT departments
    25. “We are all part of a community muchlarger than each of us individually, allcreating a massively scalable cloudoperating system.” Questions?