Your SlideShare is downloading. ×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Rightscale Webinar: Designing Private & Hybrid Clouds (Hosted by Citrix)

235
views

Published on

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 …

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

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
235
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Brian does this slide
  • Vijay does this slideBenefits of public cloud: - on-demand, PAYG compute power - infinite scalability - multiple locations - outsourced (you don’t have to build it)Benefits of private cloud: - can provide better performance - increased security - more control - lower costWhere RS fits and combines benefits for hybrid – deployment & management of multiple public & private cloud computing services to match business needs – from single pane of glass
  • Vijay
  • Brian
  • Brian
  • Brian
  • Brian
  • Brian
  • Brian
  • Vijay takes over
  • Brian takes over
  • Brian
  • Vijay takes over
  • Vijay
  • Vijay
  • Vijay
  • Vijay
  • Brian takes over
  • Brian
  • Vijay
  • Vijay
  • Vijay
  • Brian
  • Brian
  • Transcript

    • 1. Partner LogoBuilding Blocks forPrivate and Hybrid CloudsMarch 21, 2013
    • 2. Partner LogoYour 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 LogoAgenda 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 LiberationApplication 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 NManagement & automation – across cloud resource pools© 2012 Citrix | Confidential – Do Not Distribute
    • 6. Definitions and TerminologyVirtualization (server) • Division of one physical server into multiple isolated virtual environmentsPrivate 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 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) relationship • This was betterCloud Computing • Automated provisioning and management via an API appears • This is much, much better © 2012 Citrix | Confidential – Do Not Distribute
    • 8. Private Cloud Key ConsiderationsWorkload and Infrastructure Interaction • Applications have different resource needs • Choose the right fit for your application and your infrastructureSecurity • Data may be contained within the private cloud, thus allowing for stricter security complianceLatency • Consumers of the private cloud resources are generally “closer” to the private cloud, which reduces latencyUser 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 CloudsWhat 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 taskMore common use case is multiple clouds in an organization, with multipleapplications, and with each application contained entirely within a singlecloud. © 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 CasesSelf-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 CasesSelf-Service IT Portal (“IT Vending Machine”) • Demo© 2012 Citrix | Confidential – Do Not Distribute
    • 13. Use CasesScalable 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 CasesDisaster 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 ConsiderationsLocation 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 • SecurityAvailability 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 ConsiderationsIntended 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 ConsiderationsCloud Infrastructure Software ᵒCloudStack /CloudPlatform • Open source vs. commercial ᵒDictates/influences other decisions regarding cloud implementation ᵒAccess to resources • Web interface • APICloud 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 ProcessHardware Procurement ᵒPre-existing or new? • Pre-existing limits ability to tailor infrastructure to workloadsCloud 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 ProcessCompatibility ᵒAvoid vendor lock-in at IaaS level, hypervisor level, cloud infrastructure software levelUnified 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 interventionFocus 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/ConclusionsPrivate (and therefore hybrid) clouds were originally thought of as anacademic exercise or science projectRecent advances (particularly in cloud infrastructure software) have shownprivate and hybrid clouds to be viable IT delivery modelsMany considerations come into play ᵒDesign ᵒHardware ᵒSoftware ᵒImplementation DetailsNo “one size fits all” ᵒDo your research. Find the right fit. © 2012 Citrix | Confidential – Do Not Distribute
    • 26. Next Steps Contact RightScale (866) 720-02081. Learn: Read Brian’s White Paper sales@rightscale.com www.rightscale.com Will be included in follow-up email2. Try: Free Edition www.rightscale.com/free The next big RightScale Community Event! April 25-26 in San Francisco www.RightScaleCompute.com3. Attend our Conference to talk •Attend technical breakout sessionsmore 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

    ×