Architectural Implications Of Cloud Computing
Architectural Implications ofCloud ComputingGrace A. LewisResearch, Technology and Systems Solutions (RTSS) ProgramSATURN 2011May 18, 2011 2011 Carnegie Mellon University
AgendaBasic Cloud Computing ConceptsArchitectural Implications of Cloud ComputingFinal ThoughtsArchitectural Implications of Cloud ComputingSATURN 20112May 18, 2011 2011 Carnegie Mellon University
Cloud Computing“A large-scale distributed computing paradigm that is driven byeconomies of scale, in which a pool of abstracted, virtualized,dynamically-scalable, managed computing power, storage, platforms,and services are delivered on demand to external customers over theInternet.” *jaworski.net*I. Foster, Y. Zhau, R. Ioan, and S. Lu. “Cloud Computing and Grid Computing : 360-Degree Compared.” GridComputing Environments Workshop, 2008.Architectural Implications of Cloud ComputingSATURN 20113May 18, 2011 2011 Carnegie Mellon University
Cloud Computing TypesSoftware-as-a-Service (SaaS)Public CloudPlatform-as-a-Service (PaaS)Infrastructure-as-a-Service (IaaS)Based on Type of CapabilityPrivate CloudBased on Who Can AccessResourcesArchitectural Implications of Cloud ComputingSATURN 20114May 18, 2011 2011 Carnegie Mellon University
Infrastructure-as-a-Service (IaaS)Mainly computational infrastructure available over the internet,such as compute cycles and storageAllows organizations and developers to extend their ITinfrastructure on an on-demand basisExamples of IaaS Providers Amazon Elastic Compute Cloud (EC2)– Provides users a special virtual machine (AMI) that can bedeployed and run on the EC2 infrastructurez.about.com Amazon Simple Storage Solution (S3)– Provides users access to dynamically scalable storageresources IBM Computing on Demand (CoD)– Provides users access to highly configurable servers plus valueadded services such as data storage Microsoft Live Mesh– Provides users access to a distributed file system; targeted atindividual useArchitectural Implications of Cloud ComputingSATURN 20115May 18, 2011 2011 Carnegie Mellon University
Platform-as-a-Service (PaaS)Application development platforms the allow the usage of externalresources to create and host applications of a larger scale than anindividual or small organization would be able to handleExamples of PaaS providersvertoda.files.wordpress.com Akamai EdgePlatform– Large distributed computing platform for web application deployment (focuson analysis and monitoring of resources) Force.com– Platform to build and run applications and components bought fromAppExchange or custom applications Google App Engine– Platform to develop and run applications on Google’s infrastructure Microsoft Azure Services Platform– On-demand compute and storage services as well as a developmentplatform based on Windows Azure Yahoo! Open Strategy (Y!OS)– Platform to develop and web applications on top of the existing Yahoo!Platform (focus on social applications)Architectural Implications of Cloud ComputingSATURN 20116May 18, 2011 2011 Carnegie Mellon University
Software-as-a-Service (SaaS)Model of software deployment in which a third-partyprovider licenses an application to customers for use asa service on demandExamples Google Apps– Web-based office tools such as e-mail, calendar anddocument management tools Salesforce.com– Full customer relationship management (CRM)application Zoho– Large suite of web-based applications, mostly forenterprise usecloudtp.comArchitectural Implications of Cloud ComputingSATURN 20117May 18, 2011 2011 Carnegie Mellon University
Cloud Computing Types — Based on AccessPublicPERSPECTIVE Offered as a service, usually over an Internet connection Typically charge a pay-per-use fee Users can scale on-demand and do not need to purchasehardware Cloud providers manage the infrastructure and poolresources into capacity required by consumersCloudConsumerPrivate Deployed inside the firewall and managed by the userorganization User organization owns the software and hardware runningin the cloud User organization manages the cloud and provides cloudresources Resources typically not shared outside the organizationand full control is retained by the organizationCloudProviderArchitectural Implications of Cloud ComputingSATURN 20118May 18, 2011 2011 Carnegie Mellon University
Drivers for Cloud Computing AdoptionScalabilityOrganizations have access to a large amount of resources that scalebased on user demandElasticityOrganization’s can manually or dynamically decide on resourceutilization based on changing needsVirtualizationEach user has a single view of the available resources,independently of how they are arranged in terms of physical devicesLowerInfrastructureCostsThe pay-per-use model allows an organization to only pay for theresources they need with basically no investment in the physicalresources available in the cloud. There are no infrastructuremaintenance or upgrade costsAvailabilityOrganizations have the ability for the user to access data andapplications from around the globeCollaborationOrganizations are starting to see the cloud as a way to worksimultaneously on common data and informationRisk ReductionOrganizations can use the cloud to test ideas and concepts beforemaking major investments in technologyReliabilityIn order to support SLAs (service-level agreements), cloud providershave reliability mechanisms that are much more robust than thosethat could be cost-effectively provided by a single organizationArchitectural Implications of Cloud ComputingSATURN 20119May 18, 2011 2011 Carnegie Mellon University
Barriers for Cloud Computing AdoptionSecurityThe key concern is data privacy: organizations do not havecontrol of or know where their data is being storedInteroperabilityA universal set of standards and/or interfaces has not yet beendefined, resulting in a significant risk of vendor lock-inResourceControlThe amount of control that the organization has over the cloudenvironment varies greatlyLatencyAll access to the cloud is done via the internet, introducinglatency into every communication between the user and theenvironmentPlatform orLanguageConstraintsSome cloud environments provide support for specific platformsand languages onlyRegulationThere are concerns in the cloud computing community overjurisdiction, data protection, fair information practices, andinternational data transferArchitectural Implications of Cloud ComputingSATURN 201110May 18, 2011 2011 Carnegie Mellon University
AgendaBasic Cloud Computing ConceptsArchitectural Implications of Cloud ComputingFinal ThoughtsArchitectural Implications of Cloud ComputingSATURN 201111May 18, 2011 2011 Carnegie Mellon University
IaaS: Examples of Architecture and DesignQuestionsHow are resourceWhat communicationmechanisms existbetween the consumerand the cloud resource?Whatcomputationis performedin the cloud?A fullapplication?Only certainfunctionality?failures detected andcommunicated? Howare SLA commitmentsmaintained andmonitored?What data isstored in thecloud? Is itsynchronizedwith other sets ofdata? Are theredata privacyconcerns?What securitymechanismsare provided bythe cloudresource?Systems residing in the cloud or using resources from the cloudwill have to be designed and architected to account for lack offull control over important quality attributesArchitectural Implications of Cloud ComputingSATURN 201112May 18, 2011 2011 Carnegie Mellon University
PaaS: Examples of Architecture and DesignQuestionsWill cloud resources always be active?Is a cloud bursting strategy appropriate?Where do externalusers authenticate?What data isstored in thecloud? Is itpossible for thesystem to run inthe cloud and thedata to remainlocal?Are all systemelementscompatible withthe cloudplatform? Areadaptersnecessary?Architectural Implications of Cloud ComputingSATURN 201113May 18, 2011 2011 Carnegie Mellon University
SaaS: Examples of Architecture and DesignQuestionsHow does the cloudsystem fit with theexisting infrastructure?What type of client isused to interact with theSaaS resource?What dataadapters andtransformers arenecessary tointeroperate withother systems?What additionalmechanisms need tobe put in place tomonitor systemperformance andusage?Is the SaaS securityarchitecture compatiblewith the organization’ssecurity architecture?Architectural Implications of Cloud ComputingSATURN 201114May 18, 2011 2011 Carnegie Mellon University
Cloud ConsumerExample Decision # 1: Data ModelTypical decisions of a distributed environment Local vs. RemoteTotal vs. PartitionedDistributed vs. CentralizedActive Replication vs. Passive ReplicationData Security ModelChallenges Data privacy Data synchronization Performancewww.jasonkolb.comArchitectural Implications of Cloud ComputingSATURN 201115May 18, 2011 2011 Carnegie Mellon University
Cloud ConsumerExample Decision # 2: User Authentication ModelAuthentication is the mechanism by which consumers and providersprove to one another that they are acting on behalf of specific users orsystemsTypical decisions of a distributed, multi-organizational environment Local vs. Remote AuthenticationSingle Sign-On or Separate AuthenticationLocal or Remote Identity DataAuthentication MethodChallenges Incompatible authentication methodsPhysical security of identity dataSynchronization of identity dataAuditingblogs.verisign.comArchitectural Implications of Cloud ComputingSATURN 201116May 18, 2011 2011 Carnegie Mellon University
Cloud ConsumerExample Decision # 3: Allocation ofFunctionalityDecisions depend on the type of cloud implementation What functionality to deploy in the cloud? What functionality has to be implemented in addition to thefunctionality offered by the cloud provider?– Security– Management– Abstraction layers, e.g. data access, omArchitectural Implications of Cloud ComputingSATURN 201117May 18, 2011 2011 Carnegie Mellon University
Cloud ConsumerExample Decision # 4: Cloud BurstingRefers to a system that is designed for average load, but is capable ofload balancing to a cloud when it reaches its full capacityDecisions Activation, initialization and de-activation of the cloud resourceState and data synchronizationComputational elements to determine full capacityComputational elements for monitoring load and ral Implications of Cloud ComputingSATURN 201118May 18, 2011 2011 Carnegie Mellon University
Cloud ConsumerExample Decision # 5: Cloud ResourceManagementDecisions Elements for failure detection and communication Elements for SLA monitoring Logging: where, what and whenblogumn.comArchitectural Implications of Cloud ComputingSATURN 201119May 18, 2011 2011 Carnegie Mellon University
Cloud ProviderExample Decision #1: Multi-Tenancy 1Mainly in SaaS implementations, a tenant is an organization that makesuse of cloud resourcesMulti-tenancy requires Awareness of tenant context: the capability of recognizing the identity of thetenant requesting the resources based on message information as well asconfiguration data Data isolation: tenants should only have access to their own data Performance isolation: resource performance should conform to service-levelagreements, regardless of the load on the systemi.zdnet.comArchitectural Implications of Cloud ComputingSATURN 201120May 18, 2011 2011 Carnegie Mellon University
Cloud ProviderExample Decision #1: Multi-Tenancy 2Oneoption isto haveoneinstancepertenantOption 1Another optionis to have asingle instancethat usestenantconfigurationdata to providetenant contextOption 2Option 3Another optionis to havemultipleidenticalinstances thatare managedby a loadbalancerHybrid optionsare alsopossibleArchitectural Implications of Cloud ComputingSATURN 201121May 18, 2011 2011 Carnegie Mellon University
Cloud ProviderExample Decision #2: Virtualization Strategy 1Virtualization in general is the abstraction of computing resources, e.g. Network virtualization: division of available bandwidth into channels that canbe assigned to a particular resource in real time Storage virtualization: combination of physical storage devices into whatappears to be a single storage device , e.g. SAN (storage area network) Server virtualization: hiding of server resources (number and identity ofindividual physical servers, processors, and operating systems) from serverusers, e.g. VMs (virtual i/bto/20090528/Virtualization stack 270x258.jpgArchitectural Implications of Cloud ComputingSATURN 201122May 18, 2011 2011 Carnegie Mellon University
Cloud ProviderExample Decision #2: Virtualization Strategy 2Server Virtualization ExampleOS canexecuteotherapplications,e.g. neHowever,there is aperformancepenaltyMain question is “How and when are virtualmachines deployed, started, initialized, deactivated, replaced, managed andterminated?”Architectural Implications of Cloud ComputingSATURN 201123May 18, 2011 2011 Carnegie Mellon University
Cloud ProviderExample Decision #3: Resource Interfaces 1Cloud APIs are not yet standardized, so each cloud provider has its ownspecific APIs for managing its servicesCurrently, most Cloud APIs are SOAP- or REST-basedArchitectural Implications of Cloud ComputingSATURN 201124May 18, 2011 2011 Carnegie Mellon University
Cloud ProviderExample Decision #3: Resource Interfaces 2Supported ProtocolsOperations Functionality Configuration ManagementQoS Support Security Usability ConfigurabilitySample Amazon EC2 Operations (IaaS) Create Image Stop Instances Create Security Group Monitor InstancesSample Google App Engine Operations (PaaS) Upload Application Code Authenticate User Send E-mailSample Zoho.com Operations (SaaS) Set Up Application View Application Usage Data Embed in “X”Architectural Implications of Cloud ComputingSATURN 201125May 18, 2011 2011 Carnegie Mellon University
AgendaBasic Cloud Computing ConceptsArchitectural Implications of Cloud ComputingFinal ThoughtsArchitectural Implications of Cloud ComputingSATURN 201126May 18, 2011 2011 Carnegie Mellon University
Cloud Computing is at the “Peak of Inflated Expectations”Source: Gartner, Hype Cycle for Emerging Technologies, 2009Architectural Implications of Cloud ComputingSATURN 201127May 18, 2011 2011 Carnegie Mellon University
The Concept of Private Clouds is Starting to AppearSource: Gartner, Hype Cycle for Emerging Technologies, 2010Architectural Implications of Cloud ComputingSATURN 201128May 18, 2011 2011 Carnegie Mellon University
Final Thoughts 1Cloud Computing is in essence an economic model It is a different way to acquire and manage IT resourcesThere are multiple cloud providers—the cloud is real Currently most cloud consumers are small enterprises Large enterprises are exploring private clouds The number of providers will most probably grow as people start seeinggreater savings and improvements to reduce adoption barriersCloud Computing adoption requires cost/benefit/risk analysis todetermine What resources to move to the cloud (if any)What situations warrant use of cloud resources, even for one-time situationsImplementation of private clouds vs. usage of public cloudsWhat risks are associated with using resources on the cloudWhat risks are associated to providing resources in the cloudArchitectural Implications of Cloud ComputingSATURN 201129May 18, 2011 2011 Carnegie Mellon University
Final Thoughts 2Decisions from a cloud consumer perspective depend on Required control level Required security level Compatibility with local infrastructureDecisions from a cloud provider perspective depend on Market/user characteristics Established SLAs Available technologyaskbobrankin.comIn general, these are not fully technical decisions Processes — especially engineering practices Governance Cost/Benefit analysisArchitectural Implications of Cloud ComputingSATURN 201130May 18, 2011 2011 Carnegie Mellon University
Cloud Provider and Tool References 3tera: http://www.3tera.com/ Akamai EdgePlatform: .html Amazon Elastic Compute Cloud (EC2): http://aws.amazon.com/ec2/ Amazon Simple Storage Solution (S3): http://aws.amazon.com/s3/ Eucalyptus Systems: http://www.eucalyptus.com/ Force.com: http://www.salesforce.com/platform/ Google App Engine: http://code.google.com/appengine/ Google Apps: html IBM Computing On Demand: http://www-03.ibm.com/systems/deepcomputing/cod/ Microsoft Azure Services Platform: http://www.microsoft.com/azure/ Microsoft Live Mesh: http://www.mesh.com/ Salesforce.com: http://www.salesforce.com/crm/products.jsp Ubuntu: http://www.ubuntu.com/cloud Yahoo! Open Strategy (Y!OS): http://developer.yahoo.com/yos/intro/ Zoho: http://www.zoho.com/Architectural Implications of Cloud ComputingSATURN 201131May 18, 2011 2011 Carnegie Mellon University
Contact InformationGrace A. LewisResearch, Technology and Systems Solutions (RTSS) ProgramSystem of Systems Practice (SoSP) InitiativeSoftware Engineering Institute4500 Fifth AvenuePittsburgh, PA 15213-2612USAPhone: 1 412-268-5851Email: glewis@sei.cmu.eduWWW: itectural Implications of Cloud ComputingSATURN 201132May 18, 2011 2011 Carnegie Mellon University
NO WARRANTYTHIS MATERIAL OF CARNEGIE MELLON UNIVERSITY AND ITS SOFTWAREENGINEERING INSTITUTE IS FURNISHED ON AN “AS-IS" BASIS. CARNEGIEMELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSEDOR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTYOF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTSOBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOESNOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROMPATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT.Use of any trademarks in this presentation is not intended in any way to infringe on therights of the trademark holder.This Presentation may be reproduced in its entirety, without modification, and freelydistributed in written or electronic form without requesting formal permission. Permissionis required for any other use. Requests for permission should be directed to the SoftwareEngineering Institute at permission@sei.cmu.edu.This work was created in the performance of Federal Government Contract NumberFA8721-05-C-0003 with Carnegie Mellon University for the operation of the SoftwareEngineering Institute, a federally funded research and development center. TheGovernment of the United States has a royalty-free government-purpose license to use,duplicate, or disclose the work, in whole or in part and in any manner, and to have orpermit others to do so, for government purposes pursuant to the copyright license underthe clause at 252.227-7013.Architectural Implications of Cloud ComputingSATURN 201133May 18, 2011 2011 Carnegie Mellon University
Cloud Computing “A large-scale distributed computing paradigm that is driven by economies of scale, in which a pool of abstracted, virtualized, dynamically-scalable, managed computing power, storage, platforms, and services are delivered on demand to external customers over the Internet.” * 3 Architectural Implications of Cloud Computing .
Chapter 10 Cloud Computing: A Paradigm Shift 118 119 The Business Values of Cloud Computing Cost savings was the initial selling point of cloud computing. Cloud computing changes the way organisations think about IT costs. Advocates of cloud computing suggest that cloud computing will result in cost savings through
Cloud Computing J.B.I.E.T Page 5 Computing Paradigm Distinctions . The high-technology community has argued for many years about the precise definitions of centralized computing, parallel computing, distributed computing, and cloud computing. In general, distributed computing is the opposite of centralized computing.
Mobile Cloud Computing Cloud Computing has been identified as the next generation’s computing infrastructure. Cloud Computing allows access to infrastructure, platforms, and software provided by cloud providers at low cost, in an on-demand fashion. Mobile Cloud Computing is introduced as an int
Cloud Computing What is Cloud Computing? Risks of Cloud Computing Practical Applications Benefits of Cloud Computing Adoption Strategies 5 4 3 2 1 Q&A What the Future Holds 7 6 Benefits of Cloud Computing Reduced Cost for Implementation Flexibility Scalability Disaster Relief Multitenancy Virtualization Pay incrementally Automatic Updates
UNIT 5: Securing the Cloud: Cloud Information security fundamentals, Cloud security services, Design principles, Policy Implementation, Cloud Computing Security Challenges, Cloud Computing Security Architecture . Legal issues in cloud Computing. Data Security in Cloud: Business Continuity and Disaster
Cloud computing "Cloud computing is a computing paradigm shift where computing is moved away from personal computers or an individual application server to a "cloud" of computers. Users of the cloud only need to be concerned with the computing service being asked for, as the underlying details of how it is achieved are hidden.
The rationale of cloud computing (for the customer) is reduced and linearly scaling costs. Cloud computing allows allocating required computing resources dynamically to demand. It scales linearly with the number of users, i.e. incurs no or little capital expenses (capex), only operating expenses (opex). Traditional IT: Cloud computing: Users .
Grade 2 collected 25 books. Grade 3 collected 15 books. Grade 4 collected 10 books. The school had a book drive to support the local shelter. Grades 1, 2, 3, and 4 collected books. Organize the book data into the pictograph above. 1. Who collected the most books? _ 2. What was the total amount of books collected? _ 3. Which grade .
