How to create a cloud service?

Transcription

1 11/09/2010 How to create a cloud service? Michael Behrendt (michaelbehrendt@de.ibm.com) 2009 IBM Corporation

2 Outline 1. Introductory example 2. Scope of creating a new cloud service & addressed segments 3. Anatomy of a cloud service steps towards implementing a cloud service 2

3 An Application Example Julie s Correct Answer Service Meet Julie She has all the right answers Julie friends convince her to create a dynamic website where people can ask Julie questions online Julie decides that she can charge $5 US for each correct Answer and charge people s credit cards. Julie likes to write code and quickly creates a prototype Of the application on her Laptop. The application is based On WebSphere/DB2 of course Dilemma - Where can Julie find a place to deploy her application? - Can she find someone who knows how to handle billing? - Can she add the right type of services around this to - run it as a real business? - What is (small chance) Julie s Service is not popular is she out a lot of money.. Perhaps an Infrastructure as a Service (aka Compute Cloud) and Some additional value-add services will help Julie Launch her business 3

4 What Does a Compute Cloud (IaaS) provide? Tools/ Topology Automation Secure API Application Users Tivolli Live Managed Backup Web Access IHS WA S TAM DB2 Billing Service Obtain an account Create/Delete Storage Disks Julie s Operation Staff View Catalog of Images Provision/Deprovision a VM Catalog, Location, Size Mount Disk to VM Access VM via SSH Install Software Save Private Images 4 Create Firewall Rules Create a VLAN Receive a Bill Usage based Subscribe to Premium Support

5 Example of Optional Managed Services (Above Hypervisor) Feature list 1. Remote infrastructure support and connectivity 2. IBM Services Connection portal and basic operational reporting 3. Incident, problem, change management 4. Server monitoring and selected event management 5. Customer virtual private network endpoint gateway and management 6. Call center 7. IP ping monitoring and logfile monitoring 8. Storage monitoring 9. Database, middleware and groupware monitoring 10. Network device monitoring 11. Server patch management 12. Basic performance and capacity reporting 15. Network device management 16. Security scans 18. Backup and restore management 19. Advanced server management and detailed reporting 20. Advanced performance and capacity management 22. Batch management 23. Database, middleware and groupware management 5

6 Outline 1. Introductory example 2. Scope of creating a new cloud service & addressed segments 3. Anatomy of a cloud service steps towards implementing a cloud service 6

7 Cloud service creation Consumer Can be on any aas-layer Provider Developer Cloud Services Common Cloud Platform BSS Business Support Services Consumer End user Integration Tools Consumer Business Manager Consumer In-house IT Par tne r Ca pa bili tie s BPaaS New Cloud Service SaaS Exploits runtime functions PaaS IaaS Service Consumer Portal API Offering Mgmt Order Mgmt Exploits General accounting (OSS & BSS) functions Contract & Agreement Mgmt Customer Mgmt Entitlement Mgmt Invoicing Billing Opportunity to Order OSS Operational Support Services Service Templates Service Request Provisioning Monitoring & Event Metering, Analytics & Reporting Service Delivery Catalog Service Automation Change & Configuration Incident & Problem IT Asset & License Platform & Virtualization Pricing & Rating Subscriber Mgmt Peering & Settlement Service Offering Catalog Image Lifecycle IT Service Level Capacity & Performance Service Development Portal Developer Service Development Tools Service Development Tools Service Runtime Development Tools Service Business Manager Service Provider Portal Service Transition Manager Service Operations Manager Image Creation Tools Consumer Administrator (Virtualized) Infrastructure Security & Resiliency Service Security Manager Governance 7

8 Developing cloud services four major segments: Overview Existing management tooling, processes and operations staff? Yes IT organizations within enterprises Outsourcers Although Although having having different different motivations, motivations, legacy legacy & & requirements, requirements, all all identified identified segments segments there there is is a a common common approach approach developing developing IT IT capabilities capabilities as as cloud cloud services! services! Want to own IT infrastructure & have runtime & mgmt software installed onpremise? No ISVs No Communication Service Providers & new Cloud Service Providers Yes Different Different scenarios scenarios for for offering offering cloud services require cloud services require different different delivery delivery models models for for management management software software ( buildit-yourself vs. IBM-hosted) ( buildit-yourself vs. IBM-hosted) different different levels levels of of integration integration with existing management with existing management tools tools 8

9 Outline 1. Introductory example 2. Scope of creating a new cloud service & addressed segments 3. Anatomy of a cloud service steps towards implementing a cloud service 9

10 Anatomy of a Cloud service Highlevel overview The internal structure of a cloud service is the sum of all runtime and management functions used to deliver, run and manage instances of the respective cloud service. e.g. VMs, storage volumes, WAS instances, web conferencing sessions, etc. Developing a cloud service means developing using & integrating runtime & management functions in a way that IT capabilities can be delivered as-a-service. Consumer A Consumer B Cloud Cloud Cloud service service service instances instances instances Cloud Cloud Cloud service service service instances instances instances Request, modify & use cloud service instances (*-aas) e.g. VM-aaS, Storage-aaS, WAS-aaS, WebConf-aaS, etc. functions (operational & business) E.g. automated delivery & self-service mgmt, entitlement, rating, provisioning, monitoring, metering, patch management, high availability, backup & restore, incident & problem management, etc. Consumer C Cloud Cloud Cloud service service service instances instances instances Runtime functions E.g. compute power, storage capacity, network isolation zones, load balancers, web & application servers, database management systems, analytics engines, business process & portal engines, etc. operates Provider Operations staff 10

11 Cloud service instances and unit of delivery & rating Cloud services deliver dedicated IT capability (infrastructure, platform, software or business process) to cloud service consumers e.g. Infrastructure-aaS: VMs, storage volumes, IP addresses Platform-aaS: WAS clusters, DB2 installations, Oracle databases SaaS: SAP installations, healthcare apps (e.g. medical record mgmt), homegrown php/jee apps, etc. Virtualization on different levels can be used to increase the amount of shared infrastructure, middleware & apps The dedicated IT capability a cloud service consumer gets delivered and which can be used & managed in a selfservice fashion is called cloud service instance. The class of a cloud service instance is the unit of delivery & rating Examples: Compute-aaS (e.g. Smart Business Development and Test on the IBM Cloud) WebConference-aaS (e.g. LotusLive) WAS-aaS (e.g. in a private enterprise cloud) Consumer A Consumer B Consumer C Consumer A Consumer B Consumer C Consumer A Consumer B Uses VM via ssh/vnc, etc. Dedicated per tenant OS VM OS VM OS VM http-based screen-sharing Dedicated per tenant webconf1 webconf2 webconf3 http-based login to admin console WAS WAS cluster WAS WAS cluster WAS WAS Shared technology stack Hypervisor pool (KVM) HW infrastructure (idataplex, Juniper switches, SoNAS) Cloud service instance Shared technology stack Multi-tenancy capable WebConf App Middleware OS (Linux) HW (X86 non-virtualized hardware) Dedicated per tenant Shared technology stack AIX LPAR AIX LPAR AIX LPAR Hypervisor pool (phyp) AIX LPAR HW Infrastructure (System p 770, DS8000, Cisco Switches & FWs) 11

12 Cloud service instance Details The cloud service instance represents the dedicated unit which gets delivered for selfservice use & management by the cloud service consumer A cloud service instance has state Offered cloud services are available via at Service Offering Catalog Consumer: Examples: Change CPU capacity of VM Add more nodes to WAS cluster Change max # of seats for LotusLive web conf Self-service uses Examples: Control OS via ssh connection (ComputeaaS) Share screen via web conference (WebConfaaS) View/Edit customer data (CRM-aaS) Store files on a storage volume (StorageaaS) Cloud Service Instance Shared technology stack (across multiple cloud service instances) delivers Provider The cloud service instance represents the part of the IT stack which is dedicatedly assigned and isolated per tenant. Depends on the level of virtualization being used (hypervisor-, OS-, middleware-, application-) Hypervisor-level virtualization is typically used for delivering existing applications as a service 12

13 Different virtualization technologies can be used to deliver various layers of aas IaaS PaaS SaaS Different virtualization technologies are available for realizing cloud services Decreasing level of isolation Increasing level of sharing / resource efficiency Application-level virtualization (e.g. LotusLive) Platform-level virtualization OS-level virtualization (WPARs, Parallels Virtuozzo) Hypervisor-level virtualization (e.g. image-based approach around VMware, KVM, Xen, phyp, zvm,etc.) (X) X X X X X X X X E.g. SaaS can be realized by using various levels of virtualization, from Depending on the requirements of the respective cloud service regarding isolation & resource efficiency a virtualization method can be chosen Additional requirements like need for changing the code implementation of the respective cloud service also have to be taken into account, e.g. for offering existing Apps as SaaS without changing implementation requires use of OS- or hypervisor-level virtualization 13

14 Sourcing Options Each runtime & management capability needed in support of running, deliverying & managing a cloud service can be consumed in three primary ways: 1. Build-it-yourself : The hardware or software realizing this capability is purchased in the traditional fashion as a normal hardware product or licensed software product and installed within the data center premise owned by the cloud service provider. 2. Externally hosted : This refers to hardware or software that is delivered as an externally hosted service (I/P/S/BPaaS). The organization wanting to implement and offer a new cloud service and requiring the respective functionality does not have to install andy any hard- or software on-premise. 3. A mix of model 1) and 2) where some functionality is installed on-premise and other functionality is consumed as an externally hosted service. It is very important to note that no matter which of the three options above is chosen, the same development process applies for exploiting the respective externally sitting service or on-premise hardware or software installation 14

15 Example for supply chain of services path e.g. create VM, monitor service to ensure health, patch cloud service instances, etc. Service Provided: functionality of various kinds (OSS & BSS) CCMP UI New Cloud Service CCMP manages cloud services for delivery of cloud service instances & managing the cloud service (view CCMP as a cloud service for mgmt, only available internally) Unit of Delivery & Mgmt / Service Instance (example): Fraud detection app Requires cloud services both for management & runtime aspects Runtime / Use path e.g. log into a VM via ssh, log into a web conference via browser/http, store files on a storage volume, etc. Service Provided: OS runtime environment (compute), storage, web conferencing, Fraud detection, etc. SaaS Tivoli Live Unit of Delivery & Mgmt / Service Instance: SRM / ITM / BSS Use of compute cloud as a source for VMs to run the actual middleware/application on Use of PaaS instances as a runtime platform to run the actual application on PaaS Unit of Delivery & Mgmt / Service Instance: Platform Runtime environment OSS Compute Cloud Unit of Delivery & Mgmt / Service Instance: VM IaaS Storage Cloud Unit of Delivery & Mgmt / Service Instance: storage volume 15

16 Developing a new cloud service: Role of the Common Cloud Platform Reference Architecture The CCMP reference architecture describes all management components commonly needed in support of offering a cloud service While the RA provides recommendations on which product to use for developing the architecture, the actual product selection depends on the requirements of the respective project For offering a new cloud service it is required to build an implementation of the CCMP reference architecture The products selected to implement each component of the CCMP RA is driven by the respective requirements of the cloud service development (see previous slide) 16

17 Outline 1. Introductory example 2. Scope of creating a new cloud service & addressed segments 3. Anatomy of a cloud service steps towards implementing a cloud service 17

18 12 steps towards creating a Cloud service, focusing on management aspects Preparation step Runtime-specific Operational Business 1. Specify cloud service description 2. Implement runtime functionality of the cloud service 3. Define Unit of delivery & rating 4. Implement self-service delivery & management functionality 5. Implement monitoring metrics & event correlation rules 6. Implement incident, problem and asset mgmt processes 7. Implement resiliency SLA 8. Implement backup approach 9. Implement security functions 10. Implement cloud service specific billing metrics 11. Implement rates for charging cloud service consumption 12. Register cloud service to service catalog For each step: Decide on sourcing options for implementation to be exploited (buildyourself vs. hosted offering). Use product recommendations in CCMP RA Component Model as guiding documentation 18

19 Step 1: Specify cloud service description: Details Think in terms of an externally facing spec describing the characteristics of the offered cloud service Does not yet make an decisions on how the cloud service gets implemented, but nails down important attributes of the cloud service which drive how following steps are shaped It s important to clearly define the runtime functionality of a cloud service in the very beginning since this decision has implications on all following steps. There are three categories of information which need to be specified within the cloud service description 1. Function Consumer-side end-user facing functionality (e.g. CRM, run applications within a VM, deploy JEE app on an app server Consumer-side self-service management functionality (e.g. create/modify/delete VM, add node to WAS cluster, etc.) 2. Price Pricing structure, $ per xyz, discount rates, etc. 3. SLAs Availability, Support, Performance, etc. Standards compliance (SOX, HIPAA, etc.) scope (see following slide) Definition of SLAs applies to both the runtime capabilities delivered (e.g. perf. of a VM) but also to the management capabilities around it (delivery, monitoring, patching, etc.) Deliverable: Documentation of cloud service description (function, price & SLAs) 19

20 scope Scope of management determines which part of the overall technology stack is managed by the provider and how much is left for management by the consumer refers to the executing of all relevant management disciplines (incident & problem mgmt, monitoring, patching, availability mgmt, etc.) The higher the management scope covered by the provider, the more management costs are generated The more management the provider covers, the more management costs (mostly labor) are going to be generated on the provide side Provider-operated management tools must be set up for different levels of the technology stack, as defined by the management scope For example, for a VM-aaS offering monitoring only has to be setup for the hypervisor and the HW infrastructure (VM unmanaged), whereas for a PaaS offering monitoring is also needed for the middleware infrastructure Application Middleware OS HW infrastructure up to the consumer Managed by the provider up to the consumer Managed by the provider Typical PaaS offering Typical VMaaS offering 20