CCA - NoDerivs 3.0 Unported License - Usage OK, no modifications, full attribution* * All unlicensed or borrowed works retain their original licenses OpenStack Architected Like AWS (and GCP) Randy Bias, Founder & CEO OpenStack Juno Design Summit May 14th, 2014 @randybias OpenStack’s future is hybrid to public clouds
A description of how we built Open Cloud System (OCS), an OpenStack-powered complete cloud operating system. With a focus on AWS and GCE interoperability, we describe why hybrid cloud interoperability matters and how we got there. Anyone can do it and we think you should too.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
CCA - NoDerivs 3.0 Unported License - Usage OK, no modifications, full attribution*!* All unlicensed or borrowed works retain their original licenses
OpenStack Architected Like AWS (and GCP)
Randy Bias, Founder & CEO!OpenStack Juno Design Summit!
Hybrid Cloud Enables Biz AgilityTop public clouds are elastic!Elastic clouds have similar attributes!
essentially they share a “reference architecture”!
Agility is primary value for enterprise!Cloud native apps + DevOps drive agility!
they “route around failures”!
Elastic cloud is ideal platform for these apps!doesn’t matter if it’s private or public!
Businesses need choice -> hybrid cloud
14
1
2
3
4
5
6
Hybrid Cloud Interoperability
Hybrid Cloud Value Proposition
16
Application Portability ~ Independence!Move apps between clouds with impunity!Advanced capabilities such as Cloud-bursting/bridging!Future-proofing and reduction of vendor lock-in!Pick the right cloud for the job!!
Portability Requires Interoperability!API compatibility is a subset of what is required!!
Interoperability Is NOT Easy!(details to follow)
Pub Cloud Interop Matters
17
Private Clouds Must be Interoperable with Public Cloud Leaders
OpenStack’s Future is Hybrid
API Compatibility is Not Enough
18
Mac TruckInfiniti G37!
330 HP!270 lb ft torque!5 Second 0-60
600 HP!2,100 lb ft torque!60 Second 0-60
Different Behavior
Semantics & Architecture
Engine
Transmission
Braking
Suspension
Lighting
Same API
19
Hybrid Cloud Interop Requirements
1
2
3
4
5
6
Matching SLAs & Availability
Performance & QoS Guarantees
Infrastructure Feature Parity
Similar TCO / Economies of Scale
API Compatibility
Behavioral Compatibility
Hybrid Cloud Interop Requirements
20
Shared Requirement Public / Private Cloud Interoperability DetailMatching SLAs and Availability Guarantees
VM uptime (hypervisor availability) API endpoint availability
Storage system availability
Performance & QoS Guarantees
VM vCPU, networking & local storage performance Block storage system performance matching
Object storage aggregate throughput
Infrastructure Feature Parity
Must have a majority of same primary features AWS -> EC2, S3, EBS, VPC, ELB
GCP -> VMs, persistent block/object, virt. networks, etc.
Similar Cost Economics & Economies of Scale
Within ½-2x of wholesale costs/pricing TCO must be similar, particularly for operational costs
API Compatibility Support for public cloud APIs At the least: AWS, GCE, Azure, and OpenStack
Behavioral Compatibility
Implied, non-API behavior is same or similar example 1: VMs start in <30 mins
example 2: floating/elastic IP auto-assignment
1
2
3
4
5
6
Enable a Hybrid-first Cloud Strategy
21
HYBRID CLOUD
PUBLIC CLOUDPRIVATE CLOUD
Interoperability means !APIs, QoS, SLAs, TCO, Feature Parity & Same Behavior
AWS Flavored!OpenStack
AWS Interoperable OpenStack
23
1
2
3
4
5
6
Matching SLAs & Availability
Performance & QoS Guarantees
Infrastructure Feature Parity
Similar TCO / Economies of Scale
API Compatibility
Behavioral Compatibility
Matching SLAs & Availability Guarantees
24
1
HA Pair Failover / Master Election
Service Service
vs.
Load Balancing
Service1 Service2 Service3 ServiceN...
Active Passive
Active Active Active Active
With Load Balancing, the control plane scales as the cloud grows
Delivers a 99.999% Uptime APIs & Control Plane on 99.5% Hardware
25
Performance & QoS Guarantees
Spread First Scheduling
m3.2xl
c3.xl
r3.xl
c3.mm1.l
Gaps = Wasted I/O & Hardware Resources
t1
t1
t1m1.m
Bin Packing Scheduler1) fixed proportions of resources!2) all resources allocated 3) manage oversubscription rates!4) ensures Quality of Service (QoS)!5) easy to do w/ filters & host-aggregates
2AWS/GCP-Style Instance Sizing & Scheduling
Bin Packing Scheduling(by Instance Family)
m3.xl
m3.2xl
m3.xl
m3.2xl
m3.2xl
Matching Infrastructure Feature Parity
26
3
Infrastructure Application!Services
PaaS / !Orchestration
Route53
Applications WorkSpacesApp Marketplace
CloudFrontRDS DynamoDB
ElastiCacheRedshift
SimpleDB
EMR Kinesis Data Pipeline
Elastic Beanstalk
CloudFormation OpsWorks
AppStream CloudSearch
SWFSQS SESSNS
Elastic Transcoder
Core Infrastructure Services
EC2 EBS S3VM Import/Export
Auto Scaling
CloudWatchClassic Networking
VPC Networking
Mgt Console IAMCLI
ELB
Matching Infrastructure Feature Parity
27
3
Core Infrastructure Services
EC2EBS
S3
IAMAuto ScalingCloudWatch
Classic NetworkingVPC Networking
Mgt ConsoleCLI
ELB
Nova
Swift
Heat Auto Scaling
LBaaS
L2/L3 Nova NetworkingNeutron SDN Plugin
Horizon
Cinder
KeystoneCLI
Heat Monitoring
VM Import/Export Glance
#1 Cost = Servers!#2 Cost = Power!#3 Cost = Network!!!!!Use industry standard servers & build a cattle cloud (one NIC, one switch, one PSU, etc) reduces costs significantly!
Similar TCO & Economies of Scale
28
4What is required to meet Amazon’s cost structure?