Migrating from Amazon AWS to OpenStack

Transcription

1 Migrating from Amazon AWS to OpenStack Steve Curry FOUNDER AND PRESIDENT, METACLOUD, INC.

2 Why? The Pros: Easy start Fully managed Credit card, mouse click, Go! The Cons: Expensive at scale Zero availability guarantees Control

3 Demystified What is an Amazon Compute Unit (CU)? Equivalent CPU capacity of a GHz Opteron or 2007 Xeon processor Amazon CU equivalent: Today's typical 2 socket server Intel Xeon CPUs 256GB of RAM Amazon CUs SPECint / PassMark

4 Pricing Primer VM prices go down Amazon margins go up Server price/performance ratio increases by 50% every two years CUs become CUs More CUs per server = higher margins Public cloud is NOT a commodity it's a high margin business

5 73% of those surveyed are already using the cloud.

6 And the momentum is building

7 and building.

8 With a clear preference emerging for the private cloud.

9 Why Private Cloud? Increase agility Eliminate shadow IT Take advantage of covariant workloads Consolidate distributed IT organizations

10 Commercial vs. Open Source Commercial Software: software in which new features or versions must be viable for their (the software publisher s) business Open Source Software: software in which new features or versions must be viable for YOU or your business

11 Commercial vs. Open Source For example: OpenStack has 11,909 people that have joined and contribute to the community Members from 130 different countries Commercial teams are much smaller and have less opportunity for innovation

12 Why? Other platforms may be easier to setup OpenStack is designed to scale Simply Java vs. Python The community momentum is clear

13 Acquiring OpenStack UPSTREAM LINUX DISTRIBUTIONS W/ OPENSTACK OPENSTACK VENDORS

14 What is? Leader in online video management, publishing, analytics, and monetization Founded: 2007 Headquarters: Mountain View, CA Top Online Video Innovator (Frost and Sullivan, 2013), Red Herring Top 100 Global Winner Major Amazon customer

15 Staffing Considerations Ooyala has a highly-sophisticated in-house IT team Choices: Have them learn OpenStack Hire staff to build, deploy, and manage their cloud Find provider willing to build, deploy, and manage their cloud for them

16 Staffing Considerations Staff requirements: team of specialists (4-6) Hypervisor expert Linux expert Python expert Network engineer Database administrator Downside: Big payroll outlay Approach lacks redundancy

17 Staffing Considerations Alternate solution: Hunt for a unicorn Not an IT guy Must have: All the classic DEVOPS skills A deep understanding of the hypervisor you re going to run A solid understanding of networking and database scalability

18 Metacloud is + + Cloud Operations Metacloud takes the best of OpenStack and enhances it to deliver a fully scalable, highly available, and customizable cloud platform.

19 Carbon OS is A full IaaS platform Integrated compute, storage, networking and identity Based on OpenStack Built for co-variant workloads Customizable Hardware agnostic Zero lock-in

20 Full Lifecycle Cloud Ops 24x7 cloud operations Proactive monitoring and error detection Capacity planning Effortless upgrades Carbon OS feature enhancements OpenStack distribution management Integrated with your team and policies

21 Solution Fully-managed OpenStack-based private cloud from Metacloud Enterprise-grade OpenStack 24x7 operational support, including monitoring, troubleshooting, and upgrades New servers

22 Results Public cloud benefits, private cloud performance Reduced costs No need to hire or train staff Current team remains focused on innovation Long-term multi-public/private hybrid model

23 Considerations Before You Move from AWS to OpenStack Moving data VM images migrations Tools: How do AWS orchestration tools map to OpenStack? Where to locate hardware Foundational infrastructure (network, storage, compute)

24 Considerations Before You Move from AWS to OpenStack Corporate requirements (A/D, LDAP Auth) Software license agreements Integrating the cloud with existing network topology Which hypervisor to use? Which components need to be high availability?

25 Q & A