Going to the Cloud

Going to the Cloud Keys to achieving 'the Cloud'. 

From Virtualization to Orchestration.

Presenter: Jim LepiankaSession Number: 307

Code PaLOUsa 2011 Sponsors

Code PaLOUsa 2011 Sponsors

Keys to achieving 'the Cloud'.  From Virtualization to Orchestration.  Getting to the cloud is as much a mystery as what to do once there. We will discuss the types of clouds, the 4 steps to get there and what we can do now to prepare your enterprise for the leap.

4

Going to the Cloud

Agenda

Before We Begin

Cloud Overview

Steps to get to the Cloud

Lessons Learned

5

Cloud DefinitionDefinition• Cloud computing is a pay-per-use model for enabling available, convenient, on-demand network

access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. This cloud model promotes availability and is comprised of five key characteristics, three delivery models, and four deployment models.

Key Characteristics• On-demand self-service - SaaS - Public• Ubiquitous network access - PaaS - Community• Resource pooling - IaaS - Private

• Location independence - Hybrid• Homogeneity

• Rapid elasticity• Measured service

6

Source: Peter Mell & Tim Grance – National Institute of Standards and Technology – Information Technology Lab

XaaS, the concepts included in the Cloud

7

• EaaS, Everything as a Service, the transformation of IT from a physical, well established environment into a

capability that is available at people’s fingertips without knowledge of where the assets are.

• SaaS, Software as a Service, an environment where users can run predefined applications directly from their

web browser.• PaaS, Platform as a Service, an environment in which

the user is provided with a rich environment in which he can run his applications as long as they are

programmed in one of the languages supported by the platform (Java, Python or .Net)

• IaaS, Infrastructure as a Service, an environment that provides the user with processing power, networking,

storage and the other necessary resources allowing him to run his software and applications

4 Cloud Deployment Models

8

Private Cloud• Enterprise owned or leased

Community Cloud• shared infrastructure for specific community

Public Cloud• Sold to the public, mega-scale infrastructure

Hybrid Cloud• composition of two or more clouds

Source: Peter Mell & Tim Grance – National Institute of Standards and Technology – Information Technology Lab

Before We Begin

Cloud Overview

Steps to get to the Cloud

Lessons Learned

9

IT is undergoing disruptive change

1 0

IT wants Google/Amazon like agility and efficiency as an on-premise or hosted private cloud Services increasingly

span many physical, virtual and external resources

Composite Service

Aspirations for private cloud

Business needs technology to enable innovation quickly and now has more options beyond its own IT org…… as “services”, not technology, with clear understanding of capabilities and cost

Physical Virtual IaaS PaaS SaaS

TraditionalMSP

IT is expanding its role to include supply chain manager

…but obstacles are complicating progress

1 1

•Cannot build from scratch•Siloed, open-loop provisioning•Hardwired application stacks Business vulnerable from

security, data and monitoring blind spots across composite services

Composite Service

Aspirations for private cloud

Business going around IT•Unmonitored and unsecured•Can’t answer “How do we compare”?•Hollowing out IT’s perceived value

Physical Virtual IaaS PaaS SaaS

TraditionalMSP

Cannot measure vendor delivery against service levels, business impact unknown

!

!

!

?

? ? ?

? ?

First moves must be driven by service understanding and decision making

1 2

•Closed loop service automation•Service assembly, reusable infrastructure•Run-time provisioning and scaling

End-to-end security and assurance of composite services

Composite Service

Private Cloud

Fact-based decision support for in-sourcing and cloud-sourcing decisions, driving real-time optimization

Physical Virtual IaaS PaaS SaaS

MaaS

Measure service levels of external providers and their impact to your composite services

Assured and secured virtual and physical resources

Before We Begin

Cloud Overview

Steps to get to the Cloud

Lessons Learned

1 3

4 Key StepsConsolidate• Consolidate Applications and Services through Virtualization• Leverage Composite Services instead of individual services

Optimize• Pair Virtualization with management• Integrate Lifecycle Management disciplines• Integrate Management across domains and spaces

Automate• Provisioning of services through Templates• Reservations are created on demand• Automation always scales; people do not

Orchestrate• Dynamically instantiate and decommission VMs based on user load • Monitoring captures and fires alerts; Monitor the entire system not just parts• Capacity for configuring, managing and reporting

1 4

Virtualization + Automation + Service Management = Cloud

04 March 2011

Infrastructure delivery models

1 5

On-premisescustomer-owned data center

Off-premisesService provider’s data center

Cloud “Internal” cloud:Cloud platform used to develop and deliver tech-enabled services hosted in customer data center

“Private” & “Public” Clouds:Cloud platform used to develop and deliver tech-enabled services (with or w/o restrictions)

Shared Resources shared / flexed across workloads

Service providerShares/flexed resources across workloads of multiple customers.

Dedicated Resources dedicated to each workload

Co-location, multi-client data center. Resources dedicated to each workload.

04 March 20111 6

Dedicated resources

Shared resources

A A A A A A

A A

AA

A A

AA

SS

SS SS

SS

SSS

On premisesCustomer-owned data center

Off premisesService provider’s data center

Cloud services

S

Aapp

server

Sservice

Key

•

•

Before We Begin

Cloud Overview

Steps to get to the Cloud

Lessons Learned

1 7

•

•

Lessons Learned• Monitor the entire system; not just parts• Only use standards; stay away from Proprietary systems• Reengineer the architecture around Virtualization instead

of dropping it in and then expecting 100% of the benefits• Lower costs by removing hardware and the related support

costs− Multitenency is the best way to drive down cost and attain ROI

1 803/04/11

•

•

Lessons Learned• Make your services consumable : − Prioritize based on business requirements− Consumerize by providing you catalog; must cover all businesses

not just your cloud services• Maintain Security – Define your requirements before

looking for vendors− data at rest/encryption− Country where data will reside, local laws− Monitoring/ 3rd Party Auditing and certifications

• Cloud is as much about process and policy as it is about technology

1 903/04/11

•

•

Lessons Learned• Organizations struggle to maintain low to no value

applications; perform Application Rationalization and define your Service Catalog

• You cannot control things you do not know about; Catalog your offerings

• Ensure you can point to every server in the Datacenter and you know:− What is running on it− Who is responsible− What happens when it fails

2 003/04/11

•

•

Lessons Learned• There is no big bang approach to get to the cloud; start

small and grow• Metrics will need to be tested, refined, implemented,

refined further and re-implemented long after the implementation phase closes

• A knowledgeable partner can reduce time loss due to forgotten steps (like implementing technology only to be forbidden by policy)

2 103/04/11

•

•

Questions

2 2