IBM ICE (Innovation Centre for Education) Welcome to: Unit 1 Overview of delivery models in Cloud Computing. Copyright IBM Corporation

Transcription

1 Welcome to: Unit 1 Overview of delivery models in Cloud Computing 9.1

2 Unit Objectives After completing this unit, you should be able to: Understand cloud history and cloud computing Describe the anatomy of Cloud Explain the benefits of Cloud Define cloud transformation roadmap Identify cloud delivery models and explain their advantages Cloud Computing Architecture Copyright IBM Corporation 2015

3 Overview Cloud delivers IT as a service to business with the following characteristics: The cloud services are available on demand and can scale up or down based on usage You do not need to own a datacenter to use hardware or software services The excess capacity goes into a general pool and used by someone else You have an option to subscribe or unsubscribe to services delivered in the cloud Monitoring allows for more granular optimization of usage of resources in the cloud The provider will share a SLA(Service Level Agreement) for the services in the catalog The cloud services could be accessed using a standard interface The subscriber gets charged for the services subscribed and the periodic usage A large part of cloud operations is automated. The process is known as orchestration. 3

4 Cloud Definition The Cloud NIST definition is as follows: "Cloud computing is a model for enabling, convenient, on-demand 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. 4

5 Key characteristics of cloud 1. Broad network access 2. On-demand self-service (Self Provisioning) 3. Rapid elasticity 4. Measured service 5. Resource pooling 5

6 Service Models and Deployment Models Deployment Models 1. Private Cloud 2. Public Cloud 3. Hybrid Cloud 4. Community Cloud 6

7 Service Models and Deployment Models Delivery Models or Service Models 1. IaaS (Infrastructure as a Service) 2. PaaS (Platform as a Service) 3. SaaS (Software as a Service) 7

8 Cloud History (Cloud Roots) Cloud roots can be tracked by observing the advancement of several technologies, especially in hardware (virtualization, multi-core chips), Internet technologies (Web services, service-oriented architectures, Web 2.0), distributed computing (clusters, grids), and systems management (autonomic computing, data center automation). 8

9 Cloud History (Cloud Roots) 9

10 Cloud History (Cloud Roots) Few important terms in this context. SOA WEB 1.0 WEB 2.0 WEB 3.0 IoT Mashup 10

11 Cloud History (Cloud Roots) Distributed computing (Utility and Grid Computing) 11

12 Cloud History (Cloud Roots) Few important terms in this context Utility Computing Grid Computing Cluster 12

13 Utility computing Utility Computing is a service provisioning model in which a service provider makes computing resources and infrastructure management available to the customer as needed, and charges them for specific usage rather than a flat rate. Like other types of on-demand computing (such as grid computing), the utility model seeks to maximize the efficient use of resources and/or minimize associated costs. Utility is the packaging of computing resources, such as computation, storage and services, as a metered service. This model has the advantage of a low or no initial cost to acquire computer resources; instead, computational resources are essentially rented. 13

14 Grid computing (1 of 2) With an exponential increase in information generation, an infrastructure was required that could scale well with the size of job under consideration. This problem was solved by Grid Computing in the 1990s. Grid computing allowed computers from different administrative domains to run workloads in parallel. Grid computing formed a distributed network of loosely-coupled geographically dispersed computers working towards a common goal. This allowed sharing of computing resources like a utility, ex: electricity. A grid infrastructure is not owned by any one entity but can be used in entirety, on a sharing basis by all participating users. 14

15 Grid computing (2 of 2) Grid computing is a type of parallel and distributed system that enables sharing, selection, and aggregation of geographically distributed autonomous resources dynamically at run-time depending on their availability, capability, performance, cost, and users quality-of-service requirements for solving large-scale compute and data intensive applications such as brain activity analysis, high energy physics etc. Computing grids harness distributed computer power and coordinate the execution of application at internet scale, for the purpose of reducing computation time. 15

16 Cluster A computer cluster is a group of linked computers, working together closely so that in many respects they form a single computer. The components of a cluster are commonly, but not always, connected to each other through fast local area networks. 16

17 Hardware Figure 2 17

18 Cloud History (Cloud Roots) 18

19 Virtual Machine Monitor(VMM) platforms VMWare ESXi Xen KVM 19

20 Virtual Appliances and the Open Virtualization Format 20

21 System Management ( 1 of 2) With the increase in the complexity of computing systems, which in turn motivated the research on autonomic computing, which seeks to improve systems by decreasing human involvement in their operation. In other words, systems should manage themselves, with high-level guidance from humans. Autonomic, or self-managing, systems rely on monitoring probes and gauges (sensors), on an adaptation engine (autonomic manager) for computing optimizations based on monitoring data, and on effectors to carry out changes on the system. IBM s Autonomic Computing Initiative has contributed to define the four properties of autonomic systems as follows : 1. Self-configuration 2. Self-optimization 3. Self-healing 4. Self-protection 21

22 System Management ( 2 of 2) IBM has also suggested a reference model for autonomic control loops of autonomic managers, called MAPE-K (Monitor Analyze Plan Execute Knowledge). The large data centers of cloud computing providers must be managed in an efficient way. In this sense, the concepts of autonomic computing inspire software technologies for data center automation, which may perform tasks such as: management of data center capacity, management of service levels of running applications, proactive disaster recovery and automation of VM provisioning. 22

23 Anatomy of a cloud A cloud is composed of seven major components. 1. Provisioning and Configuration Module 2. Monitoring and Optimization 3. Metering and Chargeback 4. Orchestration 5. CMDB (Configuration Management Database) 6. Cloud Lifecycle Management Layer 7. Service Catalog 23

24 Cloud components Each component serves a specific function in Cloud. Not all components are present in every Cloud solution available in the market. Cloud vendors may choose to implement a subset of features to suit their end-user requirements. The choice of components may also depend on the Delivery model. Some of these components may also be partially implemented depending on the deployment model used for Cloud. 24

25 Cloud computing solution components A cloud computing solution is the end-to-end integration of components, each bringing a specific value to the whole User/IT self service Improving customer satisfaction and responsiveness Standardized delivery models Utilize service catalog of standard components. Capacity management Reservation with connection to platform configuration Controlled anticipation Validated change requests with automated approval workflow process Low or no touch deployment Drive down operational costs and manage thru full life-cycle Deploy new systems faster Shorter leads times, quicker to market, agility, competitive advantage Improve server and power utilization Cost avoidance on new hardware, energy and cooling costs Consistency of configuration Driving compliance, easier support and auditing, consistent security. 25

26 Service Catalog All offerings that the cloud can provide in a standard way but customizable through parameters End user will be offered a means (command/gui) to consume what is represented by service catalog entries Service creation Service modification Service termination Entries in the service catalog are reflected in a service template Service topology to offer Service instance process creation details Associated management functions Service is defined by technical artifacts Virtual image with contained operating system, middleware and software, associated VM definitions, and so on. 26

27 User self service portal Accessing the offerings in the self-service interface Approvals and notifications Creating a project and adding virtual servers Creating a project from a saved server image Canceling a project Modifying project Modifying server Backing up and restoring server images Managing image library Managing users Viewing requests Viewing the details of a submitted request Viewing and managing requests for approval Viewing projects Viewing and managing servers User roles 27

28 Service request management All aspects in between user actions on the portal and service deployment with provisioning Business workflows between cloud users like approval Mail integration to disseminate information and transaction lists identifying services being requested Capacity planning and reservation Change management allowing reconfiguration of the deployed service 28

29 Provisioning Provisioning is one of the key processes that accelerated the emergence of cloud Automation of pre-defined scenarios to ensure their repetitive, efficient, and reliable execution Execution steps described in provisioning workflows Provisioning runtime monitoring workflow execution to proper completion or stable recovery stage Goal is to keep workflow tasks as generic and platform independent as possible; To implement workflow steps on specific platforms To leverage existing tools and skills To integrate provisioning with future service production To limit the number of workflows to be developed and maintained Provisioning used in cloud computing as well as runtime automation in data centers 29

30 Optimized infrastructure Cloud computing provides a means to manage large numbers of highly virtualized resources and control the delivery of services on these. An optimized infrastructure for cloud Scalable Available Therefore it has to be: Virtualized Managed So all the infrastructure components (servers, storage and networks) can be automatically defined and deployed. 30

31 Chargeback Chargeback is the component which supports the pay per use functions. Based on metrics provided by the optimized infrastructure Establishes a cost for delivered services Charges are generally based on what the user uses CPU, memory, storage Metrics which could be linked to a specific workload Metrics which can be specific to a customer environment Chargeback model agreement between cloud provider and cloud consumer 31

32 What is different about cloud computing? Without cloud computing With cloud computing Virtualized resources Automated service management Standardized services Location independent Rapid scalability Self-service Software Hardware Storage Networking Software Hardware Storage Networking Software Hardware Storage Networking 32

33 Benefits of cloud (1 of 3) Provisioning is automated and on-demand and can be done on a self-service basis. The provisioning typically takes from few seconds to few hours. Also, the demand for resources can be estimated well in advance to plan for procurement of hardware. Utilization typically is around 60-70%. The freed up resources goes into a pool which can be assigned transparently to other users. It is also possible to downscale and upscale based on demand. Scalability is on-demand. Capacity can be planned and operational expenses can be fine-tuned to meet the current demand. Availability: Typically the VM instances are not tied to any particular hardware. Rather they are designed to run over a range of hardware. Hence, it is possible to restart the instance on secondary hardware if the primary hardware fails. This happens automatically and transparently. Elasticity allows scaling up and down ondemand. 33

34 Benefits of cloud (2 of 3) Capital Expenditure: Depending on the cloud deployment, a customer saves about 40% in upfront capital expenditure required to procure hardware. The operational expense can be further fine tuned based on demand, thus resulting in much higher savings. Chargeback allows for more granular monitoring of usage of resources in terms of cost. This opens up avenues for further optimization. Monitoring in cloud allows for further optimization of resources for maximum utilization and reduced wastage. This results in higher savings over time. Based on the cloud implementation, the savings in Cloud may vary. There are multiple factors that may impact the features of Cloud and the savings and benefits inherent in Cloud. 34

35 Benefits of cloud (3 of 3) 35

36 Cloud transformation roadmap (1 of 2) An organization planning to transform their infrastructure to Cloud move through three major stages of evolution. Consolidation and Virtualization Automation and Optimization Integration of Service Management 36

37 Cloud transformation roadmap (2 of 2) 37

38 Cloud Delivery models and their advantages IaaS (Infrastructure as a Service) SaaS (Software as a Service) PaaS (Platform as a Service) BPaaS ( Business Process as a Service) 38

39 Infrastructure as a Service (IaaS) Provides data center, infrastructure hardware and software resources to users via the Internet; applications are delivered as a virtualization platform by the cloud provider and can be accessed across the Internet. Features Virtualization Cloudbursting Mulit-tenancy Resource pooling Advantages Utility service Dynamic elasticity Multiple tenants Fixed costs Flexible access Green IT 39

40 Platform as a Service (PaaS) In the PaaS model, cloud providers deliver a computing platform typically including operating system, programming language execution environment, database, and web server. Application developers can develop and run their software solutions on a cloud platform without the cost and complexity of buying and managing the underlying hardware and software layers. Features Ease of use Simplicity Automation Multi-tenant Architecture Integration with web services and databases Advantages Cost savings Shortened application delivery Increased adaptability With some PaaS offers, the underlying computer and storage resources scale automatically to match application demand such that cloud user does not have to allocate resources manually. 40

41 Software as a Service (SaaS) SaaS provides a web/internet based access to software applications. The user is relieved of maintaining any licenses, patches for the provided software. The user can use the software on a subscription basis and pay for only the duration it was used. Features Configuration and Customization Advantages High adoption Accelerated feature delivery Open integration protocols Collaborative (and social ) functionality Lower initial costs Painless upgrades Seamless integration 41

42 Business Process as a Service (BPaaS) Business process services are any business process (horizontal or vertical) delivered through the Cloud service model (Multi-tenant, self-service provisioning, elastic scaling and usage metering or pricing) via the Internet with access via Web-centric interfaces and exploiting Web-oriented cloud architecture. The BPaaS provider is responsible for the related business function(s). Examples are processes for employee benefit management, business travel, procurement or also IT-centric processes such as software testing (where the entire testing process including testing staff is provided as an externally hosted cloud service). Advantages of BPaaS Decreased costs from not buying and maintaining servers to manage and coordinate business process. Pay-as-you-go pricing model Increased mobility, by accessing the solution from any geographical point. This allows usinesses the opportunity to grow and expand much faster. Scalability by allowing companies to add new processes without much infrastructural cost 42

43 Cloud Computing Architecture (1 of 2) Cloud computing architecture refers to the components and subcomponents required for cloud computing. These components typically consist of a front end platform (fat client, thin client, mobile device), back end platforms (servers, storage), a cloud based delivery, and a network (Internet, Intranet, Intercloud). Combined, these components make up cloud computing architecture. Cloud client platforms Cloud computing architectures consist of front-end platforms called clients or cloud clients. These clients comprise servers, fat (or thick) clients, thin clients, zero clients, tablets and mobile devices. These client platforms interact with the cloud data storage via an application (middleware), via a web browser, or through a virtual session. The zero client The zero or ultra-thin client initializes the network to gather required configuration files that, then tell it where its OS binaries are stored. The entire zero client device runs via the network. This creates a single point of failure, in that, if the network goes down, the device is rendered useless. 43

44 Cloud Computing Architecture (2 of 2) Cloud storage A online network storage where data is stored and accessible to multiple clients. Cloud storage is generally deployed in the following configurations: public cloud, private cloud, community cloud, or some combination of the three also known as hybrid cloud. In order to be effective, the cloud storage needs to be agile, flexible, scalable, multitenancy, and secure. Cloud based delivery Cloud networking 44

45 Unit summary Having completed this unit, you should be able to: Understand cloud history and cloud computing Describe the anatomy of Cloud Explain the benefits of Cloud Define cloud transformation roadmap Identify cloud delivery models and explain their advantages Define cloud computing architecture 45

46 Thank you 46