Building Clouds with Apache CloudStack - the business use-cases


Published on

Giles Sirett , CEO of ShapeBlue did a talk on the Business Use cases for Apache Cloudstack, looking at what’s driving organisations to build IaaS cloud infrastructures and also why those organisations are choosing Apache Cloudstack ahead of other technologies.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

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

No notes for slide
  • End of day So we’ll start gentlyHopefully something for everyonePlease bear with me if seems obvious to you.Bear with my english accent and phrases/terminologyBasics and more advanced ideasPaul AngusEngineering and Science degreesCloudStack 2.13
  • Do it as a quizSome people add on “must be on internet”
  • Across nearly all of our metrics
  • In this cloud era we are toldDespite how much engineering you do it will failSebastien Buemi escapes 200mph crash unhurt in ShanghaiSwiss, youngApril 2010
  • Cloud : modern, expects things to go wrong…if things get busy, he just sorts it out himeselfTraditional: We don’t like this guy, but he wont go away. relies on his staff, expects everything to work. If things get busy, its somebody elses problem
  • Storage, networking, overall architects technical and managerialEverything is interconnected and feels like everything relies on everything elseSomeone chipping in can be invaluable – particularly if they have past experience.
  • Building Clouds with Apache CloudStack - the business use-cases

    1. 1. The business Use-Case’s for building clouds with Apache CloudStack Giles Sirett CEO & Managing Consultant ShapeBlue Twitter: @ShapeBlue @ShapeBlue
    2. 2. #whoami? CEO of ShapeBlue “ShapeBlue are expert builders of public & private clouds. They are the leading independent global CloudStack / CloudPlatform integrator & consultancy” Involved in Apache Community, Chairman of European CloudStack user group, always talkin’ CloudStack Close relationship with Citrix Technical enough to be dangerous A unique insight….. @ShapeBlue
    3. 3. Enterprises Service Providers @ShapeBlue
    4. 4. Vendor tied End to end vCloud Director Microsoft System Center Abiquo OnApp Flexiant Hexagrid Open communities CloudStack OpenStack Opennebula Eucalyptus Your orchestration must be open to survive @ShapeBlue
    5. 5. Only CloudStack & OpenStack will survive @ShapeBlue
    6. 6. But why CloudStack Giles ? “It just works” @ShapeBlue
    7. 7. But why CloudStack Giles? @ShapeBlue
    8. 8. “CloudStack is part of OpenStack, right ?” @ShapeBlue
    9. 9. 275 @ShapeBlue
    10. 10. CloudStack Users @ShapeBlue
    11. 11. CloudStack Users 2.0 @ShapeBlue 11
    12. 12. CloudStack Users 3.0 @ShapeBlue 12
    13. 13. The obligatory cloud definition slide Self Service Resource pooling Rapid Elasticity Metered Use @ShapeBlue
    14. 14. On-demand self-service is a cloud driver Organisations are virtualised = cap/op ex savings However, operationally often still manual Still often a service ticket to provision new resources Long delivery times Relatively high operational costs Relies on specialist skills Margin for human error @ShapeBlue
    15. 15. Resource pooling is a cloud driver Make the most of a global compute estate Resources dynamically assigned according to demand Workloads can be averaged: across departments, across Geos, across times of day, days of month, etc By pooling resources, reduces the reliance on local capacity planning Abstracts physical resources @ShapeBlue
    16. 16. Measured service is a cloud driver The The XaaS model allows accurate cost measurement Compute Storage Network etc Internal chargeback model much simpler “Shadow IT” can be removed @ShapeBlue
    17. 17. Rapid elasticity is a cloud driver Scale up Scale back Autoscaling Burst capabilities WORKLOAD PORTABILITY @ShapeBlue
    18. 18. So, todays use-case’s are… Service Provider / public cloud Devops automation AWS insourcing Traditional enterprise workloads @ShapeBlue
    19. 19. Use case 1 of 4 - Service provider / public cloud $2,400,000,000 @ShapeBlue
    20. 20. August 2012 = 90% public cloud vs other use cases August 2013 = 50/50 split @ShapeBlue
    21. 21. Use case 2 of 4 - Devops Deploy my code Only on my infrastructure @ShapeBlue
    22. 22. Use Case 2 of 4 - Devops Rapid agility demanded by business Automate, script, automate, script, automate, script EVERYTHING needs infrastructure @ShapeBlue
    23. 23. Use Case 3 of 4 – “AWS Insourcing” usage 35 30 25 20 15 10 5 0 usage @ShapeBlue
    24. 24. Use Case 3 of 4 – “AWS Insourcing” usage 35 30 25 20 15 10 5 0 usage Known demand @ShapeBlue
    25. 25. Use Case 3 of 4 – “AWS insourcing” I realise that AWS is costing too much for my known demand I need to know my tooling will work I need to use the same API I still want to burst to AWS I don’t want to get into a massive/complicated project @ShapeBlue
    26. 26. Use Case 4/4 – Enterprise adoption @ShapeBlue
    27. 27. Use Case 4/4 – Enterprise adoption In 2013, we are seeing enterprises doing one of the following: adopt public cloud build private cloud align with public clouds (technology, process, standards) CloudStack has a unique position in the enterprise @ShapeBlue
    28. 28. Failure happens – Get used to it “The car was not a problem. I just lost both wheels." @ShapeBlue
    29. 29. “I have two types of workload” “Failure happens”? – no thanks Cloud Era workload Traditional workload @ShapeBlue
    30. 30. Traditional Workloads Traditional workloads Traditional n-tier applications Scale & reliance handled by the infrastructure Scale by “scaling up” Infrastructure expected to be always available @ShapeBlue
    31. 31. Cloud Era workloads Cloud era workloads Applications designed for failure Applications designed for massive scale Scale by “scaling out” (horizontally) How can an enterprise benefit from both models ? @ShapeBlue
    32. 32. Enterprises will adopt a 2 workload model Private Cloud @ShapeBlue
    33. 33. Questions? @ShapeBlue @ShapeBlue