Do you want to turn your existing data center into a private cloud? Exploring how to integrate your private cloud with a public cloud? In this webinar, we will discuss key considerations when designing a private cloud from internal resources and best practices for architecture of private and hybrid clouds. The webinar will include a demonstration, plus real-world examples of customers running their private cloud implementations on Citrix CloudPlatform using RightScale. Topics to be covered: • When to use private clouds • Hardware selection • Reference architectures and design considerations • Use cases and real-life scenarios • Managing your cloud resources effectively

1. Partner Logo
Building Blocks for
Private and Hybrid Clouds
March 21, 2013

2. Partner Logo
Your Panel Today
-Brian Adler, Sr. Services Architect,
RightScale
-Vijay Tolani, Private Cloud Specialist,
RightScale
Please use the “Questions” window to ask
questions any time!

3. Partner Logo
Agenda
Definitions and Terminology
Infrastructure Evolution
Private Cloud Key Considerations
Hybrid Clouds – Different things to different people
Use Cases for Private and Hybrid Clouds
Best Practices for Private/Hybrid Cloud Design and
Implementation
• Design Considerations
• Hardware Considerations
• Software Considerations
• Implementation
• Management
Conclusion/Q&A

4. © 2012 Citrix | Confidential – Do Not Distribute

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

6. Definitions and Terminology
Virtualization (server)
• Division of one physical server into multiple isolated virtual environments
Private Cloud
• A collection of compute, storage, and network resources for a single tenant
that are accessed programmatically via an API endpoint.
Public Cloud
• A similar set of resources that is multi-tenant and is provided by a cloud
vendor with access via an API endpoint.
Multi-Cloud
• An environment that spans two or more separate clouds, be they both
public, both private, or one (or more) of each.
Hybrid Cloud
• An environment that spans one or more public clouds as well as one or
more private clouds.
© 2012 Citrix | Confidential – Do Not Distribute

7. 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)
relationship
• This was better
Cloud Computing
• Automated provisioning and management via an API appears
• This is much, much better
© 2012 Citrix | Confidential – Do Not Distribute

8. Private Cloud Key Considerations
Workload and Infrastructure Interaction
• Applications have different resource needs
• Choose the right fit for your application and your infrastructure
Security
• Data may be contained within the private cloud, thus allowing for stricter
security compliance
Latency
• Consumers of the private cloud resources are generally “closer” to the private
cloud, which reduces latency
User Experience
• Related to latency, end user experience is enhanced due to proximity to
resources.
Cost
• OPEX is generally reduced. (CAPEX is another story )
© 2012 Citrix | Confidential – Do Not Distribute

9. Hybrid Clouds
What if application outgrows the private cloud?
Common desire is for “cloud-bursting”
• When private cloud resources are exhausted, a server tier expands into the
public cloud to tap into the “infinite” resources
• Considerations:
• Security – 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 multiple clouds in an organization, with multiple
applications, and with each application contained entirely within a single
cloud.
© 2012 Citrix | Confidential – Do Not Distribute

10. Hybrid Cloud Bursting
PUBLIC
INTERNET
LOAD BALANCERS
APP SERVERS APP SERVERS
MASTER DATABASE
SLAVE DATABASE
OBJECT STORAGE
PRIVATE CLOUD PUBLIC OR PRIVATE CLOUD
Cloud Bursting
© 2012 Citrix | Confidential – Do Not Distribute

11. Use Cases
Self-Service IT Portal (“IT Vending Machine”)
• Users select one of several preconfigured tech stacks
• Isolated Test/Dev environments
© 2012 Citrix | Confidential – Do Not Distribute

12. Use Cases
Self-Service IT Portal (“IT Vending Machine”)
• Demo
© 2012 Citrix | Confidential – Do Not Distribute

13. Use Cases
Scalable Applications with Uncertain Demand
• Public cloud used as “proving ground” for new applications
• If applications fail, they are allowed to run their course in the public cloud until
they are end-of-lifed
• If an application gains traction, it remains in the public cloud during its growth
phase
• When stability of workload is reached, the application is transitioned into the
private cloud
© 2012 Citrix | Confidential – Do Not Distribute

14. Use Cases
Disaster Recovery (DR)
• Production environment in one cloud
• DR environment in a second cloud
• Most common configuration is the “Warm DR” scenario
• Replicating slave in a second cloud
• All other servers in non-operational state
• Failure of production environment requires promotion of slave to master,
launching of “standby” servers, and DNS reassignment
© 2012 Citrix | Confidential – Do Not Distribute

15. Design Considerations
Location of Physical Hardware
ᵒOn-premise
• Availability considerations (power, cooling, networking, etc.)
ᵒHosted or Colocation facility
• Accessibility of hardware for additions and/or modification
• Latency to end users
• Security
Availability and Redundancy Configuration
ᵒEasiest configuration (single zone, single region, single API endpoint) does
not promote high availability
• Outage of API endpoint renders entire cloud unavailable
• Power issues affect entire pool of resources
ᵒHigh Availability of cloud resources requires more complex configurations
• Multiple zones, multiple regions (if possible/practical)
• Multiple API endpoints
• Redundant and segregated power and networking
© 2012 Citrix | Confidential – Do Not Distribute

16. Design Considerations/Options
Simple Configuration
HA Configuration
No HA or Redundancy
© 2012 Citrix | Confidential – Do Not Distribute

17. Design Considerations
Intended Workloads and Use Cases
ᵒDoes the application require high availability or is it tolerant of interruptions of
service?
• User-facing will most likely require HA.
• Batch processing tasks may not.
ᵒIs flexibility of the infrastructure required for test-beds and/or proof-of-
concepts?
• Potential topologies and hardware options will be affected/limited
ᵒDoes the application require (or greatly benefit from) GPUs or other
specialized processors?
ᵒDoes the application have high IOPS demands?
ᵒAre low-latency or high bandwidth interconnects required?
© 2012 Citrix | Confidential – Do Not Distribute

18. Hardware Considerations
Compute
ᵒCommodity
• Allows for easy addition of capacity
• Easy swap-out of failed components
ᵒHigh end/specialized
• May be required for intended workloads
• Limits available options
• Increases costs
• Complicates maintenance
Networking
ᵒDriven by topology, latency demands, and price
ᵒSome cloud infrastructure software offerings have support for network
hardware devices (load balancers in particular)
Storage
ᵒCost vs. Performance (commodity? SSD?, etc.)
© 2012 Citrix | Confidential – Do Not Distribute

19. Software Considerations
Cloud Infrastructure Software
ᵒCloudStack /CloudPlatform
• Open source vs. commercial
ᵒDictates/influences other decisions regarding cloud implementation
ᵒAccess to resources
• Web interface
• API
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
© 2012 Citrix | Confidential – Do Not Distribute

20. Implementation Process
Hardware Procurement
ᵒPre-existing or new?
• Pre-existing limits ability to tailor infrastructure to workloads
Cloud Infrastructure Software
ᵒThis decision will dictate/limit many future decisions
ᵒ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
© 2012 Citrix | Confidential – Do Not Distribute

21. 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.
© 2012 Citrix | Confidential – Do Not Distribute

22. RightScale’s Hybrid-cloud Engine at work
Zynga’s zCloud
• Concept to production in < 6 months
• Built on commodity hardware
• Supports no less than thousands of physical servers
• Can (and have) fully provisioned over 1,000 physical servers in less than 24
hours
• Integrated with RightScale
Source: Zynga CTO – Infrastructure; InterOp, May 2011
© 2012 Citrix | Confidential – Do Not Distribute

23. Hybrid Cloud Reality: Zynga’s zCloud
© 2012 Citrix | Confidential – Do Not Distribute

24. Coupa
Challenges:
• Customer data residency
requirements in Canada and
Europe
Results:
• Built hybrid cloud in with Cloudstack
“RightScale multi-cloud support enables us to transparently host
Coupa on public clouds such as Amazon and Rackspace or a
CloudStack-based private cloud while delivering high availability
and data privacy compliance.”
Sanket Naik, Sr. Director, Cloud Operations and Integrations
© 2012 Citrix | Confidential – Do Not Distribute

25. Summary/Conclusions
Private (and therefore hybrid) clouds were originally thought of as an
academic exercise or science project
Recent advances (particularly in cloud infrastructure software) have shown
private and hybrid clouds to be viable IT delivery models
Many considerations come into play
ᵒDesign
ᵒHardware
ᵒSoftware
ᵒImplementation Details
No “one size fits all”
ᵒDo your research. Find the right fit.
© 2012 Citrix | Confidential – Do Not Distribute

26. Next Steps
Contact RightScale
(866) 720-0208
1. Learn: Read Brian’s White Paper sales@rightscale.com
www.rightscale.com
Will be included in follow-up email
2. Try: Free Edition
www.rightscale.com/free The next big RightScale Community Event!
April 25-26 in San Francisco
www.RightScaleCompute.com
3. Attend our Conference to talk •Attend technical breakout sessions
more with us and the CloudPlatform team •Get RightScale training
www.RightScaleCompute.com •Talk with RightScale customers
•Ask questions at the Expert Bar
© 2012 Citrix | Confidential – Do Not Distribute