More Related Content
Similar to Comparing Cloud platforms and tools
Comparing Cloud platforms and tools
- 1. COMPARING CLOUD PLATFORMAND TOOLS Om Maniyar Sameer Abrol
- 2. Agenda • Hard Problems •Cloud Components • Evaluation Approach
- 3. WHAT ARE TOP3 HARDEST PROBLEM YOU HAVE?
- 4. Hard Problem: CapacityManagement 3 out of 4 cases it is going to be wrong. We tend to build in the Safe to Wasteful zones Above. Doing it right requires Extreme Agility.
- 5. Capacity management • Capacitymanagement • Has been a hard problem across the industry • Highly underutilized infrastructure • Typical average CPU usage is 10%-20% • Higher utilization is key to infrastructure investment ROI • Multi tenancy and Resource pooling is a necessity to increasing utilization • Usage metering and billing become very important in resource pooled environments
- 6. Infrastructure Management • Managingdisparate resources spread all over the globe is a hard problem • How do you get visibility into all the resources you have? • How do you maximize capacity utilization? • How do you react to changing demands quickly? • How do you manage across your own resources and public cloud? • How do you do this in near real time? Need A Good infrastructure management Platform
- 7. Migration into futurestate • Current legacy • Legacy processes • Tools • Skills • Need to run current business while evolving to future state • Need to maintain SLA Invest/innovate in new while running current platform!
- 8. CLOUD – WHATIS IT TO YOU?
- 9. Cloud capabilities NIST definitionof cloud • On Demand Self-Service • Resource pooling • Rapid Elasticity and Scalability • Usage metering and Chargeback • Universal access
- 10. Key components ofcloud
- 11. Cloud Components and Services H/W &Virtualization = Engine Cloud Services = Chassis, Body Management Tools = Dashboard, controls, Steering wheel Security Monitoring User Interface MultiTenancy Recovery Self Service Provisioning Hypervis or Cloud Platform
- 12. Typical challenges • Many ResourcePools • • • • • • • Bare metal Virtualized Public Cloud Possibly private cloud Lack of comprehensive visibility Lack of governance due to direct consumption Lack of standardization THINK BIG! THINK HOLISTICALLY!
- 13. Evaluation Approach • DetailedRFP for evaluation (akin to Job Description) • Operational and functional use cases • Business & Technical success criteria • Pricing • Score RFP (akin to short list candidates) • Conduct POCs (akin to onsite interviews) • Setup Demo/POC environments • Execute use cases on working platform. Seeing is believing. Create options! Options provide negotiation power.
- 14. Use case areas •Tenant Management • Create a private cloud and register a Tenant • Assign granular access to cloud services for a User/Tenant including quota limits • Service Management • Self-Service Portal/API • Service Catalog • Provisioning • Create Instances of different sizes and types • Automation of creation/provisioning of cloud, Instances and Services • Multi-Tenancy through Security Groups • Scalability • Auto Scale out/down
- 15. Use case areas •Orchestration • Automate server builds • Automate application deployment workflows • Metering • Track Usage of service • Cloud based pricing showback/chargeback • Monitoring • Infrastructure and App Monitoring • Resource Utilization • Asset Management • Ease of adding/removing cloud resources • Resource view across all clouds. • High Availability • Shared storage/Share-nothing live migration • Auto migration of instances
- 16. Single Pane Management • Inventoryof all assets in all locations • • • • • • Physical Virtualized Public Visibility into workloads running Visibility into resource Utilization Consolidate underutilized resources
- 17.