building blocks for hybrid it

29
#rightscale Building Blocks for Hybrid IT Brian Adler, Sr. Services Architect, RightScale Ryan Geyer, Cloud Solutions Engineer, RightScale April 30, 2013

Upload: rightscale

Post on 20-Aug-2015

437 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Building Blocks for Hybrid IT

#rightscale

Building Blocks for Hybrid IT

Brian Adler, Sr. Services Architect, RightScale

Ryan Geyer, Cloud Solutions Engineer, RightScale

April 30, 2013

Page 2: Building Blocks for Hybrid IT

# 2

#rightscale

Agenda• Definitions and Terminology• Infrastructure Evolution• On-Premises – Key Considerations• Use Cases • Best practices for design and implementation• Hybrid IT – Different things to different people• Customer Use Cases• Conclusion/Q&A

Page 3: Building Blocks for Hybrid IT

# 3

#rightscale

On-Premises Resource Cloud Resource

Page 4: Building Blocks for Hybrid IT

# 4

#rightscale

Application Portfolio

Requirements Filter

Resource Pools

App 1App 2App 3

PerformanceCost

ComplianceGeo-location

Security

Workload Liberation

Management & automation – across cloud resource pools

App N…

App 1App 2App 3

Hosted Private

Public Cloud 2

Public Cloud 1

VendorsExisting DC

App 4App 5

App N…

App 4App 5

Internal Private

Page 5: Building Blocks for Hybrid IT

# 5

#rightscale

Definitions and Terminology

Virtualization (server)Division of one physical server into multiple isolated virtual environments

On-Premises ITA collection of compute, storage, and network resources for a single tenant that are accessed programmatically via an API endpoint.

Cloud ArchitectureA similar set of resources that is multi-tenant and is provided by a cloud vendor with access via an API endpoint.

Page 6: Building Blocks for Hybrid IT

# 6

#rightscale

Definitions and Terminology

Multi-CloudAn environment that spans two or more separate cloud providers.

Hybrid ITAn environment that spans one or more cloud providers as well as one or more on-premises IT environments.

Page 7: Building Blocks for Hybrid IT

# 7

#rightscale

Infrastructure EvolutionOld school Datacenters

• Racks of physical nodes, one application per node• It’s all we knew, it worked, and it was fine.

Virtualization – The Early Years• Capability of a node outgrew the needs of any single application

-Lots of idle resources on each node• Virtualization provided the ability to have a many-to-one (servers per node)

-This was better

Cloud Computing• Automated provisioning and management via an API appears

-This is much, much better

Page 8: Building Blocks for Hybrid IT

# 8

#rightscale

On-Premises IT: Key Considerations

Workload and Infrastructure Interaction• Applications have different resource needs• Choose the right fit for your application and your infrastructure

Compliance • Data may be contained on-premises for compliance needs or requirements.

Latency• Consumers of the on-premises resources are generally “closer” to the

environment, which reduces latency

Page 9: Building Blocks for Hybrid IT

# 9

#rightscale

On-Premises IT: Key Considerations

User Experience• Related to latency, end user experience is enhanced due to proximity to

resources.

Cost• OPEX is generally reduced. (CAPEX is another story )

Page 10: Building Blocks for Hybrid IT

# 10

#rightscale

Use CasesSelf-Service IT Portal (“IT Vending Machine”)

• Users select one of several preconfigured tech stacks• Isolated Test/Dev environments

Page 11: Building Blocks for Hybrid IT

# 11

#rightscale

Demo

Page 12: Building Blocks for Hybrid IT

# 12

#rightscale

Use CasesScalable Applications with Uncertain Demand

• Cloud used as “proving ground” for new applications• Low-demand applications run their course in the cloud until they are

end-of-lifed• Applications that gain traction remain in the cloud during growth phase• When stability of workload is reached, the application is transitioned

into an on-premises environment.

Page 13: Building Blocks for Hybrid IT

# 13

#rightscale

Use CasesDisaster Recovery (DR)

• Production environment in on-premises environment• DR environment in the cloud• Most common configuration is the “Warm DR” scenario

• Replicating slave in the cloud• All other servers in non-operational state

ON-PREMISES

Page 14: Building Blocks for Hybrid IT

# 14

#rightscale

Demo

Page 15: Building Blocks for Hybrid IT

# 15

#rightscale

Design Considerations

Location of Physical Hardware• On-premises

• Availability considerations (power, cooling, networking, etc.)• Hosted or Co-location facility

• Accessibility of hardware for additions and/or modification• Latency to end users• Security

Page 16: Building Blocks for Hybrid IT

# 16

#rightscale

Design Considerations

Availability and Redundancy Configuration• Easiest configuration (single zone, single region, single API endpoint) does not

promote high availability• High Availability of resources requires more complex configurations

Page 17: Building Blocks for Hybrid IT

# 17

#rightscale

Design Considerations/Options

Simple ConfigurationNo HA or Redundancy

HA Configuration

Page 18: Building Blocks for Hybrid IT

# 18

#rightscale

Design Considerations

Intended Workloads and Use Cases• Does the application require high availability or is it tolerant of interruptions of

service?• Does the application require (or greatly benefit from) specialized hardware or

network configurations?

Page 19: Building Blocks for Hybrid IT

# 19

#rightscale

Hardware ConsiderationsCompute

• Commodity• High end/specialized

Networking• Driven by topology, latency demands, and price• Some infrastructure software offerings have support for

network hardware devices (load balancers in particular)

Storage• Cost vs. Performance (commodity? SSD?, etc.)

Page 20: Building Blocks for Hybrid IT

# 20

#rightscale

Software Considerations

Cloud Infrastructure Software• Open source vs. commercial• Dictates/influences other decisions regarding cloud implementation

Cloud Management Software• Abstracts underlying details of the cloud infrastructure offerings• Presents consistent interface to the available resources regardless of the

underlying infrastructure provider• Provides a cloud-portable solution• Provides orchestration tools for provisioning and management

Page 21: Building Blocks for Hybrid IT

# 21

#rightscale

Implementation ProcessHardware Procurement

• Pre-existing or new?

Cloud Infrastructure Software• Research options, and choose wisely!

Cloud Topology• Zones, storage allocation, HA considerations, etc.

Build or Buy• Use in-house resources if expertise exists• Third-party resources

• Build using existing resources• Build using new preconfigured hardware

Page 22: Building Blocks for Hybrid IT

# 22

#rightscale

Management Process

Compatibility• Avoid vendor lock-in at IaaS level, hypervisor level, cloud infrastructure

software level

Unified Control/Security• “Single pane of glass” for user access, keys and credentials, etc.

On-Demand, Self-Service Provisioning• Allow users to access resources without administrative intervention

Focus on Applications• Core competency is in application development, so remove yourself from

image management, automation, provisioning, etc.

Page 23: Building Blocks for Hybrid IT

# 23

#rightscale

Hybrid ITWhat if an application outgrows your on-premises IT environment?

Common desire is for “bursting”• When on-premises resources are exhausted, a server tier expands into the

cloud to tap into the “infinite” resources• Considerations:

• Control – public Internet is traversed• Latency – traversal of public Internet involves the Great Unknown• Cost – bandwidth charges for public Internet traversal• Complexity – setting up a secure environment is not a trivial task

More common use case is each application contained entirely within a single environment whether cloud or on-premise.

Page 24: Building Blocks for Hybrid IT

# 24

#rightscale

Hybrid IT / Cloud Bursting

ON-PREMISES CLOUD

LOAD BALANCERS

APP SERVERS

MASTER DATABASE

SLAVE DATABASE

OBJECT STORAGE

APP SERVERS

PUBLIC INTERNET

Cloud Bursting

Page 25: Building Blocks for Hybrid IT

# 25

#rightscale

Demo

Page 26: Building Blocks for Hybrid IT

# 26

#rightscale

Hybrid IT Customer Example

Results: • Built hybrid architecture with AWS

and CloudStack• RightScale provides unified

management

Challenges: • Customer data residency

requirements in Canada and Europe

“RightScale multi-cloud support enables us to transparently host Coupa [both in the cloud and on-premises] while delivering high availability and data privacy compliance.”

Sanket Naik, Sr. Director, Cloud Operations and Integrations

Page 27: Building Blocks for Hybrid IT

# 27

#rightscale

Hybrid IT Customer Example

Results: • Built hybrid architecture with AWS

and CloudStack• RightScale provides unified

management

Challenges: • Deliver consistent and approved

configurations to developers• Compliance needs for data

residency

Fortune 500 Clinical Laboratory Provider

Created a Self-Service IT on-premises environment alongside AWS.

Use the RightScale IT vending machine to provide developers with standard configurations that can be launched without a ticket, RFS (Request for Service) or a phone call.

Provisioning time takes 15 minutes

Page 28: Building Blocks for Hybrid IT

# 28

#rightscale

Summary/Conclusions• On-premises or hybrid IT was originally thought of as an academic

exercise or science project• Recent advances (particularly in cloud infrastructure software)

have shown hybrid architecture to be viable IT delivery model• Many considerations come into play

• Design• Hardware• Software• Implementation Details

No “one size fits all”• Do your research. Find the right fit.

Page 29: Building Blocks for Hybrid IT

# 29

#rightscale

Resources and Next Steps

1. LEARN: Read our White Paper

http://bit.ly/rswhitepaper

2. TRY: Free Edition www.rightscale.com/free

3. TALK: Visit us at our Booth today

Enter to win $100 Amazon gift certificate

Contact RightScale

(866) [email protected]