Weitere ähnliche Inhalte
Kürzlich hochgeladen (20)
7 steps-to-deploying-a-private-cloud-130124153611-phpapp02
- 1. 7 Steps to Enterprise
Cloud “Heaven”
Rich Wolski
CTO
Eucalyptus Systems
© 2013 Eucalyptus Systems, Inc.
- 2. 3 approaches to on-prem IaaS
CLOUD (APPS)
APPROACH DATACENTER
APPROACH
IaaS
SERVICE PROVIDER
APPROACH
© 2013 Eucalyptus Systems, Inc.
- 3. The Apps Perspective:
Services are the Infrastructure
• IaaS is really backwards
– Infrastructure is really an application component
• Resources are really API and QoS
– No idea “what” hardware is actually being used
• Cloud platform is the unifying framework
– The services interact to provide complete infrastructure
functionality regardless of underlying hardware
• Users, applications, operating systems, and data sets
“touch” only the services
– Hardware becomes peripheral and interchangable
© 2013 Eucalyptus Systems, Inc.
- 4. Step 1 – Understand the
Application Workload
• Application workload characteristics
– Cloud abstractions
• Compute
• Network
• Storage
• Identity
– Deployment requirements for the application
• Reliability
• Load balance
• Geographic distribution (e.g. regulatory)
© 2013 Eucalyptus Systems, Inc.
- 5. Step 2 – Understand
Application Governance
• Who owns the application workload?
– Different than who owns the code
• Must design a way for the cloud administrators to “see”
what the application is doing and to “talk” to the workload
owners
• Software ecosystem
© 2013 Eucalyptus Systems, Inc.
- 6. Step 3 – Design the Physical
Deployment
• The cloud is a control plane
– Once the apps are running, the cloud is out of the “way”
• Imagine, after the apps are deployed, that the cloud
control plane vanishes for an instant
– Will the apps survive?
• VM capacities, network design, storage requirements
© 2013 Eucalyptus Systems, Inc.
- 7. Step 4 – Design the Cloud
Deployment
• Private cloud is a scalable service venue
– Many cooperating service components requiring network,
storage, and compute
• High-availability and redundancy
• Traffic planning
• Memory requirements for cloud components
© 2013 Eucalyptus Systems, Inc.
- 8. Step 5 – Test everything and
then test it again
• Figure or merit testing should be worst case
– Test failures
– Test upgrade
– Test failures during upgrade
– Test upgrade during failures
• Observe the testing results from the application
perspective
– What does the application experience if the cloud is
degraded?
© 2013 Eucalyptus Systems, Inc.
- 9. Step 6 – Integrate cloud with
existing management policies
• The cloud is a new platform
– Not a set of independent tools
• Capacity planning
• HW budgeting
• Racking
• Identity management and security
• Coordination of scheduled down time
– Who gets called?
© 2013 Eucalyptus Systems, Inc.
- 10. Step 7 – Lifecycle planning
• Plan to build incrementally
• Plan to hybrid incrementally
– Internal: Cloud and non-cloud components need to interact in
the data center
– External: Enterprise cloud and public clouds
• Plan to sunset incrementally
© 2013 Eucalyptus Systems, Inc.
- 11. Eucalyptus
• Elastic Utility Computing Architecture Linking Your Programs
To Useful Systems
• Web services based implementation of elastic/utility/cloud
computing infrastructure
– Linux image hosting ala Amazon
• How do we know if it is a cloud?
– Try and emulate an existing cloud: Amazon AWS
• Functions as a software overlay
– Existing installation need not be altered
• Open Source
– Built from best-of-breed Open Source technologies for
eCommerce
© 2013 Eucalyptus Systems, Inc.
- 12. Architecture
Client-side API
Translator
Cloud Controller
Database Walrus
CC
Cluster Controller
Node Controller
NC
SC
ESX
vSphere ESXi RHEV-M
ESX
ESX ESX
ESXi Storage Controller
© 2013 Eucalyptus Systems, Inc.
- 14. Three Production Use Cases
• eCommerce company
• Social gaming company
• Telco
© 2013 Eucalyptus Systems, Inc.
- 15. eCommerce Company
• Highly varied web content
• Transaction processing
• Eucalyptus administration via internal network only
© 2013 Eucalyptus Systems, Inc.
- 16. eCommerce Deployment
Load Balancer
CLC
Corporate network
Walrus 192.168
CC CC
SC SC
10.0
10x 10x
NC NC
© 2013 Eucalyptus Systems, Inc.
- 17. Social Gaming Company
• High interactivity rate
• Churn in the application population
– New games
– Sunsetting games
• Test/dev/ops and user access
– Game development and ops are outsourced
© 2013 Eucalyptus Systems, Inc.
- 18. Social Gaming Deployment
10G
CC CLC
SC Walrus
2x10G
DB x12
36x1G
36x1G
36x
4x1G iSCSI
NC SAN
© 2013 Eucalyptus Systems, Inc.
- 19. Telco
• Modular QoS
– Scalable QoS units
• Bandwidth optimized
• Port-cost controlled
© 2013 Eucalyptus Systems, Inc.
- 20. Cloud Service Modules
• Front End Unit
48 – 48 ports 10G
CLC
iSCSI – 16 cores
SAN – 32GB RAM
Walrus
– Dual NIC
– SAN
• Middle End Unit
32 – 32 ports 10G
SC
iSCSI – 16 cores
SAN CC – 32 GB RAM
– Dual NIC
– SAN
32
• Back End Unit
NC – 32 ports 1G + 2x10G up
30x – 8 cores
– 64 GB x30
– 1 NIC
© 2013 Eucalyptus Systems, Inc.
- 21. ~500 VMs
48 CLC
iSCSI
SAN Walrus
32 SC
iSCSI
SAN CC
32 NC
30x
32 NC
30x
© 2013 Eucalyptus Systems, Inc.
- 22. ~5000 VMs
Front End
ME ME ME ME ME
x5
© 2013 Eucalyptus Systems, Inc.
- 23. ~50000 VMs
Front End
ME ME ME
© 2013 Eucalyptus Systems, Inc.
- 26. Learn More
Overcoming Public and Private Cloud
Uncertainty with Monitoring
Next Webinar: Feb 5 at 2pm GMT and Feb 7 at 2pm EST
www.eucalyptus.com/webinar
Do More
Download Eucalyptus FastStart
Deploy your own private cloud in minutes.
www.eucalyptus.com/faststart
© 2013 Eucalyptus Systems, Inc.