RightScale Conference Santa Clara 2011: What is the cloud and how do you manage it? Uri Budnik will discuss the cloud technology landscape and where RightScale fits in to drive agility, cost, and time savings above cloud infrastructure. RightScale has been investing heavily for the past four years to make cloud infrastructure easy to leverage. This session will clarify elements that are straightforward, what continues to be difficult, and the impact on your schedule and budget.
Streamlining Python Development: A Guide to a Modern Project Setup
5 Cloud Commandments - Why Cloud Management Makes Sense
1. 1
5 Cloud Commandments:
Why Cloud Management
Makes Sense
Uri Budnik (@uribudnik)
Director, ISV Partner Program, RightScale
Watch the video of this presentation
2. 2#
Agenda
• What is Cloud
• Why Cloud Management
• 5 Cloud Commandments
• It Has Been Built
Real Cloud Experience. Shared.
3. 3#
What do we mean by Cloud?
• Cloud is a metaphor for
complexity that does not
need to be managed
• The edge of the Cloud
serves as a point of
demarcation
• The concept of utility
based computing goes
back to the 60s*
• James Urquhart** calls
it an application centric
operations model
*John McArthy **Wisdom of Clouds Blog and Cisco
Real Cloud Experience. Shared.
4. 4#
What’s Driving Cloud?
• Four horsemen
• Cut costs
• Improve agility
• Increase scale & reliability
• Leverage best practices
• Highly effective layers of abstraction
• SaaS – cloaked below the browser
• PaaS – cloaked below the code
• IaaS – cloaked below the OS
• Each layer achieves scalability &
reliability through uniformity
• True IaaS clouds are API-driven
Real Cloud Experience. Shared.
5. 5#
Cloud computing – A transition of IT
Adoption
Demand (user competition)
Utility
(cost of doing business)
Service
(outsourced)
Product
(feature differentiation)
Custom build
(componentization)
Improvement (supply competition)
Innovation
Time
Framework adapted from Steven Wardley, Canonical
Real Cloud Experience. Shared.
6. 6#
Cloud computing – A definition
Cloud computing is a transition of IT:
• Delivery models – Packaged hardware & software Web & API-
accessed
• Business models – License fees Utility usage fees
• Sales models – High touch Self-checkout
• Business processes – Centralized IT Self-service provisioning
Ingredients:
• Idea – A computing utility (1966)
• Technology – Bandwidth, commodity hardware, virtualization (2000s)
• Attitude – Lean startup, outsourcing, cost savings (2000s)
Popularized:
• SaaS - Salesforce (1999)
• IaaS - Amazon Web Services (2006)
• PaaS – Heroku, Engine Yard (2007)
Real Cloud Experience. Shared.
7. 7#
So what’s the problem?
• Paying attention to design
• Using cloud != designing for cloud
• Accidental tourist in cloud
• Sign up, launch servers, sit back
• Good cloud design
• Secure
• Reliable
• No lock-in
Real Cloud Experience. Shared.
8. 8#
The DIY Trap
• Most clouds are a set of APIs
and/or a simple UI to launch
servers – is that what you need?
• These are basic building blocks, not a management system
• How should you spend your time?
• Managing multiple users with different levels of access
• Configuration management and app lifecycle management
• Track usage and costs across applications and business units
• All the general purpose things you need to do like:
Monitoring, Alarms, Auto-scaling, etc
What do you do about IT or development personnel unilaterally
opening a cloud account and deploying an environment?
Real Cloud Experience. Shared.
9. 9#
Why Cloud Management Makes Sense –
The 5 Cloud Commandments
1. Thou shalt automate
2. Thou shalt go forth and
reproduce cloud server
environments
3. Thou shalt control and have
visibility of cloud resources
4. Thou shalt covet many
clouds
5. Thou shalt architect for
scalability and fault
tolerance
Real Cloud Experience. Shared.
10. 10#
Commandment #1
1. Thou shalt automate
2. Thou shalt go forth and
reproduce cloud server
environments
3. Thou shalt control and have
visibility of cloud resources
4. Thou shalt covet many
clouds
5. Thou shalt architect for
scalability and fault
tolerance
Real Cloud Experience. Shared.
11. 11#
Management is biggest component of TCO
IDC - Virtualization 2.0 - Dec 2006
Real Cloud Experience. Shared.
12. 12#
Cost savings means admin efficiency
Site Architectural
Management Engineering
Software Total Total Server-to-admin ratio is an
Development 7% 8%
Total
7%
indicator of admin costs
• Inefficient operations as low
Requests as 20:1
Total
6% • Above average ratio 150:1
(enterprises typically 70-140)
Deployment
Overhead
Total
Management • Best practices over 2,000:1
Total
11%
31%
(some customers achieve this)
Problem Savings on admin costs of
Engineering
Total easily 50%
10% Incident
Management
Total
20%
Source: Deepak Patil, GFS 2006
Real Cloud Experience. Shared.
15. 15#
Commandment #2
1. Thou shalt automate
2. Thou shalt go forth and
reproduce cloud server
environments
3. Thou shalt control and have
visibility of cloud resources
4. Thou shalt covet many
clouds
5. Thou shalt architect for
scalability and fault
tolerance
Real Cloud Experience. Shared.
16. 16#
Cloud Ready Solutions
“RightScale the Latest to Provide App Store for Infrastructure”
by Derrick Harris
Real Cloud Experience. Shared.
17. 17#
ServerTemplates: Reproducible servers
on demand
Configuring servers Configuring servers
through bundling images: with ServerTemplates:
Custom MySQL 5.0.24 (CentOS 5.2)
Custom MySQL 5.0.24 (CentOS 5.4)
MySQL 5.0.36 (CentOS 5.4) Setup DNS and IPs
boot sequence
MySQL 5.0.36 (Ubuntu 8.10)
A set of configuration
Restore last backup
MySQL 5.0.36 (Ubuntu 8.10) 64bit
directives that will install
Frontend Apache 1.3 (Ubuntu 8.10) Configure MySQL
and configure software on
Frontend Apache 2.0 (Ubuntu 9.10) -patched top of the base image
Install MySQL
CMS v1.0 (CentOS 5.4) Server
CMS v1.1 (CentOS 5.4) Install monitoring
My ASP appserver (windows 2008)
My ASP.net (windows 2008) – security update 1 Base Image
My ASP.net (windows 2008) – security update MultiCloudImage
8
Very few and basic
SharePoint v4 (windows 2003) – 32bit
SharePoint v4 (windows 2003) –64bit
CentOS Ubuntu
Win 2003
SharePoint v4.5 (windows 2003) –64bit 5.2
CentOS 8.10
Ubuntu
Win 2007
… 5.4 9.10
Real Cloud Experience. Shared.
18. 18#
ServerTemplates – Reproducible servers
on demand
VS.
Integrated approach that puts together all the parts needed to
architect single & multi-server deployments
Real Cloud Experience. Shared.
21. 21#
Commandment #3
1. Thou shalt automate
2. Thou shalt go forth and
reproduce cloud server
environments
3. Thou shalt control and have
visibility of cloud resources
4. Thou shalt covet many
clouds
5. Thou shalt architect for
scalability and fault
tolerance
Real Cloud Experience. Shared.
22. 22#
Maintain control while remaining flexible
• Monitoring
• Logs + audit entries
• Alerts & escalations
• Last access
• User management
• Authentication
• Roles, permissions
• Multiple accounts
• Accountability
• Cost tracking & usage quotas
• Real-time run rate projs.
Real Cloud Experience. Shared.
23. 23#
Visibility example: Infrastructure Audit
• Review of all Security Groups or • SSH Key audit analyzes all
SSH Keys or running servers
• Includes audit of all Regions • Store up to 10 audits and use
• Security Group audit analyzes to baseline
all or public ports • Audits can be downloaded as
text or JSON files
Real Cloud Experience. Shared.
25. 25#
Commandment #4
1. Thou shalt automate
2. Thou shalt go forth and
reproduce cloud server
environments
3. Thou shalt control and have
visibility of cloud resources
4. Thou shalt covet many
clouds
5. Thou shalt architect for
scalability and fault
tolerance
Real Cloud Experience. Shared.
26. 26#
Why you should care about multi-cloud
• Multi-cloud scenarios
• Within / between public clouds
• Public / private hybrid
• Lock-in dangers
• Data has mass
• Vendor contracts, features & APIs
• High availability and disaster recovery
• What you should do
• Preserve multiple choices for any service
• Keep contracts to length you can predict
• Avoid unique services & APIs
• Anticipate moving – set up small footprints elsewhere
• Pilot a private cloud
• Design for portability: architecture choices matter
Real Cloud Experience. Shared.
27. 27#
Take advantage of many resource pools
London Amsterdam
Chicago Beijing
Shanghai
Dublin
Seattle
Seoul
NYC Area
SF Area
Tokyo
DC Area
Fukuoka
Dallas Hong Kong
Hyderabad
Singapore
Houston
Private Clouds Public & Managed Clouds
Amazon Web Services Rackspace
Datapipe SoftLayer
Yahoo! Japan / IDCF Tata
Korea Telecom UnGeo
Logicworks
Real Cloud Experience. Shared.
28. 28#
It’s a multi-cloud world
• Not all clouds are created equal
• Once upon a time there was the expectation that a clear Linux
top choice would emerge
• Clouds will proliferate and companies will differentiate to
compete
• Keep your options open,
…like she does
Source: FailBlog.org
Real Cloud Experience. Shared.
29. 29#
Commandment #5
1. Thou shalt automate
2. Thou shalt go forth and
reproduce cloud server
environments
3. Thou shalt control and have
visibility of cloud resources
4. Thou shalt covet many
clouds
5. Thou shalt architect for
scalability and fault
tolerance
Real Cloud Experience. Shared.
32. 32#
RightScale enables multi-provider high
availability
ServerTemplates provision and configure
RightImages for cloud servers are
instances ―in-context‖ automatically
specific to the cloud/region
Real Cloud Experience. Shared.
34. 34#
There is no need to build this yourself;
RightScale has built the ark
5 Cloud Commandments
Visible &
Reproducible Controlled Multi-cloud
Scalable &
Automated
Fault Tolerant
Real Cloud Experience. Shared.
35. 35#
RightScale links the cloud ecosystem
Users Content
Clouds Services
Real Cloud Experience. Shared.
37. 37#
―We want to use clouds, not
build them‖
— Adrian Cockcroft, Netflix Infrastructure Team
Source: Qcon San Francisco 2010 Presentation
Real Cloud Experience. Shared.
Not all companies are this bigDatabase failover analogyMovie and tracking shot analogy
RS has 160 people working on this
Don’t reinvent the wheel
Easily reproducible – One-click to cloneConsistency across servers–ServerTemplates
Not just for individual machines but for complete environmentsUse Zend Solution Pack example
These are examples, not the comprehensive list of features
Roach motel – you can check in and never check out
Use linux analogy here
Differences to clarify from Multi-AZ…Don’t be fooled by similarity of appearance…Some resources are not shared across clouds (images, Elastic IPs and Snapshots)…These are problems you have to solve… Images we have made easyElastic IPsyou need a global load balancer somewhere… or use DNSHave to copy the data yourself for snapshots. You can have a replicating slave in the cloud…Or backups to a common place like S3 (constraint is that EBS snapshots are only good in the same AZ)To get a snapshot multi- cloud portable you 1) slave sync or 2) take LVM snapshots and upload the data somewhere
RightScale'sServerTemplates allow you to capture best practices for provisioning and automating cloud infrastructure. In this breakout session, we will explore how you can leverage the RightScale platform to share ServerTemplates with others. Specifically, we'll walk through the steps to share and update ServerTemplates across your organization. We'll also show you how to publish ServerTemplates publicly for the whole world to use. This topic is best for: IT members who are responsible for maintaining server configurations within the organization, developers who would like to share work product within their group or ISVs wishing to reach cloud users by publishing through RightScale.