By leveraging a hybrid model that encompasses both on-premise resource utilization and cloud computing, organizations can deploy applications to the most appropriate resource pools, making themselves more agile and saving money. In this presentation at AWS Summit San Francisco, RightScale Senior Services Architect Brian Adler describes the factors that organizations must consider when they create a hybrid model that uses AWS services. He shares a detailed reference architecture for hybrid clouds, covers the preferred use cases for the allocation and utilization of on-premise and cloud computing resources, and reviews technologies available to seamlessly manage hybrid IT infrastructure.

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

2. #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

3. #3
#rightscale
On-Premises ResourceCloud Resource

4. #4
#rightscale
Application
Portfolio
Requirements
Filter
Resource
Pools
App 1
App 2
App 3
Performance
Cost
Compliance
Geo-location
Security
Workload Liberation
Management & automation – across cloud resource pools
App N
…
App 1
App 2
App 3
Hosted Private
Public Cloud 2
Public Cloud 1
Vendors
Existing DC
App 4
App 5
App N
…
App 4
App 5
Internal Private

5. #5
#rightscale
Definitions and Terminology
Virtualization (server)
Division of one physical server into multiple isolated virtual
environments
On-Premises IT
A collection of compute, storage, and network resources for a single
tenant that are accessed programmatically via an API endpoint.
Cloud Architecture
A similar set of resources that is multi-tenant and is provided by a
cloud vendor with access via an API endpoint.

6. #6
#rightscale
Definitions and Terminology
Multi-Cloud
An environment that spans two or more separate cloud providers.
Hybrid IT
An environment that spans one or more cloud providers as well as
one or more on-premises IT environments.

7. #7
#rightscale
Infrastructure Evolution
Old 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

8. #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

9. #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 )

10. #10
#rightscale
Use Cases
Self-Service IT Portal (“IT Vending Machine”)
• Users select one of several preconfigured tech stacks
• Isolated Test/Dev environments

11. #11
#rightscale
Demo

12. #12
#rightscale
Use Cases
Scalable 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.

13. #13
#rightscale
Use Cases
Disaster 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

14. #14
#rightscale
Demo

15. #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

16. #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

17. #17
#rightscale
Design Considerations/Options
Simple Configuration
No HA or Redundancy
HA Configuration

18. #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?

19. #19
#rightscale
Hardware Considerations
Compute
• 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.)

20. #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

21. #21
#rightscale
Implementation Process
Hardware 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

22. #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.

23. #23
#rightscale
Hybrid IT
What 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.

24. #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

25. #25
#rightscale
Demo

26. #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.”
SanketNaik, Sr. Director, Cloud Operations and
Integrations

27. #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

28. #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.

29. #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) 720-0208
sales@rightscale.com
www.rightscale.com