Webinar: Why Private PaaS is Not an Oxymoron (ActiveState Stackato and Cloud Foundry)

  • 1,988 views
Uploaded on

PaaS promises to trim development and deployment time from months and years to days and weeks, but what are the signs of a true PaaS powerhouse? Is it simply free of servers or software to manage? …

PaaS promises to trim development and deployment time from months and years to days and weeks, but what are the signs of a true PaaS powerhouse? Is it simply free of servers or software to manage? Does it provide automatic upgrades and elasticity? Can you develop in multiple languages?

When you hear of PaaS (Platform-as-a-Service) what typically comes to mind are names like Heroku, EngineYard, DotCloud, and CloudFoundry.com–hosted Public PaaS providers. With the increasing focus on development of SaaS applications and some clear advantages to placing IT infrastructure in the cloud, these PaaS providers have had some trouble gaining significant traction with enterprises despite obvious advantages.

There is an emerging trend where enterprises require PaaS capabilities, but are demanding it on their own terms. They want a PaaS behind their own firewall to enable a secure cloud–a private PaaS.

Join Patrick Chanezon, VMware Senior Director, Developer Relations, and Bart Copeland, ActiveState CEO to learn about:

* The landscape and drivers for Private PaaS
* Issues for enterprises moving development resources to the cloud
* How a Private PaaS differs from a Public PaaS
* Avoiding vendor lock-in
* What to consider when implementing and deploying a Private PaaS

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • Want to watch the webinar? Watch a recording at:

    http://www.activestate.com/webinars/private-paas-oxymoron
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
1,988
On Slideshare
0
From Embeds
0
Number of Embeds
2

Actions

Shares
Downloads
41
Comments
1
Likes
7

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • 2:40 to 3:25. Allow 5 to 10 minutes for questions so talk for 35 to 40 minutesI got the idea for this topic “why private PaaS is Not an Oxymoron” when I was speaking an analyst Principal Analyst of Forrester at Cloud Expo NYC early this year. Because after a talk he gave I approached him for his views on Private PaaS. He immediately said, private PaaS isn't that an Oxymoryon. I then explained to him on the surface yes it is, but no it is not when you look under the surface. Then I thought, what a great topic. Hence why I am going to speak to you today about “Why Private PaaS is not an Oxymoron.
  • *** COULD BE PRESENTED BY BART OR PATRICK *** If Patrick, change to his slide formatting here.From Gartner: PaaS is a common reference to the layer of cloud technology architecture that contains all application infrastructure services, which are also known as "middleware" in other contexts. PaaS is the middle layer of the software stack "in the cloud."
  • A lot of providers in private IaaSPrivate IaaS Servers are not multi tenantWhen you move to the cloud, how much do you move? The first possibility is an Infrastructure as a Service (IaaS) environment where the networking, storage, servers, and any virtualization resources are handled in the cloud by the Service Provider. It is basically the operating system in the cloud. This takes some of the core infrastructure headaches away, in theory, but leaves much of the environment from the operating system up in the hands of the Subscriber. This level of control is desirable by some, but places a lot of the responsibility in the hands of the Subscriber. Public IaaS providers like Rackspace or Amazon EC2 help companies move core IT infrastructure resources into large, shared, elastic pools of computing power. In addition to moving these to operational expenditures (rather than costly capital investments), this enables IT organizations to outsource commoditized components and focus on value-add. These are excellent goals and many of the main reasons why IaaS is being implemented broadly by companies worldwide.  Private clouds (e.g. Private IaaS) leverage server virtualization to capitalize on the same advantages offered by public clouds. However, they provide greater security, control and customization afforded by dedicated resources.  The primary differentiator then of a private cloud is that it is operated solely for a specific organization, either by the organization itself or by a third party.  Implementation behind a corporate firewall is often vital to ensure data privacy, security and control. Private clouds make good sense for large enterprises that have specific internal IT requirements that public cloud services cannot reliably fulfill, or for companies with application or security requirements that are not compatible with the shared public resource model. Leading hypervisor providers that enable the creation of a private IaaS include VMware, Citrix, Microsoft, and others.
  • How to leverage the infrastruture more. Been there done that.Scaling/elasticty/central control of your entire cloud
  • When you move to the cloud, how much do you move? The first possibility is an Infrastructure as a Service (IaaS) environment where the networking, storage, servers, and any virtualization resources are handled in the cloud by the Service Provider. It is basically the operating system in the cloud. This takes some of the core infrastructure headaches away, in theory, but leaves much of the environment from the operating system up in the hands of the Subscriber. This level of control is desirable by some, but places a lot of the responsibility in the hands of the Subscriber. Public IaaS providers like Rackspace or Amazon EC2 help companies move core IT infrastructure resources into large, shared, elastic pools of computing power. In addition to moving these to operational expenditures (rather than costly capital investments), this enables IT organizations to outsource commoditized components and focus on value-add. These are excellent goals and many of the main reasons why IaaS is being implemented broadly by companies worldwide.  Private clouds (e.g. Private IaaS) leverage server virtualization to capitalize on the same advantages offered by public clouds. However, they provide greater security, control and customization afforded by dedicated resources.  The primary differentiator then of a private cloud is that it is operated solely for a specific organization, either by the organization itself or by a third party.  Implementation behind a corporate firewall is often vital to ensure data privacy, security and control. Private clouds make good sense for large enterprises that have specific internal IT requirements that public cloud services cannot reliably fulfill, or for companies with application or security requirements that are not compatible with the shared public resource model. Leading hypervisor providers that enable the creation of a private IaaS include VMware, Citrix, Microsoft, and others.
  • When an enterprise uses a public PaaS, it is outside of the firewall. The providers are essentially providing a one-size-fits-all solution. This may work for new apps when development is done from scratch. But the first move for most companies will be porting existing apps. Set the variables for secruity and privacy.
  • Global financial services
  • PrivacyHIIPA compliance for data privacy (applications with medical information) – private coudDevelopers don’t have infrastructure nor middleware expertise – paid to code appThey also don’t want to worry about the middlewareThey want all the components and don’t want to have to worry about configuration and dependenciesEliminate hours/days of configuration work
  • Minimize complexity, don’t have the expertise in DevOpsSimpler, faster way to manage application infrastructure for SaaSMinimize time setting up environmentsLack expertise to deploy, host, manage applications in the cloudAvoiding vendor lock-inThey want portablilityAllow to focus on core competencies (coding!)Don’t have DevOps, Don’t have IT your infrastructure experience
  • Managing the complexityThousands of developersThousands of custom applicationsInfrastructure: vSphere, othersLanguages: Java, Python, Perl, othersDatabases: Oracle, Sybase, DB2, SQL ServerChallenge: Migrating existing applicationsMigrating/integrating databasesEnabling self-service for developers to get applications to market fasterReduce IT bottlenecks
  • End with a bold statement on our vision

Transcript

  • 1. Bart CopelandPresident & CEOActiveState SoftwarePatrick ChanezonSenior Director, Developer RelationsVMware
  • 2. Drivers for [Private] PaaSPrivate PaaS vs. Public PaaSIntroduction to Cloud FoundryIntroduction to StackatoUse CasesQ&A, Wrap Up
  • 3. Founded 19972 million developers, 97% of Fortune 1000Development, management, distribution,cloud solutions for dynamic languagesSome Customers
  • 4. SaaS SALESFORCE.COM (Applications) PaaS (ApplicationMiddleware/Platform) IaaS (Infrastructure)
  • 5. Public IaaS Private IaaS Private Corporate Lots of providers IaaS serving Powered by: government, large enterprise, SMB
  • 6. Infrastructure for clouds implemented Public mostly Private increasing
  • 7.  Middleware Operating System Programming Language Modules Frameworks Databases Web servers AutoConfig Seamless Deployment
  • 8.  Worry Free Middleware Dependencies Configurations Deployment Management Coding Less Work
  • 9. Large EnterpriseGovernment(Some) SMBs
  • 10.  NoControl One-Size-Fits-All New Apps Existing Apps Custom/Internal Apps Security Privacy (Compliance)
  • 11.  Reduction IT Config Not “bypassing” IT Automatic Config Migrate Existing Apps And New Apps Faster time-to-market Self-service  utilization of hypervisor $PLUS: Security, privacy of data ALL Within IT control
  • 12. Platforms
  • 13. Platforms Raise the Unit of currency to be application & services instead of infrastructure Google App Engine, Cloud Foundry, Joyent, Heroku, Stax (Cloudbees), Amazon elastic beanstalk, Microsoft Azure, AppFog Single or a few languages, services Start of Multi language Polyglot platforms Enabler for Agile Developers -> Create Business value faster Lack of standards: risk, vendor lock-in Enterprise needs: Control, customizability Private/Hybrid Cloud Avoid lock-in
  • 14. Agility as a survival skill Consumer software is becoming like fashion Phone apps, social apps, short lifetime, fast lifecycles Ab testing Clay shirky situational apps Kent Beck, Usenix 2011 Talk change in software process when frequency grows Cloud Platforms enables an Agile culture, driver for innovation Scalability is built in the platforms Can iterate faster Focus on design
  • 15. Main Risk: Lock-In Welcome to the Hotel California Such a lovely place Such a lovely face Plenty of room at the Hotel California Any time of year, you can find it here Last thing I remember I wasRunning for the door I had to find the passage back To the place I was before “Relax,”said the night man “We are programmed to receive. You can checkout any time you like But you can never leave!”
  • 16. Cloud Foundry: The Open PaaS• Open Source: Apache 2 Licensed• multi language/frameworks• multi services• multi cloud
  • 17. Open Source
  • 18. Open Source Advantage http://code.google.com/p/googleappengine/issues/detail?id=13• https://github.com/cloudfoundry/vcap/pull/25
  • 19. Multi Cloud
  • 20. CloudFoundry.COM Cloud Foundry Runtimes & Frameworks Services vCenter / vSphere Infrastructure
  • 21. Cloud Foundry.ORG Cloud Foundry The Source Code to Compile & Build Cloud Foundry vCenter / vSphere Download Setup Setup Scripts Deploy Environment Behind Code Firewall
  • 22. Micro Cloud Foundry Micro
  • 23. What is a Micro Cloud? Or Entire Cloud Running inside of a single VM
  • 24. What is in Micro Cloud Foundry? .COM Dynamic Updating DNS App Instances Services Open source Platform as a Service project 10.04
  • 25. Other Cloud Foundry powered PaaSPrivate PaaS, added Python and PerlPublic PaaS, added PHPNode.js Community Lead
  • 26. Development LifeCycle
  • 27. Traditional App Deploy and Request/Response Web Request/AllocateWeb Build/Setup Install/Configure App Deploy/TestApp Scale? Upgrade? DBDB Update?
  • 28. How Apps are Deployed on Cloud FoundryWeb Web App “vmc push MyApp” DBApp Scale? “vmc instances MyApp 5”DB Upgrade? “vmc map MyApp MyApp2” Update? “vmc update MyApp”
  • 29. Services
  • 30. Current Services Available on Cloud Foundry
  • 31. Service Creation and Binding App Instance Redis Service MongoDB Service
  • 32. How it works
  • 33. Logical View
  • 34. The cloud platform for creating your
  • 35. 1. Enterprise-ready: commercial supported2. More choice: languages, frameworks, data services3. Hypervisor (IaaS)-agnostic and Portable: from desktop (micro cloud) to private, public, and hybrid clouds4. Migrate existing apps with minimal re-engineering5. Simplicity of PaaS deployment6. End-to-end: push from desktop IDE (Eclipse, Komodo)7. Manage your PaaS: Admin Dashboard8. Enhanced security: multi-tenant LXC containers9. More control: CPU, memory usage10. Monitor performance: New Relic
  • 36. Based on Cloud Foundry open source Python Community Lead for open source project Stackato: commercially supported, hardened Optimized for VMware cloud infrastructure: Runs on vSphere“ActiveState’s Stackato is a great option for enterprises that, forsecurity and other reasons, want the flexibility to create a privatecloud or private PaaS environment.”— Christopher Keene, VP Cloud Computing Ecosystem, VMware
  • 37. Setup & Scale Develop & Deploy Manage & Monitor• Create a AUTO- • Deploy • Manage CONFIGURING NEW, migrating updates, upgrad private PaaS on EXISTING es top of private applications to • Control, monitor cloud or IaaS in the cloud in 3 application minutes steps, < 15 performance minutes
  • 38. IT/Systems Development Teams Administrators/DevOps• Save significant amount of • Faster code to cloud and time in configuration, set-up time to market: eliminate set- up and provision time, move• Respond to business needs apps to cloud in < faster 15 minutes• Greater utilization and ROI • On-demand self-service: out of virtualized Auto provisioning of infrastructure dependencies• Avoid vendor lock-in • Flexibility with choice
  • 39. MinimizeComplexity
  • 40. ManagingComplexity
  • 41. www.activestate.com/cloud @activestate www.cloudfoundry.com @cloudfoundryTry Stackato Beta in the Sandbox (Amazon EC2) or on a micro cloud: http://activestate.com/cloud Try Cloud Foundry: http://cloudfoundry.com/signup Promo code: cfactivestate