• Like

Building Blocks for Hybrid IT

  • 326 views
Uploaded on

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 …

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.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
326
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
23
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
  • Brian
  • Brian
  • Brian
  • Brian
  • Brian takes over
  • Brian
  • Vijay takes over
  • Vijay takes over
  • Vijay
  • Vijay
  • Vijay
  • Vijay
  • Brian takes over
  • Brian
  • Brian
  • Brian
  • Vijay
  • Quest Diagnostics story – can’t publicize the nameSelf-Service ITQuest Diagnostics manages development, test, and production environments across AWS and a CloudStack private cloud using RightScale. Quest has developed a self-service IT portal called "hashbang" that lets their internal developers pick an instance & launch a server without a ticket, a RFS, or a phone call.Challenge — Move to Cloud Amid RegulationConsistency: Need standard processes and configurations across cloud vendors. Organizational change: Current siloed org of network, storage, and data teams does not translate well to the cloud. Regulations require private cloud: HIPAA, PHI, PCI, and other data residency requirements make public cloud impossible for some workloads.Solution — Hybrid Self-Service PortalHybrid cloud environment: Use RightScale to manage AWS and an on premise CloudStack private cloud. Self-service portal: Built a self-service portal called HashBang on top of RightScale API to deliver approved configurations for developers.Impact — Flexible IT FootprintProvisioning in 15 minutes: IT teams can provision resources in the time it takes them to get a coffee.
  • Brian

Transcript

  • 1. #rightscaleBuilding Blocks for Hybrid ITBrian Adler, Sr. Services Architect, RightScaleRyan Geyer, Cloud Solutions Engineer, RightScaleApril 30, 2013
  • 2. #2#rightscaleAgenda• 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#rightscaleOn-Premises ResourceCloud Resource
  • 4. #4#rightscaleApplicationPortfolioRequirementsFilterResourcePoolsApp 1App 2App 3PerformanceCostComplianceGeo-locationSecurityWorkload LiberationManagement & automation – across cloud resource poolsApp N…App 1App 2App 3Hosted PrivatePublic Cloud 2Public Cloud 1VendorsExisting DCApp 4App 5App N…App 4App 5Internal Private
  • 5. #5#rightscaleDefinitions and TerminologyVirtualization (server)Division of one physical server into multiple isolated virtualenvironmentsOn-Premises ITA collection of compute, storage, and network resources for a singletenant that are accessed programmatically via an API endpoint.Cloud ArchitectureA similar set of resources that is multi-tenant and is provided by acloud vendor with access via an API endpoint.
  • 6. #6#rightscaleDefinitions and TerminologyMulti-CloudAn environment that spans two or more separate cloud providers.Hybrid ITAn environment that spans one or more cloud providers as well asone or more on-premises IT environments.
  • 7. #7#rightscaleInfrastructure 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 betterCloud Computing• Automated provisioning and management via an API appears-This is much, much better
  • 8. #8#rightscaleOn-Premises IT: Key ConsiderationsWorkload and Infrastructure Interaction• Applications have different resource needs• Choose the right fit for your application and your infrastructureCompliance• Data may be contained on-premises for compliance needs or requirements.Latency• Consumers of the on-premises resources are generally “closer” to theenvironment, which reduces latency
  • 9. #9#rightscaleOn-Premises IT: Key ConsiderationsUser Experience• Related to latency, end user experience is enhanced due to proximity toresources.Cost• OPEX is generally reduced. (CAPEX is another story )
  • 10. #10#rightscaleUse CasesSelf-Service IT Portal (“IT Vending Machine”)• Users select one of several preconfigured tech stacks• Isolated Test/Dev environments
  • 11. #11#rightscaleDemo
  • 12. #12#rightscaleUse CasesScalable Applications with Uncertain Demand• Cloud used as “proving ground” for new applications• Low-demand applications run their course in the cloud until they areend-of-lifed• Applications that gain traction remain in the cloud during growth phase• When stability of workload is reached, the application is transitionedinto an on-premises environment.
  • 13. #13#rightscaleUse 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 stateON-PREMISES
  • 14. #14#rightscaleDemo
  • 15. #15#rightscaleDesign ConsiderationsLocation 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#rightscaleDesign ConsiderationsAvailability and Redundancy Configuration• Easiest configuration (single zone, single region, single API endpoint) does notpromote high availability• High Availability of resources requires more complex configurations
  • 17. #17#rightscaleDesign Considerations/OptionsSimple ConfigurationNo HA or RedundancyHA Configuration
  • 18. #18#rightscaleDesign ConsiderationsIntended Workloads and Use Cases• Does the application require high availability or is it tolerant of interruptions ofservice?• Does the application require (or greatly benefit from) specialized hardware ornetwork configurations?
  • 19. #19#rightscaleHardware ConsiderationsCompute• Commodity• High end/specializedNetworking• Driven by topology, latency demands, and price• Some infrastructure software offerings have support fornetwork hardware devices (load balancers in particular)Storage• Cost vs. Performance (commodity? SSD?, etc.)
  • 20. #20#rightscaleSoftware ConsiderationsCloud Infrastructure Software• Open source vs. commercial• Dictates/influences other decisions regarding cloud implementationCloud Management Software• Abstracts underlying details of the cloud infrastructure offerings• Presents consistent interface to the available resources regardless of theunderlying infrastructure provider• Provides a cloud-portable solution• Provides orchestration tools for provisioning and management
  • 21. #21#rightscaleImplementation 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
  • 22. #22#rightscaleManagement ProcessCompatibility• Avoid vendor lock-in at IaaS level, hypervisor level, cloud infrastructuresoftware 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 fromimage management, automation, provisioning, etc.
  • 23. #23#rightscaleHybrid 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 thecloud 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 taskMore common use case is each application contained entirely within asingle environment whether cloud or on-premise.
  • 24. #24#rightscaleHybrid IT / Cloud BurstingON-PREMISES CLOUDLOAD BALANCERSAPP SERVERSMASTER DATABASESLAVE DATABASEOBJECT STORAGEAPP SERVERSPUBLICINTERNETCloud Bursting
  • 25. #25#rightscaleDemo
  • 26. #26#rightscaleHybrid IT Customer ExampleResults:• Built hybrid architecture with AWSand CloudStack• RightScale provides unifiedmanagementChallenges:• Customer data residencyrequirements in Canada andEurope“RightScale multi-cloud support enables us totransparently host Coupa[both in the cloud andon-premises]while delivering high availabilityand data privacy compliance.”SanketNaik, Sr. Director, Cloud Operations andIntegrations
  • 27. #27#rightscaleHybrid IT Customer ExampleResults:• Built hybrid architecture with AWSand CloudStack• RightScale provides unifiedmanagementChallenges:• Deliver consistent and approvedconfigurations to developers• Compliance needs for dataresidencyFortune 500 Clinical LaboratoryProviderCreated a Self-Service IT on-premisesenvironment alongside AWS.Use the RightScale IT vendingmachine to provide developers withstandard configurations that can belaunched without a ticket, RFS(Request for Service) or a phone call.Provisioning time takes 15 minutes
  • 28. #28#rightscaleSummary/Conclusions• On-premises or hybrid IT was originally thought of as an academicexercise 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 DetailsNo “one size fits all”• Do your research. Find the right fit.
  • 29. #29#rightscaleResources and Next Steps1. LEARN:Read our White Paperhttp://bit.ly/rswhitepaper2. TRY:Free Editionwww.rightscale.com/free3. TALK: Visit us at our Booth todayEnter to win $100 Amazon gift certificateContact RightScale(866) 720-0208sales@rightscale.comwww.rightscale.com