THE DATA CENTER AS A COMPUTER

Transcription

1 THE DATA CENTER AS A COMPUTER Cloud Computing November FIB-UPC Master MEI

2 CLOUD COMPUTING It s here to stay

3 CONTENT 1. How do we get here? 2. What is Cloud Computing? 3. Definitons and types 4. Case study: AWS 5. Cloud Computing Inhibitors 6. Virtualization: The pillar of Clud Computing 7. Homework

4 HOW DO WE GET HERE? Pilot ACE, UK.1950

5 EVERY 15 YEARS A major technological jump in IT TIC That has redefined IT and industry in general

6 MAINFRAMES Mainframes

7 PERSONAL COMPUTERS Personal Computers Mainframes

8 INTERNET Internet Personal Computers Mainframes

9 INDUSTRIALIZATION OF IT Internet Huge Data Centers Personal Computers Mainframes

10 HUGE DATA CENTERS m2 40 Mw Source: set/?set=a

11 HUGE DATA CENTERS Foto: Google

12 HUGE DATA CENTERS Foto: Google > football pitch x 4

13 HUGE DATA CENTERS Foto: cortesía BSC Industrialization of IT: has arrived!

14 Source:

15 Source:

16 Source:

17 WHERE DO WE FIND DC? foto: Google

18 WHERE DO WE FIND DC? foto: Google Energy price: 0,03-0,04 /kwh

19 ENERGY CONSUMPTION Foto: cortesía BSC 1W IT 1 or 0,7 W cooling

20 ENERGY CONSUMPTION

21 NETWORKS & UNDERSEA CABLE foto: foto:

22 CONTENT 1. How do we get here? 2. What is Cloud Computing? 3. Definitons and types 4. Case study: AWS 5. Cloud Computing Inhibitors 6. Virtualization: The pillar of Clud Computing 7. Homework

23 IT AS A SERVICE Cloud Computing represents a major change in IT service architecture, delivery and consumption Foto: J.T.

24 IT AS A SERVICE Amazon Data Center Foto: Tutorial SC Robert Grossman (*) IaaS

25 IT AS A SERVICE More flexible IT, which can adapt to businesses and where costs can be predicted Ubiquitous access Rapid elasticity Pay per use On-demand self-service....

26 UTILITY COMPUTING Illusion of infinite computing resources available on demand no need for users to plan ahead for provisioning No up-front cost or commitment by users companies can start small increase resources only when there is an increase in need Pay for use on short-term basis as needed processors by the hour and storage by the day release them as needed, reward conservation

27 EXAMPLE: WORKLOAD

28 SYSTEM CAPACITY Capacity Resources Demand Time

29 RESOURCES NOT USED Resources not used Capacity Resources Demand Time

30 WASTE OF RESOURCES Resources Capacity Demand Time

31 CUSTOMER BEHAVIOR Resources Capacity Demand Time (days)

32 CUSTOMER BEHAVIOR Resources Capacity Demand Time (days)

33 CLOUD COMPUTING ELASTICITY Resources Capacity Demand Time

34 CONTENT 1. How do we get here? 2. What is Cloud Computing? 3. Definitons and types 4. Case study: AWS 5. Cloud Computing Inhibitors 6. Virtualization: The pillar of Clud Computing 7. Homework

35 TYPES OF CLOUDS Software as a Service (SaaS) Plataforma as a Service (PaaS) Infraestructura as a Service (IaaS)

36 INFRAESTRUCTURE AS A SERVICE 1 computer in a rack for 120 hours 120 computers in three racks for 1 hour Idea : Tutorial SC Robert Grossman

37 AGILITY FOR SUPPLYING vs in house data center Fotos: cortesía BSC

38 TYPES OF CLOUDS Tradicional IaaS PaaS SaaS Apps Apps Apps Apps Frameworks Frameworks Frameworks Frameworks VM VM VM VM Server Server Server Server models of service delivery

39 Enterprise resources Data+ Programs + Hardware SCENARIO CLOUD electronic devices with identification/computing/storage/communication capabilities User Sep 2011

40 INSIDE THE CLOUD Enterprise resources Data+ Programs + Hardware PUBLIC CLOUD PRIVATE CLOUD electronic devices with identification/computing/storage/communication capabilities User

41 SELF MANAGED CLOUD Enterprise resources Data+ Programs + Hardware PUBLIC CLOUD Intelligent & autonomic management of resources PRIVATE CLOUD Client-aware Services Services that intelligent take advantage of user devices capabilities as mobile or context-aware electronic devices with identification/computing/storage/communication capabilities User

42 HYBRID CLOUD Workload

43 HYBRID CLOUD capacity Workload

44 HYBRID CLOUD capacity

45 HYBRID CLOUD External Provider

46 EVERYTHING AS A SERVICE IaaS PaaS SaaS XaaS DRaaS SUaaS BDaaS

47 CLOUD DEFINITION The NIST definition is the most precise and also most referred: Cloud computing is a model for enabling ubiquitous, convenient, ondemand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction composed of: five essential characteristics, three service models, and four deployment models. Source: These slides are extracted from «Cloud Computing Synopsis and Recomendations» National Institute of Standards and Technology, Special Pub , May 2012

48 CLOUD DEFINITION SOURCE:

49 Essential characteristics five essential characteristics: On-demand self-service. A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service s provider. Broad network access. Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, tablets, laptops, and workstations). Resource pooling. The provider s computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. There is a sense of location independence in that the customer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter). Examples of resources include storage, processing, memory, and network bandwidth. 49

50 Essential characteristics five essential characteristics (cont.): Rapid elasticity. Capabilities can be rapidly and elastically provisioned, in some cases automatically, to scale rapidly outward and inward commensurate with demand. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be appropriated in any quantity at any time. Measured Service. Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service. 50

51 Three Service Models Cloud Software as a Service (SaaS). The capability provided to the consumer is to use the provider s applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a Web browser, or a program interface. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited userspecific application configuration settings. Cloud Platform as a Service (PaaS). The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or -acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations. 51

52 Three Service Models Cloud Infrastructure as a Service (IaaS). The capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications; and possibly limited control of select networking components (e.g., host firewalls). 52

53 Deployment models 4 deployment models: Private cloud. The cloud infrastructure is provisioned for exclusive use by a single organization comprising multiple consumers (e.g., business units). It may be owned, managed, and operated by the organization, a third party, or some combination of them, and it may exist on or off premises. Community cloud. The cloud infrastructure is provisioned for exclusive use by a specific community of consumers from organizations that have shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be owned, managed, and operated by one or more of the organizations in the community, a third party, or some combination of them, and it may exist on or off premises. 53

54 Deployment models 4 deployment models (cont.): Public cloud. The cloud infrastructure is provisioned for open use by the general public. It may be owned, managed, and operated by a business, academic, or government organization, or some combination of them. It exists on the premises of the cloud provider. Hybrid cloud. The cloud infrastructure is a composition of two or more distinct cloud infrastructures (private, community, or public) that remain unique entities, but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load balancing between clouds)." 54

55 Typical Commercial Terms of Service A consumer s terms of service for a cloud are determined by a legally binding agreement between the two parties often contained in two parts: (1) a service agreement, and (2) a Service Level Agreement (SLA). (*) Generally, the service agreement is a legal document specifying the rules of the legal contract between a consumer and provider, and the SLA is a shorter document stating the technical performance promises made by a provider including remedies for performance failures. For simplicity, this publication refers to the combination of these two documents as a service agreement. 55

56 Typical Commercial Terms of Service Published service agreements between consumers and providers can typically be terminated at any time by either party, either for cause such as a consumer s violation of a cloud s acceptable use policies, or for failure of a consumer to pay in a timely manner. Further, an agreement can be terminated for no reason at all. Consumers should analyze provider termination and data retention policies. Provider promises, including explicit statements regarding limitations, are codified in their service agreements. 56

57 Typical Commercial Terms of Service A provider s service agreement has three basic parts: 1. a collection of promises made to consumers, 2. a collection of promises explicitly not made to consumers, i.e., limitations 3. a set of obligations that consumers must accept. 57

58 Promises Availability Providers typically advertise availability promises as uptime percentages ranging from 99.5 percent to percent. These are strong claims, and care is needed to understand how these percentages are calculated. Often, the percentage applies to the number of time intervals within a billing cycle (or longer periods such as a year) in which services are not up for the entire interval. Remedies for Failure to Perform. If a provider fails to give the promised availability, a provider should compensate subscribers in good faith with a service credit for future use of cloud services. 58

59 Classifying Systems According to Availability 59

60 Promises (cont.) Data Preservation. If a subscriber s access to cloud services is terminated for cause, i.e., because the subscriber has violated the clouds' acceptable use policy or for nonpayment, most providers state that they have no obligation to preserve any subscriber data remaining in cloud storage. Legal Care of Subscriber Information. Generally, providers promise not to sell, license, or disclose subscriber data except in response to legal requests. Providers, however, usually reserve the right to monitor subscriber actions in a cloud, and they may even demand a copy of subscriber software to assist in that monitoring. 60

61 Limitations Scheduled Outages. If a provider announces a scheduled service outage, the outage does not count as failure to perform. Force majeure events. Providers generally disclaim all responsibility for events outside their realistic control. Examples include power failures, natural disasters, and failures in network connectivity. SLA Changes. Providers generally reserve the right to change the terms of the SLA at any time, and to change pricing with limited advanced notice.. 61

62 Limitations ( cont.) Security. Providers generally assert that they are not responsible for security, i.e., unauthorized modification or disclosure of subscriber data, or for service interruptions caused by malicious activity. Generally, SLAs are explicit about placing security risks on subscribers. In some cases, providers promise to use best efforts to protect subscriber data, but all of the providers surveyed disclaim security responsibility for data breach, data loss, or service interruptions by limiting remedies to service credits for failure to meet availability promises. Further, it is unclear how easy it would be for a subscriber to determine that a service disruption was maliciously induced versus induction from another source. Service API Changes. Providers generally reserve the right to change or delete service APIs at any time. 62

63 Subscribers Obligations Acceptable Use Polices. Subscribers generally must agree to refrain from storing illegal content, such as child pornography, and from conducting illegal activities such as: (1) gambling, (2) sending spam, (3) conducting security attacks (e.g., denial of service or hacking), (4) distributing spyware, (5) intrusive monitoring, and (6) attempting to subvert cloud system infrastructures. Licensed Software. All providers state that third-party software running in their clouds must conform to the software s license terms. In some cases, providers bundle such software and include monitoring to ensure that license restrictions are enforced. Timely Payments. 63

64 SUMMARY Source: Security Guidance for Critical Areas of Focus in Cloud Computing, April Cloud Security Alliance. Hundreds of companies on stage