Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

(ISM319) What Drives the Need for Application-Defined Management

734 views

Published on

"The typical Forbes Global 2000 enterprise has more than 5,000 applications. Amazon EC2 has more than 54,800 possible instance configurations for a simple three-tiered application. Managing the application lifecycle is challenging due to three interrelated degrees of freedom in the cloud: application proliferation, execution venue diversification, and the increase in the rate of change to one or both of the latter.

Creating rigid, hard-wired relationships between applications and infrastructure simply won’t scale. What’s needed is the ability to abstract up to the application level, define each application’s topology and dependencies, and use this metadata to allow the infrastructure environment to dynamically provision resources based on application criteria. This focus on the application and not just infrastructure is what’s behind application-defined cloud management. Session sponsored by cliQr."

Published in: Technology
  • Be the first to comment

  • Be the first to like this

(ISM319) What Drives the Need for Application-Defined Management

  1. 1. © 2015, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Gaurav Manglik: Co-Founder, CEO October 2015 ISM319 The Three Degrees of Freedom on the Cloud and How an Application-Defined, Model-Based Approach Can Help
  2. 2. Traditional Datacenter • Manually configure • Manually tune • Manually maintain For every: • Application • Infrastructure configuration • Change over time
  3. 3. • Software-defined datacenter  Compute  Storage  Network • Drives infrastructure efficiencies • Still leaves gap between infrastructure and application APIs… SDx Software-Defined Datacenters Are Not Sufficient
  4. 4. Application Workloads Are Growing 200M workloads 5,000 - 10,000 applications/global 2000 enterprise
  5. 5. Application Rate of Change Is Increasing Source 2013 State of DevOps Report Puppet Labs, IT Revolution Press Top Performers 30x more frequent code deployments Of those with DevOps implemented > 12 month: More than 25% can deploy on demand
  6. 6. Number of Execution Venues Is Growing 54,872* Example: Possible combinations to deploy a 3-tier application on AWS assuming 38 instance types * Actual possible options can be much higher
  7. 7. Single Cloud – Application Find the “knee” to optimize value 45 50 55 60 65 70 $0.00 $2.00 $4.00 $6.00 Instance Web Tier App Tier DB Tier M1.Sm M1.Med M1.Med M1.Med M1.Med M1.Sm Baseline M1.Med M1.Med M1.Med M1.XL M1.Med M1.Med Optimal M1.Med M1.XL M1.Sm M1.Med M2.4XL M1.Med Cost per hour ($) Requestspersecond • Optimal – Smaller DB tier, larger app tier • Is 5 requests per second worth going from $0.5 to $1.5 per hour? PetClinic – Three-tier web application
  8. 8. Single Cloud – Batch Job Find the “knee” to optimize value Instance Size C3.8XL C3.4XL Optimal C3.2XL C3.XL Job time minutes Jobcost($) • Note – Optimization limited by AWS per-hour minimum charge Blender – 5 task rendering job $0.00 $0.50 $1.00 $1.50 $2.00 $2.50 $3.00 20 25 30 35
  9. 9. Global average use 4 cloud platforms + 1 out of 8 use 7+ cloud platforms Cloud Reality Check 2015 Report from NTT Communications 1,600 ICT decision makers across the USA and Europe January and February 2015 80% expect that number to increase in next 3 years
  10. 10. Three Degrees of Freedom 1. Growth in applications 2. Growth and diversification in infrastructure environments 3. Changes in either or both the applications or infrastructure create work and inefficiencies
  11. 11. Traditional automation approaches do not scale with the increasing complexity
  12. 12. Example Three-Tier Web Application SAMPLE DEPLOYMENT WORKFLOW 1. Launch DB VM Instance 2. Mount Persistence Storage 3. Configure DB VM Security Groups 4. Launch AS VM Instance 5. Configure AS VM Security Groups 6. Launch LB VM Instance 7. Configure LB VM Security Groups 8. On DB VM, Install DB Server 9. On DB VM, Start DB 10. On DB VM, Load DB 11. Wait for Success 12. Obtain DB information 13. On AS VM, Change DB Settings 14. On AS VM Load Application 15. On AS VM, Start AS 16. Wait for Success 17. Obtain AS Information 18. On LB VM, Change LB Connection Settings 19. On LB Start LB LB AS DB
  13. 13. Infrastructure Requirements May Change SAMPLE DEPLOYMENT WORKFLOW 1. Launch DB VM Instance 2. Mount Persistence Storage 3. Configure DB VM Security Groups 4. Launch AS VM Instance 5. Configure AS VM Security Groups 6. Launch LB VM Instance 7. Configure LB VM Security Groups 8. On DB VM, Install DB Server 9. On DB VM, Start DB 10. On DB VM, Load DB 11. Wait for Success 12. Obtain DB information 13. On AS VM, Change DB Settings 14. On AS VM Load Application 15. On AS VM, Start AS 16. Wait for Success 17. Obtain AS Information 18. On LB VM, Change LB Connection Settings 19. On LB Start LB LB AS DB
  14. 14. Application May Change SAMPLE DEPLOYMENT WORKFLOW 1. Launch DB VM Instance 2. Mount Persistence Storage 3. Configure DB VM Security Groups 4. Launch AS VM Instance 5. Configure AS VM Security Groups 6. Launch LB VM Instance 7. Configure LB VM Security Groups 8. On DB VM, Install DB Server 9. On DB VM, Start DB 10. On DB VM, Load DB 11. Wait for Success 12. Obtain DB information 13. On AS VM, Change DB Settings 14. On AS VM Load Application 15. On AS VM, Start AS 16. Wait for Success 17. Obtain AS Information 18. On LB VM, Change LB Connection Settings 19. On LB Start LB LB AS DB
  15. 15. Changes Can Get Complicated SAMPLE DEPLOYMENT WORKFLOW 1. Launch DB VM Instance 2. Mount Persistence Storage 3. Configure DB VM Security Groups 4. Launch AS VM Instance 5. Configure AS VM Security Groups 6. Launch LB VM Instance 7. Configure LB VM Security Groups 8. On DB VM, Install DB Server 9. On DB VM, Start DB 10. On DB VM, Load DB 11. Wait for Success 12. Obtain DB information 13. On AS VM, Change DB Settings 14. On AS VM Load Application 15. On AS VM, Start AS 16. Wait for Success 17. Obtain AS Information 18. On LB VM, Change LB Connection Settings 19. On LB Start LB LB AS DB Cache DB-2
  16. 16. Consider an Application Blueprint/Model-Based Approach OneHybrid Deploy Lifecycle • Scripts  Everything scripted. Stage. Cloud  Infrastructure focused  Environment specific  Labor intensive • Orchestrators/Workflows  More efficient than scripting  Infrastructure focused  Environment specific  Lifecycle management • PaaS  Application focused, multiple clouds  But less flexibility and customization • Application Models/Blueprints  One platform, profile portability  Manageable ManageabilityCloudsupport PaaS Scripts Orchestrators Application-defined
  17. 17. Application Model–Based Approaches • Define reusable services  E.g. PaaS – Elastic Load Balancing, Amazon RDS, etc.  VM base image–based • Services capture  Service-specific requirements  Service lifecycle scripts  Parameterize infrastructure choices  Infrastructure requirements (but not choices) • Application models become service topologies  With dependency graph  Abstracted from infrastructure choices
  18. 18. Reusable building blocks (services)
  19. 19. Select Infrastructure Choices at Deployment Time
  20. 20. Example Three-Tier Web Application SAMPLE APPLICATION BLUEPRINT STEPS 1. DRAG AND DROP DB 2. POINT TO DB SETUP 3. DRAG AND DROP AS 4. POINT TO APP PACKAGE 5. Connect AS to DB 6. DRAG AND DROP LB 7. Connect LB to AS LB AS DB Actual workflow gets automatically generated as you “peel” the services
  21. 21. Benefits SAMPLE APPLICATION BLUEPRINT STEPS 1. DRAG AND DROP DB 2. POINT TO DB SETUP 3. DRAG AND DROP AS 4. POINT TO APP PACKAGE 5. Connect AS to DB 6. DRAG AND DROP LB 7. Connect LB to AS 1. Rapidly create new models as number of applications increases 2. Infrastructure options flexible 3. Change either easily
  22. 22. Get to AWS Faster 90 minutes vs. 3 weeks Granular control
  23. 23. Agility vs. Control Do IT fast vs. do IT right Run IT like a business - Plan and execute - Stability value - Maximize control Run IT like a startup - Sense and respond - Speed and scale value - Well-defined guardrails Era of Application Velocity
  24. 24. Control access
  25. 25. Demonstration CliQr as an Example of Model-Based Approaches
  26. 26. Thank you! www.cliqr.com
  27. 27. Remember to complete your evaluations!

×