Talk presented at OpenStack Live 2015

1. Building Next Generation Clouds
With OpenStack
Kenneth Hui
EMC
April 14, 2015

2. Agenda
• What Is The Cloud (Really)?
• Where Does OpenStack Fit?
• Characteristic Of Cloud-Native Applications
• Building Clouds With OpenStack

3. In The Beginning… There Was Central IT

4. Virtualization Made Things Better

5. But With Software Driving Innovation…

6. I Want My Apps Now!

7. The Internet Of Things Is Coming

8. Same Old Way = Failure

9. A New Way Of Doing IT

10. The Value of AWS
COST SAVINGS
OPERATIONAL
EFFICIENCY SELF SERVICE
SPEED AND
AGILITY
INNOVATE
AND COMPETE

11. Winning Over Developers

12. But We Already Have Our Own Cloud!
Starting tomorrow, our five
year old virtualization farm
will be called a private cloud

13. But Is It Really?

14. An AWS Alternative Comes Along

15. The OpenStack Project
Horizon Dashboard
Swift
object store
Glance
image store
Nova
compute node
Cinder
volume service
Neutron
networking
Trove
database
S3 EC2 EBS vPC RDSAMI
Cloud
Formation
IAM
Heat
Orchestration
Keystone
identity service
Ceilometer
telemetry service
• Currently 14 integrated projects within OpenStack
• All these projects communicate via public API’s
• Quite a few new projects focused on Management and Operations
• Services have behavioral compatibility with AWS

16. Should I Run Legacy Apps In OpenStack?

17. Here’s The Truth…

18. Match Workload To Architecture

19. Cloud-Native Applications Are Different

20. Choose The Right Platform
Operator Controlled IT Processes
HYBRID
Traditional IT Processes Developer Controlled IT Processes
• Monolithic Applications
• Workloads Scale Up
• Applications Expect Resilient
Infrastructure
• Infrastructure Provides Resiliency
• High Degree of Virtualization
• IT Operational Processes Largely
Unchanged
• Monolithic Applications
• Workloads Scale Up
• Applications Assume Resilient
Infrastructure
• IT Process Automation –
Accelerate/Automate IT Processes
• More Agile IT
• More Agile DevOps Focus
• Apps Loosely Coupled, Small
Components
• Stateless Execution Modules
• Application Takes Responsibility of
Resiliency, Fault Tolerant.
• Assume High Data Resiliency
• Workloads Easily Scale Out
• DevOps Focus
PLATFORM 2 PLATFORM 2.5 PLATFORM 3
Virtualized Traditional IT Automated Virtualized
Traditional IT
Elastic IT

21. Cloud-Native Apps Need To Scale

22. At Scale Unexpected Failure Happens

23. So Design For Failure

24. Let The Application Handle Its Resiliency

25. Use Loosely Coupled Components

26. Scale Out Not Scale Up

27. Treat Your Servers Differently
• Instances are disposable
• Instances are homogeneous
• Tune and groom your applications
• Shoot and replace your instances
• Instances have short shelf-life
• Servers are valuable
• Servers have unique names
• Tune and groom your servers
• Spend hours fixing broken servers
• Servers have long shelf-life
Pets Cattle

28. How Do I Use OpenStack To Build My Cloud?
• Do It Yourself
– Build up an OpenStack engineering team
– You own management of your own distribution
• Choose and Partner with a distribution vendor
• Choose and deploy a turnkey solution

29. OpenStack Reference Architectures
• Provide customers a choice to build OpenStack based cloud.
• Partner with leading OpenStack distributors and service integrators.
• Certified EMC OpenStack drivers on the distributions.
• Integrate with partner tools to enable better manageability.
• Provide validated reference designs
• Joint services and support
Storage Arrays
Certified & Validated
Designs
Partner Tools
Integration
Cooperative
Support
Joint Services
EMC

30. Integrated OpenStack
What if…
• You could run AWS in your own data center?
• What if turning on your cloud just meant rolling in a
turnkey solution?
• The core cloud platform was open sourced?
• If the software was integrated with hardware to
enable full-stack orchestration and management?

31. Takeaways
• Cloud is mainly about innovation and agility
• Virtualization != Cloud
• Your workload should match your architecture
• Clouds like OpenStack are designed for distributed apps
• Host cloud-native apps that are designed to handle failures
• Choose the OpenStack consumption model that fits your
use case

32. Thank You