Your SlideShare is downloading. ×
Which cloud(s) & why? Defining Clouds and Best Practices
Upcoming SlideShare
Loading in...5
×

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

Which cloud(s) & why? Defining Clouds and Best Practices

239

Published on

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

  • Be the first to like this

No Downloads
Views
Total Views
239
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
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
  • How many connected devices do you own?By 2020 we will have to support about 24 billion devices. That’s only 7 short years away!Can your current data center support a 3x increase? What are your plans to support the increase?http://gigaom.com/cloud/internet-of-things-will-have-24-billion-devices-by-2020/
  • The biggest cloud drivers are:Scalability – supporting that 3x increase by 2020Agility – current data center thinking in not very flexible. We allocate resources based on projects. We ask our architects how much CPU, memory, disk space a project requires and build systems from there. What about point #1? If an application needs to scale, can it?Cost – as with most things, cost saving is always good. One point here is, we need to utilize what we have more efficiently. Virtualization took us from 5-15% utilization to about 30-50%. Think about that, data center resources sitting idle for 50-70% of the time. We have to get better at this.Remember – Can your data center support a 3x increase?
  • What our future looks like. As we move toward our 2020 goal of supporting 3x the workloads of today, we will use a mix of public and private cloud to support the increasing demand. Or what we call Hybrid Cloud.
  • http://csrc.nist.gov/publications/drafts/800-145/Draft-SP-800-145_cloud-definition.pdfPretty much any IT survey in the last 2 years puts cloud and virtualization among the top goals for most companies.So what is cloud computing? Seems like every company says that they have a cloud today, but do they? Are they just cloud-washing?NIST offers a broad definition covering all aspects of cloud computing.More detail on the following pages.
  • From the top done.Deployment modelsService models5 Essential Characteristics
  • What does a cloud look like? What characteristics does it need?On-demand self-service – Self-service to me takes on two characteristics. The first is a for individual consumers of the cloud to have portal like access. The second is to allow programmatic access. An API. This is for build and automation tools, orchestration engines, monitoring frameworks. Network access – People have to able to access what we build on these cloudsResource pooling – combine our resources. No more silo’s or equipment. Let others shareElasticity – the ability to change or be flexibleMeasured service – charge back or show back
  • AWS: Amazon Web ServicesGCE: Google Compute Engine
  • Approvals and deployments depend on humans and therefore have the potential for delays. Deployment can take days, weeks, or even months.
  • The cloud itself, not the IT department, checks to see if the request is within policies. Because humans are less involved there is no potential for delay.
  • How are we going to get there?Server virtualizationDistributed virtualizationPrivate Cloud – EucalyptusHybrid Cloud – Eucalyptus and Amazon AWS – this is were we can share the load across the on-premise Eucalyptus cloud and the public Amazon AWS cloud. This gives you the maximum flexibility.Public Cloud- Amazon AWS – moving as much of your workloads into the public cloud.Link to Gartner research:http://www.internap.com/wp-content/uploads/Virtualization-to-the-Cloud-Internap_vol2_issue2.pdf
  • Bursty workloads – seasonal spikesTransient apps – QABig data – move from data-warehousing analyzing in real timeGaming – could be spikey
  • How are we going to get there?Server virtualizationDistributed virtualizationPrivate Cloud – EucalyptusHybrid Cloud – Eucalyptus and Amazon AWS – this is were we can share the load across the on-premise Eucalyptus cloud and the public Amazon AWS cloud. This gives you the maximum flexibility.Public Cloud- Amazon AWS – moving as much of your workloads into the public cloud.Link to Gartner research:http://www.internap.com/wp-content/uploads/Virtualization-to-the-Cloud-Internap_vol2_issue2.pdf
  • Transcript

    • 1. © 2013 Eucalyptus Systems, Inc.Which Cloud(s) &Why? Defining Cloudsand Best PracticesPaul WeissTechnical Marketing Manager1
    • 2. © 2013 Eucalyptus Systems, Inc.Agenda• Why Cloud?• Define Cloud• Cloud Models• Old vs New• Benefits of Cloud• How to Select the Right Cloud Model(s)• How to Select the Applications to Move into the Cloud• How to Successfully Migrate Applications into the Cloud• Best Practices (Getting Started)2
    • 3. © 2013 Eucalyptus Systems, Inc.3
    • 4. © 2013 Eucalyptus Systems, Inc.Why Cloud?4
    • 5. © 2013 Eucalyptus Systems, Inc.The Connected Life by 20205Be prepared to support 3x the workload in 7 years
    • 6. © 2013 Eucalyptus Systems, Inc.What’s Driving Cloud Adoption6Source: 2012 Future of Cloud SurveyScalability is the #1 reason for cloud. Remember 3xin 7 years
    • 7. © 2013 Eucalyptus Systems, Inc.Tomorrow’s Cloud Forecast7Source: 2012 Future of Cloud SurveyHybrid is the only way to scale to 3x in 7 years
    • 8. © 2013 Eucalyptus Systems, Inc.What is a Cloud?8
    • 9. © 2013 Eucalyptus Systems, Inc.Cloud Computing Definition• Industry surveys indicate that the desire to move to cloudcomputing is widespread. So what is cloud computing?• National Institute of Standards and Technology (NIST)definition:“. . . a model for enabling ubiquitous, convenient, on-demandnetwork access to a shared pool of configurable computingresources . . . that can be rapidly provisioned and releasedwith minimal management effort or service providerinteraction.”9
    • 10. © 2013 Eucalyptus Systems, Inc.NIST Cloud Definition10
    • 11. © 2013 Eucalyptus Systems, Inc.5 Essential Cloud Characteristics11
    • 12. © 2013 Eucalyptus Systems, Inc.Cloud Deployment ModelsPrivate Cloud Community Cloud Public CloudThe cloud infrastructure isoperated entirely for anorganization.The cloud infrastructure isshared by severalorganizations and supports aspecific community that hasshared concerns.The cloud infrastructure ismade available to the generalpublic or a large industrygroup and is owned by anorganization selling cloudservices.• Secure• Predictable Performance• Existing resources• Path to hybrid cloud• Control• Cost control• Designed w/ a purpose• Scale• Cost savings (if managed)• Cost savings (if managed)• Scale• Regions to span• Many servicesEucalyptus, Apache CloudStack, OpenStackAWS GovCloud AWS, GCE, Windows Azure,RackSpace~~~~ Hybrid Cloud ~~~~12
    • 13. © 2013 Eucalyptus Systems, Inc.Traditional IT Deployment Model(OLD)13• In a traditionalmodel, the usermust work throughthe IT department toprovision a server.• This is a multi-stageprocess that hasinherent delays.• Can takedays, weeks, oreven monthsUser requests serverServer provisionedWaitNegotiate resourceconfigurationNegotiate businesscaseApproved?IT available?nonoyesyesOld methods will not scale to the 3x we need tosupport
    • 14. © 2013 Eucalyptus Systems, Inc.Cloud Computing Deployment Model(NEW)14• In a cloud computing modelthe user can self-provisionservers that fall withinpredefined IT resourcepolicies.• This model eliminates manyof the inherent delays in thetraditional deployment model.• Deployment time reduced tominutesUser requests serverServer provisionedIT defines resourcepoliciesWithin policies?yesnoCloud computing deployment model will help usscale to support the 3x demand
    • 15. © 2013 Eucalyptus Systems, Inc.Differences Between Virtualizationand Cloud Computing15TraditionalVirtualizationCloud ComputingVM Location on a specific host on any host inavailability zoneVM Storage persistent ephemeral (except forvolumes)VM Resources (CPU,memory)customizable standard sizes (Small,Medium, Large, etc.)VM Resource ChangeMethodresize existing VM launch new VMTime to Provision Minutes/Hours/Days MinutesVM Failure RecoveryMethodattempt to recover failedVMdiscard and start newVMVirtualization alone is not cloud!
    • 16. © 2013 Eucalyptus Systems, Inc.Some Benefits of Cloud Computing• Application scalability• Agility• Cost control• Time to Market• Security• Better utilization of resources• Disaster Recovery• Remove IT silos16#1 – Scalability#2 – Agility#3 Cost
    • 17. © 2013 Eucalyptus Systems, Inc.17The Roadmap Through Private CloudAfter virtualization, private cloud is the next step
    • 18. © 2013 Eucalyptus Systems, Inc.IaaS Use Cases - Getting Started• Transient apps: dev & test environments• Bursty workloads: web and mobile applications• Big data: analytics and computations• Gaming applicationsand: hybrid clouds, rich media encoding/decoding, complex and large-scale dataprocessing, training & e-learning, storage-as-a-service, remote desktop hosting,public cloud, carrier-grade cloud18Dev / Test is a great place to start
    • 19. © 2013 Eucalyptus Systems, Inc.To Cloud or Not? – Think about• Dev / Test – on ramp to public cloud• Security• Intellectual Property (IP)• Manufacturing• Some Enterprise Applications19Every application needs to be carefully evaluated –to cloud or not!
    • 20. © 2013 Eucalyptus Systems, Inc.20
    • 21. © 2013 Eucalyptus Systems, Inc.Images / Instances21
    • 22. © 2013 Eucalyptus Systems, Inc.What’s in an Image?• Not running• Operating System• Current Patches*• Application*Note: An image is stored in the cloud, not running22An image is a stored snap-shot or disk copy of asystem, ready to be launched
    • 23. © 2013 Eucalyptus Systems, Inc.What’s in an Instance?• Running copy of an image• Configured size (VM Type)– CPU– Memory– Disk– Network / Security• Operating System• Current Patches• User(s) – keys by default, LDAP, AD• Additional storage if needed• Application(s)• Connections to other systems – LB’s, DB’s, etc.23An instance is a running virtual machine, based onan image, ready to use
    • 24. © 2013 Eucalyptus Systems, Inc.ImagesMachine Size• CPU(s)• Mem• Disk• NetworkOperationSystemInitialConfiguration(network,access,mounts, etc)Patches Application ApplicationConfigurationBasic VirtualMachineManuallyConfigureChoose ISO,ManuallyinstallManualconfigurationManuallyinstallManuallyinstallManualconfigurationAdvancedVirtualMachineBoot pre-configured VM template ManualconfigurationManual update Installed withtemplateManualconfigurationBasic CloudInstanceChoose VM-TypeChoose Image CloudconfiguredManuallyinstallManuallyinstallManuallyconfiguredSemi-AutomatedCloudChoose VM-TypeChoose Image CloudconfiguredConfiguration ManagementAgent managedFullyAutomatedCloudUsing monitoring, load-balancing, auto-scaling – cloud automatically provisions / de-provisions as neededto maintain work-load.24Think about supporting 3x the workload
    • 25. © 2013 Eucalyptus Systems, Inc.Instance Flow25VM Size OS InstallInitialConfigAppInstallPatchInstallFinalConfigHow many of these steps do you want to domanually?
    • 26. © 2013 Eucalyptus Systems, Inc.How to start an Instance• Start basic instance– $euca-run-instances emi-12345 –k mykey• Advanced instance start– $ euca-run-instances emi-12345 –k mykey –g my_security_group –tVmtype –f cloud-config.txt26
    • 27. © 2013 Eucalyptus Systems, Inc.Cloud-init$ cat cloud-config.txt#cloud-config# upgrade the instance on first bootpackage_upgrade: true# setup mount pointsmounts:- [ sdc, /opt/data ]# install additional packages at first bootpackages:- your favorite configuration management system agent27
    • 28. © 2013 Eucalyptus Systems, Inc.Application GroupsApache + HAProxy Apache + HAProxyApp Server 1 App Server 2 App Server 3 App Server nMasterDBSlaveDBEBSVol.EBSVol.WalrusYour SiteDaily Snapshots Rolling SnapshotsReplication172.168.2.54 172.168.9.87Web-Tier Group #1App-Tier #1
    • 29. © 2013 Eucalyptus Systems, Inc.Web-Tier Group #1• VM Type: Large– 2 CPU– 8 GB RAM– 160 GB Disk• Update OS• Install Apache + HA Proxy• Connect to App-Tier Message Queue• Add IP to load balancer• Report success to monitoring tool when above is done29
    • 30. © 2013 Eucalyptus Systems, Inc.App-Tier Group #1• VM Type: X-Large– 4 CPU– 16 GB RAM– 160 GB Disk• Update OS• Install Application Server• Connect to App-Tier Message Queue• Connect to Database Message Queue• Report success to monitoring tool when above is done30
    • 31. © 2013 Eucalyptus Systems, Inc.Monitor Each Tier• Understand load placed on tier• Knows how to scale up when demand increases– Max instances• Knows how to scale down when demand decreases– Min instances31Group applications, monitor and scale up or downas needed to meet demand and contain cost.
    • 32. © 2013 Eucalyptus Systems, Inc.Applications32
    • 33. © 2013 Eucalyptus Systems, Inc.Application Dependency Mapping33Has risk assessment and dependancy mappingbeen done on every mission critical application?
    • 34. © 2013 Eucalyptus Systems, Inc.Less Complex34Keep it simple for first time success!
    • 35. © 2013 Eucalyptus Systems, Inc.Examples of Tight / Loose Coupling• Example of tight coupling:Controller A Controller B Controller CController A Controller B Controller CController A Controller B Controller CController A Controller B Controller CQ1Q1Q1• Example of loose coupling using queues:Design for scalability
    • 36. © 2013 Eucalyptus Systems, Inc.Example of Scalability DesignApache + HAProxy Apache + HAProxyApp Server 1 App Server 2 App Server 3 App Server nMasterDBSlaveDBEBSVol.EBSVol.WalrusYour SiteDaily Snapshots Rolling SnapshotsReplication172.168.2.54 172.168.9.87
    • 37. © 2013 Eucalyptus Systems, Inc.Design for Scalability• A scalable application architecture is critical to takeadvantage of a scalable infrastructure• Load balancing and proxying• Caching– Don’t generate the same content twice• No central point of data storage contention– Shared Nothing / Sharding / Distributed Caching• Loose coupling of processing requestors and responders
    • 38. © 2013 Eucalyptus Systems, Inc.Design for Failure• "Everything fails, all the time“- Werner Vogels, CTO Amazon.com• Avoid single points of failure• Assume everything fails, and design backwards• Design for failure and your app won’t fail
    • 39. © 2013 Eucalyptus Systems, Inc.Hybrid Cloud39
    • 40. © 2013 Eucalyptus Systems, Inc.Stage-Move-Manage CloudEBSS3EC2IAMEMIS3EC2 EBSIAMAMI• Multi-vendor Virtualization• Multi-vendor Storage• Data center Networking• Infrastructure MeshedApplications• Layer over multi-vendorcomplexity• Separate application logicfrom infrastructure• Store data with cloudcompute accessibility• Create LDAP/AD to IAMbridge• Seamless access to on-demand capacity• On-demand pricing• Better applicationavailability• Better data resiliencyCloud Management Framework
    • 41. © 2013 Eucalyptus Systems, Inc.Hybrid Cloud API Compatibility41Test on-premise cloud compatibility with provenapplications
    • 42. © 2013 Eucalyptus Systems, Inc.AWS & Eucalyptus Compatibility42How compatible is the hybrid solution?
    • 43. © 2013 Eucalyptus Systems, Inc.Hybrid Example43
    • 44. © 2013 Eucalyptus Systems, Inc.Mirroring / ReplicationScaled downStandbyDataVolumeApplicationServerReverseProxy /CachingServerAWS RegionSlaveDatabaseServerDataVolumeApplicationServerReverseProxy /CachingServerEucalyptus On-Premise IaaSMasterDatabaseServerPilot LightNot RunningPilot Light Systemwww1.eucalyptus-labs.com
    • 45. © 2013 Eucalyptus Systems, Inc.www1.eucalyptus-labs.com (Euca)45
    • 46. © 2013 Eucalyptus Systems, Inc.Mirroring / ReplicationDataVolumeApplicationServerReverseProxy /CachingServerAWS RegionSlaveDatabaseServerDataVolumeApplicationServerReverseProxy /CachingServerEucalyptus On-Premise IaaSMasterDatabaseServerPilot Light - recoveryStart inminutesAdd additionalcapacity as neededwww2.eucalyptus-labs.comX
    • 47. © 2013 Eucalyptus Systems, Inc.www2.eucalyptus-labs.com (AWS)47
    • 48. © 2013 Eucalyptus Systems, Inc.Review and Best Practices48
    • 49. © 2013 Eucalyptus Systems, Inc.49The Roadmap Through Private CloudCan you support 3x? Planning is critical!
    • 50. © 2013 Eucalyptus Systems, Inc.Cloud Best Practices (requirements)• Risk assessment on all mission critical applications• Dependency mapping on all mission critical applications• Gather application issues• Application requirements (OS, platform)• Machine requirements (CPU, Memory)• Network requirements• Storage requirements (space and IOPS)• Benchmark virtual machine / application• Document application monitoring50
    • 51. © 2013 Eucalyptus Systems, Inc.Cloud Best Practices (Getting Started)• Review NIST Special Publication 800-146• Review Gartner Cloud Roadmap• Decide what cloud model(s) you will start with• Get executive sponsorship• Agree what success looks like• Create a project plan• Train staff• Choose an application that makes sense• Benchmark application in the cloud (compare)– Performance, Availability & Scalability• Monitor51
    • 52. © 2013 Eucalyptus Systems, Inc.Thank you.52Paul Weisspaul.weiss@eucalyptus.com@Paul_Weiss

    ×