Automating Cloud Operations: Tips from Managed Services

AUTOMATING CLOUD OPERATIONS:

TIPS FROM MANAGED SERVICES

Panelists

• Javier Hernandez

• Manager, RightScale Managed Services

• Josh Fraser

• SVP

• The Challenge of CloudOps

• Supporting Diverse Workloads

• The Role of Templates

• Scale through Automation

• Self-Healing your Cloud Applications

• Integrating with 3rd Party Systems

Agenda

2

RightScale to Manage Any Resource Pool

Self-Service Cloud Analytics

Universal Cloud Management Platform

Cloud Management

Multi-Cloud Orchestration

3

Governance

Public

Clouds

Private

Clouds

Virtual

Servers

Bare Metal

Servers

THE CHALLENGE OF

CLOUDOPS

Companies Using Hybrid Cloud

# of Clouds Used Public Clouds

All respondents

Private Clouds All respondents

Running applications 1.5 1.7

Experimenting 1.5 1.3

Total 3.0 3.0

Average # of Clouds Used

Each Cloud Is Different

7

• Support the particular approach their “customer” wants to

take?

• Support multiple clouds plus virtual and bare-metal servers?

• Offer self-service cloud access while maintaining control?

• Scale efficiently as more applications move to the cloud?

How Does CloudOps…

ALIGN APPROACH WITH

DESIRED OUTCOME

Adoption Levels for Any Workload

10

Govern

Connect creds for:

• Workload visibility

• Organize and tag

• Cost visibility & controls

• Access controls

• Basic provisioning

Enable with agent for:

• Lifecycle operations

• Operational scripts

• Audit trails

• Managed login

• Automated provisioning

Use monitoring for:

• Alerts & escalations

• Self-healing

• Event-triggered actions

• Lifecycle management

Existing workloads

New workloads

Your Portfolio of Workloads

Govern 1 Manage 2 Automate 3

Existing workloads Existing workloads

New workloads

11

Features Level 1:

Govern

Level 2:

Manage

Level 3:

Automate

Workload Visibility ✓ ✓ ✓

Organize and tag resources ✓ ✓ ✓

Cost visibility & controls ✓ ✓ ✓

Access controls ✓ ✓ ✓

Basic provisioning ✓ ✓ ✓

Lifecycle operations ✓ ✓

Operational scripts ✓ ✓

Audits trails ✓ ✓

Managed login ✓ ✓

Automated provisioning with templates ✓ ✓

Alerts & escalations ✓

Automated lifecycle management ✓

Event-triggered provisioning and operations ✓

CloudOps Capabilities Summary by Level

ENABLE DIVERSE

ENVIRONMENTS VIA

TEMPLATES

Cloud Application Templates

13

Load Balancers

App Servers

Master DB Slave DB

Replicate >

DNS

Configure a system: Cloud Application Template (CAT)

Configure a server: • ServerTemplates (portable)

• Docker container (portable)

• AMI

• CF

• VM template

Multi-Cloud, Multi-Service Orchestration

Cloud Application Template

Cloud Compute

Cloud Storage

Cloud Network

Images

Templates/Contain

ers

PaaS Services

IaaS+ Services

Web Services

Define

Resources

Control

User Options Orchestrate Deployment

Enable

Operations

Code

IaaS Resources Extended Services Application Assets

14

ServerTemplates

15

AWS Azure Google CloudStack OpenStack vSphere

Multi-Cloud Image

Configuration Scripts Containers

ServerTemplate Standardization

• Automate provisioning and

configuration

• Version-controlled

• Follow standards for

versions, patches and

configuration

• Leverage a variety of

scripting languages

• Modular and auditable

Portability through Multi-Cloud Images

Cloud-Specific Images

AWS Azure Google

AWS Azure Google

AWS Azure Google

AWS Azure Google

Multi-Cloud Images

Referenced by ServerTemplates.

Pulls the image for each cloud.

Specific to each cloud. Located in each cloud.

Used by the Multi-Cloud Image (MCI)

16

SELF-SERVICE

(WITH CONTROL)

Increase Innovation

• Catalog of templates that

meet corporate standards

• Orchestrate and automate

deployment and

operations

• Policy controls

• Clouds

• Resource types

• Schedules

• Cost quotas

• Security / compliance

• Integrates with ITSM

via REST API

Curate a Catalog of Templates

18

Use Policies to Control Options

19

Give Developers Automated Operations

20

SCALE THROUGH

AUTOMATION

1. Provision accounts

2. Set up user access

3. Define & implement tagging scheme

4. Define alerts (beyond “standard”)

5. Define escalation paths

6. Automate “runbooks”

7. Test “runbooks”

Steps to Onboard New Customers/Apps

Standardize Alerts

Escalations

Self-Service Healing and Self-Healing

INTEGRATED PROCESS

Integrating with Customer Processes

27

Customer

Ticketing

System

RightScale

CMP Platform

Cloud User

RightScale

Managed Services

(CloudOps)

Call

Ticket

Customer IT

IaaS

Provider

3rd Party

Operational

Scripts, Actions

Alerts &

Escalations

Zendesk Pingdom

• Contact us to learn how to get started

• [email protected]

Q&A