6. 6#
One “Cloud” – Many Resource Pools
London Amsterdam
Chicago Beijing
Seattle
Dublin
Oregon
Seoul
NYC Area
SF Area
Tokyo
DC Area
Fukuoka
Dallas Hong Kong
Hyderabad
Singapore
São Paulo
Private Clouds Public & Managed Clouds
Amazon Web Services Logicworks
Datapipe Rackspace
IDCF / Yahoo! Japan SoftLayer
Korea Telecom Tata
KINX UnGeo
Cloud Management
8. 8#
Configuration Framework
RightScale ServerTemplates™
• Reproducible: Predictable
deployment
• Dynamic: Configuration
from scripts at boot time
• Multi-cloud: Cloud agnostic
and portable
• Modular: Role and behavior
abstracted from cloud
infrastructure
Cloud Management
10. 10#
ServerTemplates
• ServerTemplates define individual servers and/or complete
systems
• More than just instance characteristics … entire system
configuration (e.g., networking, environment variables,
automation settings, server interdependencies)
Cloud Management
11. 11#
First step to nirvana: ServerTemplates
ServerTemplate
Virtual Machine Image
• Chiseled in stone. • Live above the image.
• Painful to change. • Live above the cloud.
• So pre-cloud. • Code your infrastructure.
Cloud Management
12. 12#
ServerTemplates are Server DNA
Cloud Agnostic
One Asset, Multiple Options
Public Cloud
“Web Server”
Private Cloud
Future Cloud
Cloud Management
13. 13#
ServerTemplates
• Dynamic configuration
• Abstract role and behavior
from cloud infrastructure
• Predictable deployment
• Cloud agnostic / portable
• Object-oriented programming
for sysadmins
Cloud Management
14. 14#
What are ServerTemplates?
Anatomy of a Example ServerTemplate
ServerTemplate MySQL 5.0
operations
operations
RightScript/Recipe 6 Initialize slave
… …
RightScript/Recipe 6 Perform backup
RightScript/Recipe N Start all services
… …
RightScript/Recipe 5 Setup DNS and IPs
boot sequence
boot sequence
RightScript/Recipe 4 Restore last backup
RightScript/Recipe 3 Configure/tune MySQL
RightScript/Recipe 2 Install MySQL Server
RightScript/Recipe 1 Install monitoring
Base Image Right Image
Cloud Management
15. 15#
What do ServerTemplates help me do?
• Affect Cloud Resources and specify cloud properties
(image, instance type, ssh key, security groups, etc.)
• “Record” everything you do to set up a server
(install software, edit configuration files, start
services, etc.)
• Extract variable configuration information [as Inputs]
• Define custom monitors and alerts
• Keep versions of your configurations, images, scripts…
• Share best practices within your organization, or to the
world
• Incorporate best practices from others, and receive
updates
Cloud Management
16. 16#
Dynamically Configure with ServerTemplates
Create agile, automated, and predictable IT infrastructure
• Dynamically configure
servers at run-time
• Abstract role and behavior
from cloud infrastructure
• Modular and variable-based
for easy maintenance
• Launch predictable
infrastructure
• Portable
Cloud Management
17. 17#
How does RightScale help with Abstraction?
• Unified Multi-Cloud UI and new API (in progress)
• Multi-Cloud Servers/Arrays
• Multi-Cloud ServerTemplates
• Multi-Cloud Images
1:1 ServerTemplate 1:N I
Image I
Server I
I
I
runnable abstraction software config runtime config cloud resources
Cloud Management
18. 18#
MultiCloud Image
• Collection of RightImages that represent a standard
configuration across multiple clouds
MCI: Windows Server 2008
AWS AP- AWS AP- AWS US- AWS US-
Rackspace AWS EU
Singapore Tokyo East West
Cloud Management
19. 19#
ServerTemplates
Modular – Portable – Reproducible
Application
Applications
• Cloud independent App Libraries
deployment
SQL Server/ASP.NET…
Networking Cloud Portability
• Standard configurations
Storage volumes that work across clouds
RightImages & OS
Multi-Cloud Images
• Standard image Virtual machine
configurations
Cloud Management
21. 21#
Automation Engine
• Monitoring and alerting
• Server and application
• Escalations and triggers
• Auto-scaling
• Operational automation
• Database
backup, failover, recovery
• Script execution
• Code deploys and patches
Cloud Management
22. 22#
Cluster monitoring
• Individual graphs
• Good for a dozen servers
• Displays all standard graphs with full detail
• Stacked graphs
• Displays the contribution of many servers to a total
• Great to see the sum and variability of activity in a cluster
• Difficult to make out individual servers
• Examples: requests/sec, cpu busy cycles, I/O bytes/sec
• Heat maps
• Displays a bar for each server
• Great to see uneven distribution across servers
• Great to quickly spot performance problems across many servers
• Difficult to read absolute values or see the total cluster activity
Cloud Management
28. 28#
Cluster monitoring architecture
• Architecture
• Monitoring front-end servers
pull data from storage servers
• Up to 100 servers on one graph
(to be increased)
monitoring monitoring
storage front-end
servers servers
your servers
Cloud Management
30. 30#
Governance Controls
• Access and security
• Authentication, roles, permissions
• Umbrella accounts and sharing
• Auditing and logging
• Server logs
• Infrastructure audits and tracking
• Usage and cost metering
• Cost tracking and quotas
• Real-time run rate projections
Cloud Management
31. 31#
Control Users & Costs
Maintain IT control & visibility
• Access current and
projected costs by project or
department
• Roll-up and export cost data
• Manage user permissions
• Establish and enforce
corporate standards
• Automate compliance
management
• Maintain audit and log files
Cloud Management
32. 32#
Codify Corporate Best Practices
Achieve operational excellence and execute governance strategies
• Build library of company-
specific best practices
• Preserve corporate learning
• Standardize configurations
and architectures
• Create run books with
associated operational
scripts
• Collaborate and share cloud
computing assets
Cloud Management
33. 33#
Niche Phase
• Share & preserve learning and
best practices for next game
• Maintain the experience with SLA-
based automation ensures users
• Easily migrate “in-house” with
hybrid cloud solutions
Cloud Management
34. 34#
RightScale Accounts
• Each account corresponds to a set
of AWS credentials
• Complete isolation –
reporting, configuration
assets, cost tracking, etc.
• Configurations are easily shared
amongst 2 or more accounts via
Sharing Groups (see slide 9)
• “Enterprise Manager” allows you to
manage multiple account under 1
parent account
Cloud Management
35. 35#
User Roles
• User roles and access rights are
organized “Account down” as
opposed to “User up”
• A user can access 1 or more
environments with different roles
and access rights
• SSO supported
• Users are granted rights by Admin
via invitation process
Cloud Management
36. 36#
User Roles
• Admin – full rights on RightScale; only role that can access
AWS private key material
• Observer – may only observe an account
• Actor – launch / terminate services, run configuration scripts
bundle instance, create volumes, etc.
• Security Manager – only role that may create or edit security
groups (port access; firewall)
• Designer – create ServerTemplates, RightScripts, set Alerts
• Library – import configuration assets from library
Cloud Management
37. 37#
User Roles, continued
• Server-login – only role that may login to servers (SSH)
• Publisher – can publish configuration assets to library; share
configurations via private “Sharing Groups”
• Billing – manage billing info
• Enterprise Manager – access all accounts under Enterprise
Group, grant access, control user roles
• Lite User – limited access to RightScale; may launch pre-
configured systems published to Lite User account
Complete list available at: http://support.rightscale.com/15-
References/Tables/User_Role_Privileges?highlight=user+roles
Cloud Management
39. 39#
Sharing Groups
Account 1 Account 2 Account 3
• Admin can set up private libraries
• Accounts with “Publisher” rights can publish ServerTemplate
configurations into library
• Members of private libraries can access and deploy configurations
• No migration; seamless roll into production
Cloud Management
40. 40#
Visibility
Master Parent Child Accounts
GLOBAL (Master PC
Child #1
EMEA
Parent Account)
PC
Global RS Admin
Manages user accounts Child #2
and ServerTemplates for Each group / PO can have specific
number of accounts / users pre-
Dev.
all branches.
Child #3 associated … and can buy more at
Pricing pre-negotiated corporate rate
Pricing set at Global level
… pre-negotiated rates Child #4
LOB 1
apply to all child accounts
Monthly usage
Child #5 cost, associated to
account and PO-
Infrastructure Audits number
Child #6
User Audits
LOB 2
Cost Tracking Makes separate PO and
Child #7
Single Billing gets charged for specific
additional services (ie
education, more private
Child #8 cloud nodes etc)
Cloud Management
41. 41#
Visibility example: Infrastructure Audit
• Review of all Security Groups or • SSH Key audit analyzes all or
SSH Keys running servers
• Includes audit of all Regions • Store up to 10 audits and use
• Security Group audit analyzes all to baseline
or public ports • Audits can be downloaded as
text or JSON files
Cloud Management
42. 42#
Billing
• RightScale will single bill for RS and AWS fees
• Full support for AWS‟ consolidated billing
• RightScale accepts credit card, wire, ACH, check
• Supports monthly, annual or multi-year invoicing
• Standard Net30 payment terms
• RightScale will mass-provision AWS accounts for customers
Cloud Management
43. 43#
RightScale for Enterprise
• Visibility: Single pane of glass for
public, private, and hybrid clouds
• Cloud-enabled infrastructure:
On-demand, elastic, metered
• Simplified provisioning:
Standardized, enforced
configurations
• Application-aware infrastructure:
Manage systems, not servers
• Vendor freedom: Leave doors open
in a rapidly changing environment
Cloud Management
44. 44#
The Enterprise Path to the Cloud
• Traditional Data Center
• Siloed, over capacity, server sprawl
• Virtualized Data Centers
• Increased consolidation and
standardization
• Automated Hybrid Cloud
• Rapid, elastic provisioning
• Shared resource pools and workloads
• Pay per use
Cloud Management
46. 46#
Use Case: Hybrid Cloud
• RightScale customer since 2009
• Zynga manages their public and private/hybrid cloud (zCloud)
with RightScale – through a „single pane of glass‟
“The zCloud also integrates with the operational and
management tools that have proven critical to our
business, such as RightScale and CloudStack.”
- Allan Leinwand
Zynga CTO – Infrastructure Engineering
Cloud Management
47. 47#
IT and Evolution of Infrastructure
Private / Multi-Cloud
Public + Private
Standardization
Extensible toolset
Visibility
Users Accounts Billing Security
Abstraction / Automation
API / Config Management
Public Cloud
Dynamic/Elastic/Pay per Use
Virtualization
Increase utilization
Consolidation
Physical infrastructure
Traditional IT
Siloed/over capacity/server sprawl
Cloud Management
48. 48#
RightScale’s BioPharma Solutions
Grid Batch
• Independent jobs / Scheduled runs
parallel computing Single or multiple worker
• Single or multiple worker classes
classes
HPC Utility Computing
Complex jobs On-demand access to
Tightly coupled compliant builds
machines Self-service interface
Cloud Management
49. 49#
What is Private Cloud?
• Comprised of one or more datacenters
• Physical Infrastructure that sits behind an API
• May or may not leverage virtualization
• May or may not be hosted by „you‟
• Is available only for your consumption.
Cloud Management
50. 50#
Why Private and Hybrid Cloud?
• Discourage rogue use of Public Clouds
Control • Security and Compliance
• Leverage existing hardware resources
• Integrate with existing systems and
Flexibility processes
• Enable use of specialized hardware
Performance • Configure systems to match workloads
Cloud Management
52. 52#
Benefits of myCloud
Agility & Choice: Choose your cloud infrastructure based on
Application requirements.
Flexibility: Manage application deployments across public and
private clouds; scale on demand.
Control: Securely manage your public, hybrid, and private cloud
deployments from a single Pane of Glass.
Proven: myCloud is based on proven Reference Architectures
with key RightScale partners (Cloud.com, Euca, Openstack).
Cloud Management
53. 53#
Public Cloud Stack
e.g. Web Apps, Dev/Test,
Applications & Data Self-Service, etc
Application Code
RightScale Cloud Middleware Automation
Management Platform OS Image
Rackspace Region
AWS EC2 Region
Public IaaS Clouds
Cloud Management
57. 57#
Use Case: Public to Public
Your Applications
US-East RAX US-West Cloud N
I S
a
a
S a S3 Cloud Files Google Storage N
t g
o e
r
Cloud Management
58. 58#
Use Case: Public to Private
App A App B App C App D
myCloud 1 myCloud 2 US-West RAX
I S
a
a
S a DC1 DC2 S3 Cloud Files
t g
o e
r
Private Cloud Public Cloud
Cloud Management
59. 59#
Use Case: Private to Public
App A App B App C App D
myCloud 1 myCloud 2 US-West RAX
I S
a
a
S a DC1 DC2 S3 Cloud Files
t g
o e
r
Private Cloud Public Cloud
Cloud Management
60. 60#
Use Case: Private to Private
App A App B App C App D
myCloud 1 myCloud 2 US-West RAX
I S
a
a
S a DC1 DC2 S3 Cloud Files
t g
o e
r
Private Cloud Public Cloud
Cloud Management
61. 61#
Cloud Enable Your Infrastructure
Create
myCloud
Account
Choose your
infrastructure
Install your
hardware
and register
Launch
Server
Templates
Automate, Integrate for
monitor & hybrid
manage clouds
Cloud Management
62. 62#
Dev & Test
• Lifecycle Challenges
• Limited, shared resources
• Lead time for procuring and provisioning equipment
• Maintaining consistent environments throughout the lifecycle
• Maintaining multiple environments in parallel
• Distributed teams and team members
Cloud Management
63. 63#
Dev & Test
Available, Easily Provisioned Resources
Cloud Management
64. 64#
Batch Processing / Grid Computing
100%
50%
0%
1-Jan 8-Jan 15-Jan 22-Jan 29-Jan 5-Feb 12-Feb 19-Feb 26-Feb 5-Mar 12-Mar 19-Mar 26-Mar
Resource Utilization
Challenges
• For IT
• High capital investment, typically low capacity utilization
• Scheduling conflicts, constant provisioning
• Specialized architectural and operational skills
• Specialized software applications and unique datasets
• For End Users
• Wait for resources
• Limited to resources available in the datacenter
Cloud Management
65. 65#
Grid Computing in the Cloud
Cloud Computing Model Grid Computing in the Cloud
Resources on Demand Resolves Scheduling Issues
Virtually Infinite Resources Supports Faster Processing
Pay as You Go Matches Costs to Demand
Cloud Management
66. 66#
Cloud-based Grid Computing Use Cases
Pharmaceutical Analysis – Researchers expected a protein analysis comparing 2.5 million
compounds to take a week of processing on internal servers
• Using hundreds of servers, the job was completed in one day
Insurance Claims Loss Control – Systems for detecting fraudulent, improper or duplicate claims
in batches of millions of claims would have required months of processing time to run and millions
of dollars in capital outlay to build in the data center
• Batch runs finished in a few days at significantly lower cost
Web 2.0 – One customer transcodes images to render video on demand
• Processing time was reduced from hours on internal resources to minutes
Financial Data Processing – Back testing environments that analyze data to test new
trading strategies
• Trading strategies analyzed faster and more cost-effectively by scaling out servers
Cloud Management
67. 67#
RightScale Grid / Batch Architecture
Automated server scaling, operational remediation, server cost optimization
RightScale Management Interface
SQS Output Queue
SQS Input Queue
Your SQS Error Queue
code
Amazon S3
Worker
Daemon Amazon S3 Your application or
Batch jobs from next batch process
Your job producer job consumer
application
Scalable cloud servers
using RightScale Server Templates
RightScale Customer code Amazon Cloud Infrastructure
Cloud Management
69. 69#
Why in the AWS Cloud with RightScale?
Extensive experience in large, highly-elastic
single gaming applications
• 600K concurrent users
• 100X scaling in 4 days
• 8,000 instances
• 250K new users per hour
• 0 to 35M unique users in one day
• 1:1000+ data center management ratio
69
Cloud Management
71. 71#
Scalable Web Applications
• Add capacity as demand dictates
• Classic example of “pay as you go” utility computing
• Enables the ability to react to viral and flash-crowd events
without degradation of service
• PaaS solutions exist that can leverage scalability benefits
• Zend Solution Pack
• VMware‟s Cloud Foundry
• Hybrid cloud environments can scale to take advantage of both
public and private clouds
• Zynga‟s Z Cloud is currently the largest hybrid cloud in the world, all of
which is managed through the RightScale platform
Cloud Management
Hinweis der Redaktion
IT has not been involved in that adoption … don’t understand that you need automation on top of images … why image buildingAnyone that is doing anything at size and complexity, you are now tasked with doing that for a portfollio
You might just find exactly what you need.Or you can find snippets of what you need and build it and test it. Finally, we have partners that have put up a lot of the software for you. And they build test it everyday. Open Diff in new tab.Clone LAMP all in one. Rename to Wordpress. Bookmark.Remove continuous backups.Add APP Wordpress configure to bottom of template.Set default inputs on new template.
First, a point to drive home. Live above the cloud. Live above the image. Configure vanilla machines at runtime. The flexibility of the cloud ends at the image.
“Cloud Aware” configuration vs. images or other configuration solutions which are generally only aware of the machine scope
RightScale’s ServerTemplates innovate beyond “machine images,” providing dynamic configuration at run-time – no more post-launch configuration! When a server is launched using a ServerTemplate it automatically configures itself in the context of a deployment running on a specific cloud. It automatically obtains the needed IP addresses, gets the address of and access to storage, checks in with load balancers, submits monitoring data, and collaborates with other servers in the deployment. While some of what our ServerTemplates can do could be programmed into a machine image, RightScale ServerTemplates are designed to do it automatically – no more developing or maintaining custom machine images.To do this, we have designed our ServerTemplates to include:A Base Machine Image which is stripped down to the barest level - the operating system and some hooks to RightScale. RightScale maintains images for each OS and cloud combination. You just select the appropriate combination for your app. Second, Cloud Configurations configure all the cloud specific resources required such as the instance size, storage required, security group, and IP address. Again RightScale maintains these configurations for each cloud. You just need to select the appropriate options.Because of this layer of abstraction, you worry about the server’s role and function, not the underlying cloud-specific infrastructure. The server’s role and function is determined by a series of scripts which you add that can be executed when the server boots, as it is running, or when the server is decommissioned. You select or write the scripts to load the application software, libraries, data … whatever is needed. You can leverage our libraries of ServerTemplates or write your own. They can be written in a number of common scripting languages (shell, bash, perl, ruby, python) or you can use Chef cookbooks and recipes. ServerTemplates are modular and variable-based - all the scripts, executables, and variables are stored outside the template. This makes maintenance much easier; you just need to make one change and it is automatically reflected in all ServerTemplates that use that script, executable, or variable value. This also enables automation. As deployments change, servers reconfigure themselves and new servers launch in the context of the current deployment. We’ll talk more about this on the next slide. ServerTemplates launch servers with the same configuration every time, so you are assured that you get the same predictable result. Finally, because the underlying cloud infrastructure is abstracted from the role and function of the server, ServerTemplates are portable across cloud infrastructure providers.
RightScale already provides several abstractions that are cloud-agnostic. In fact you’re already using probably all of them (despite you might only be deployed in 1 cloud)..We have the concept of a server (something that can be launched/running on any cloud)The concept of a ServerTemplate, which specifies the configuration we want on a serverAnd the concept of an MCI which specifies which image configuration we want (lower-level stuff)And all these things are RS concepts…the cloud is not really involved in all this…
Individual graphs only work for so many servers, they also don’t show what is happening as an aggregateStacked graphs stack the contribution of each server on top of one anotherWalk through what the graph shows
The cluster monitoring is very powerful in that it provides different types of views into the operation of large clusters of servers
Walk through ofhow it works: in any deployment, go to the monitoring tab select servers select metric to plot familiar controls to switch time period and graph size displays one graph per server, here core1.rightscale.com through core8.rightscale.com in this example the graphs show cpu utilization for the past week, where blue is busy time and green is idle
Individual graphs only work for so many servers, they also don’t show what is happening as an aggregateStacked graphs stack the contribution of each server on top of one anotherWalk through what the graph shows
Stacked graphs are great to see the aggregate, but it is often difficult to see abnormal server behaviorHeat maps show many servers on one graph by plotting one horizontal bar per serverThe time axis is the same for all servers and it is shown at the bottom of the graphThe color of the bar shows the value of the metric for the serverWalk through the graphIt’s easy to see that there are 6 servers sharing the load, and two servers that are different
At scale this is how all this looks and comes togetherThis example is real, it shows an incident we had with our monitoring cluster a few months agoThis heat map shows 100 servers out of one of our monitoring clusters (we want to be vague here…)When there are more than 100 servers, the heat map shows a sampling of 100Describe the sampling: most recently launched, longest running, some of each server template, rest randomStory:This heat map plots I/O wait for our monitoring servers on a day where we suddenly received a number of alerts for a few serversThe heap map shows these servers clearly as red bands starting between 7am and 8amSo we could clearly see that something was going on with a small number of servers and that it started more or less at the same time on all themTo see what happened in aggregate, we can switch graph type…
This shows the same incident as on the previous slide, but with a timescale of a weekIt shows the number of servers handled by each monitoring server, i.e. each color bar shows one serverIt is easy to see that some customer launched a large number of servers right at the time the overload beganFurther investigation showed that due to a bug these servers were allocated unevenly across the cluster causing the overload’
The architecture behind the cluster monitoring is rather extensiveCustomer (i.e. your) servers send monitoring data every 20 seconds to our serversThe data points are cached in-memory on those servers and flushed to disk periodicallyCluster monitoring graphs are produced on separate front-end servers, which pull the data from over 100 monitoring storage serversThe graphs are produced using rrdtool and auto-refresh
RightScale’s management platform includes the tools you need to maintain IT control and visibility across multiple users, departments, and customers. It’s easy to associate costs with projects or departments and you can review your month-to-date expenditures at any time and see a projection of expenditures for the entire month. Roll up the cost information for several accounts within a master account and export it as a CSV file for further analysis or import it into your cost accounting system.Within each account, users are assigned permissions ensuring they have all the access they need - but no more. Some users might be able to access a production database, while others cannot. By the end of the year, you will be able to control the RightScale functionality accessible to each account and the users within that account. You might have some users who can only access and deploy ServerTemplates, while other users can create them. We are also delivering capabilities to alert administrators when servers are not in compliance. We monitor each server’s compliance to corporate guidelines set by you and then notify the appropriate administrator when a server violates those guidelines. If deemed necessary, the server can be restored to it’s original, compliant state automatically.And of course, audit files are maintained after servers are decommissioned to ensure you have the data to resolve any issues or breaches.
With RightScale, you build a repository of your company’s best practices, a corporate CMDB (configuration management data base), that not only saves valuable systems administration time, but reduces the number of errors introduced by repetitive or manual processes. With documented best practices it’s easy to achieve operational excellence and execute corporate governance strategies.Whether you choose to centralize development of best practices in one group or distribute it across the organization, you have one central repository for storing all the information about your deployments and a common method of building, testing and deploying applications on the cloud.You can build standard server configurations with ServerTemplates and system architectures with deployments. For example, you might create a standard ServerTemplate to launch a LAMP stack for development or a standard deployment for a website with a redundant MySQL database. Once established these can be used over and over, improving productivity and reliability. By using tested best practices, you achieve predictability in how components and systems are deployed and behave. You can also create run books that address specific events that might occur such as a master database failure with the associated procedures embodied in operational scripts. ServerTemplates, Scripts and Macros can be published to one or more work groups using our sharing group feature. You invite users to participate in a sharing group and gain access to your cloud assets. As these assets are updated, it’s easy to publish new versions and notify users to retrieve and use the updated ones.
These are examples, not the comprehensive list of features
The Grid Processing Solution Pack has everything you need to run a complete, scalable grid application environment in the cloud. The solution is automated, resilient to errors, and 100% auditable. It is a preconfigured framework for deploying grid processing in the cloud that leverages Amazon’s Elastic Compute Cloud (EC2), SQS (Simple Queue Service) and S3 (Simple Storage Service) capabilities to process large numbers of jobs in a scalable and cost efficient manner. The Grid Solution Pack hides the “plumbing” of any operations specific to AWS so that the grid application can be plugged in with minimal effort.
Orchestrates and automates Amazon Web ServicesS3, SQS Queues, EC2 ServersMultiple AWS Regions and Availability ZonesRapid and repeatable deployment solutionsPre-configured environments for graceful provisioning/de-provisioningAutomation, scaling and remediationError handling, logging and reportingBest practices architecture with consultative support