4.cloud Deployment models

4.cloud Deployment models

• 1.
  CLOUDDEPLOYMENTMODELS • Dr.Rajapraveen
• 2.
  CLOUDDEPLOYMENTMODELS
• 4.
  3 Enterprise DataCenter THERE IS ASPECTRUM OF DEPLOYMENT OPTIONS FOR CLOUD COMPUTING 1) Private Cloud 2) Managed Private Cloud 3) Hosted Private Cloud 4) Community Cloud Services 5) Public Cloud Services Enterprise DataCenter 3rdparty operated Enterprise 3rd party hosted & operated Private Cloud Managed PrivateCloud Hosted PrivateCloud EnterpriseA EnterpriseB Enterprise C User1 User2 User4 User3 Private Public Hybrid Key features •Scalability •Automatic/rapid provisioning •Chargeback ability •Widespread virtualization •Security Key features •Scalability •Automatic/rapid provisioning •Standardized offerings •Consumption-based pricing. •Multi-tenancy Key features • Internal & external services integrated • Functions allocated to based on requirements, business needs, architecture etc S hared CloudServices Public CloudServices
• 5.
  Customers are choosingavariety of cloud models tomeet their unique needsand priorities. Private Cloud On or off premises cloud infrastructure operated solely for an organization and managed by the organization or a third party Public Cloud Available to the general public or a large industry group and owned by an organization selling cloud services Hybrid Cloud Traditional IT and clouds (public and private) that remain separate but are bound together by technology that enables data and application portability Traditional IT Appliances, pre-integrated systems and standard hardware, software, and networking CLOUD DELIVERY MODELS
• 6.
  FFlelexxibibiliiltiyty DIFFERENT DELIVERY MODELS Off-Premise Traditiona l IT DedicatedHybrid On-Premise Description Cost Model Service P rivate/P ublic Dedicated systems in customers data centre. Bespoke and highly customised to application needs. $$$$ Customer owned. Customer operated. High Capex/ High Opex. Long term commitment. High SLAs. 99.999 availability. Custom security. Behind customer firewall. Always private Dedicated cloud in customers data centre. Highly automated, pattern based, tuned for workloads. $$$ Customer owned. Customer operated. High Capex/Medium Opex. Mid term commitment. High SLAs. 99.999 availability. Standardised security. Behind customer firewall. Always Private Combined on-premise and off- premise cloud systems. Includes off-premise private Cloud. Highly standardised build, some parts run by service provider. $$ Partial customer ownership. Mostly service provider operated. Med Capex/Medium Opex. Short term commitment. High SLAs. 99+ availability. Standardised security. Requires good network and security. Can be private or public Public cloud infrastructure run off premise by service provider. Commodity resources defined by the service provider. Catalog based services. $ Provider owned. Provider operated. Full Opex model. No/short term commitment. PAYG. Medium SLAs. 98+ availability. Relies upon provider security and trust. Likely to be public, but can have dedicated private cloud at off-premise service provider.
• 7.
  PRIVATECLOUD • centralizing accessto IT resources by different parts, locations, or departments of the organization. • When aprivate cloud existsasacontrolled environment, the problemsdescribedin the RisksandChallengessectiondo not tend toapply. • Aprivate cloud isowned by asingle organization. • Private clouds enable cloud computing technology as a means an organization to use of
• 8.
  • CLOUD INFRASTRUCTURE BUILT INHOUSE •Retains control of resources • More security & privacy • Canconform to regulatory requirement • Needscapital investment • Needsexpertise to buildand maintain P P r r i v i v a a t t e e C C l o l o u u d d
• 10.
  PUBLICCLOUD • A publiccloud is a publicly accessible cloud environment owned by a third- party cloud provide • TheITresources on public clouds are usually provisioned via cloud delivery models. • Thecloud provider is responsible for the creation and on-going maintenance of the public cloud and its ITresources.
• 11.
  • AVAILABLE TO EVERYONE. • Anyonecan go and signup for theservice. • Economies of Scaledueto Size. • Somepublic cloud concerns – Ownership – Control – Regulatory compliance – Data/Application security – Liability for SLAbreaches P P u u b b l i l c i c C C l o l o u u d d I n t e r n e t
• 12.
  • Many ofthe scenarios andarchitectures explored via Public cloud.
• 13.
  • A hybridcloud is a cloud environment comprised of two or more different cloud deployment models. • Best of BothWorld • Workload is deployed mostly on private cloud • Resources can be used from public cloud when there is a surge in peak load (CloudBurst) P P r r i v i v a a t t e e C C l o l o u u d d P P u u b b l i l c i c C C l I o l o u u d d n t e r n e t HYBRID CLOUDS
• 14.
  HYBRID DELIVERS BENEFITSBEYOND ONLY PUBLIC OR PRIVATE CLOUD MODELS Reducecosts and maximise existing ITinvestments. – Data centre and infrastructure reused alongside flexible publiccloud. Businessagility, scale quickly to respond tobusinessevents. – Move quickly increasing workloads to off-premiseClouds. Maintain control through applicationlifecycle. – Single point of control of ITinfrastructure resources,consumption and usage Maintain visibility of importantworkloads. – Workloads placed basedon servicerequirements Shared Off-Premise Dedicated Hybrid On-Premise Traditiona l IT Enterprise class Flexibility & Resilience Regulated Workloads Regulated Workloads P roduction User Data Low-cost commodity Test/Dev Anonymised Data Performance without commitment Pre- Production/Test Anonymised Data Production User Data
• 15.
  Data centre prioritisedfor high- availability production workloads with service mgmt Low priority workloads moved externally Lower investment in fixed data centre assets ITIL managed Burst at peak workload to low cost commodity provider Dev Test - SIT De v No commitment Pay as you go - commodity Long term flexibility with external Dedicated Private Exploit unused production capacity Development SCM Build SIT UAT Prod Application Lifecycle Time ADOPTING HYBRID LOWERS COSTS WHILE MAINTAINING SERVICELEVELS
• 16.
  Deployment Models -Benefits C ustomer Scenario ServiceModel Deployment Model Benefits Payroll Processing IaaS(VMs), cloudstorage PublicCloud Processingtime reduced Hardwarerequirementsreduced Elasticityenabledfor future expansion Astronomic Data Processing IaaS(VMs), cloudstorage PublicCloud Hardwareexpensegreatly reduced processingpowerandstorage) Energycostsgreatly reduced Administrationsimplified Central Government IaaS,PaaS Private Cloud ITexpertiseconsolidated Hardwarerequirementsreduced Local Government IaaS,PaaS HybridCloud ITexpertiseconsolidated Hardwarerequirementsreduced