Upload
kenneth-hui
View
398
Download
2
Tags:
Embed Size (px)
Citation preview
Building Next Generation Clouds With OpenStack
Kenneth HuiEMCApril 14, 2015
Agenda
• What Is The Cloud (Really)?
• Where Does OpenStack Fit?
• Characteristic Of Cloud-Native Applications
• Building Clouds With OpenStack
In The Beginning… There Was Central IT
Virtualization Made Things Better
But With Software Driving Innovation…
I Want My Apps Now!
The Internet Of Things Is Coming
Same Old Way = Failure
A New Way Of Doing IT
The Value of AWS
COST SAVINGSOPERATIONAL
EFFICIENCY SELF SERVICESPEED AND
AGILITYINNOVATE
AND COMPETE
Winning Over Developers
But We Already Have Our Own Cloud!
Starting tomorrow, our five year old virtualization farm will be called a private cloud
But Is It Really?
An AWS Alternative Comes Along
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
Ceilometertelemetry 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
Should I Run Legacy Apps In OpenStack?
Here’s The Truth…
Match Workload To Architecture
Cloud-Native Applications Are Different
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
Cloud-Native Apps Need To Scale
At Scale Unexpected Failure Happens
So Design For Failure
Let The Application Handle Its Resiliency
Use Loosely Coupled Components
Scale Out Not Scale Up
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
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
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
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?
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
Thank You