Cloud Computing Reference Architecture 2.

0: Overview

CC RA team / presented by Mike Buzzetti

© 2011 IBM Corporation

IBM Cloud Computing Reference Architecture

Agenda

Executive Summary Introduction & Overview –Historical evolution of the Reference Architecture –Structure of the RA 2.0 –Target audience –How to apply the RA for cloud implementations Cloud Computing Reference Architecture Details
2 © 2011 IBM Corporation

IBM Cloud Computing Reference Architecture

IBM Cloud Computing Reference Architecture
The IBM CC RA represents the aggregate experience across hundreds of cloud client engagements and the implementation of IBM-hosted clouds – Based on knowledge of IBM’s services, software & system experiences, including IBM Research The IBM Cloud Computing Reference Architecture (CC RA) is reflected in the design of – – – – IBM-hosted cloud services Clouds IBM implements for clients IBM cloud appliances IBM cloud service management products
Cloud Service Consumer
Cloud Services

Cloud Service Provider
Common Cloud Management Platform (CCMP)

Cloud Service Creator

Existing & 3rd party services, Partner Ecosystems Cloud Service Integration Tools

Business-Processas-a-Service

Sof tware-as-a-Service Operational Support Services (OSS) Platf orm-as-a-Service Business Support Services (BSS) Service Creation Tools

Consumer In-house IT Inf rastructure-as-a-Service

The CC RA focuses on cloud specifics such as radical cost reduction while achieving high degrees of security, reliability, scalability and control The CC RA consists of 21 detailed documents representing best-of-industry knowledge and insight on how to architect, design and implement clouds
3

Inf rastructure

Security, Resiliency, Performance & Consumability Governance

© 2011 IBM Corporation

Platform as a Service (PaaS). Software as a Service (SaaS) and Business Process as a Service (BPaaS) Enables the flexible scaling and resiliency required for successful cloud economics and ROI Facilitates seamless integration into existing customers' environments Is based on our industry leading expertise with SOA for building services and serviceoriented architectures 4 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture The IBM Cloud Computing Reference Architecture ensures consistency & quality across IBM development and delivery projects The IBM Cloud Computing Reference Architecture … Is based on open standards Delivers enterprise-class security to meet local. top-to-bottom management of cloud infrastructure and cloud services Supports the full spectrum of cloud service models. regional and national compliance for privacy and governance Combines powerful automation and services management (low touch) with rich business management functions for fully integrated. including Infrastructure as a Service (IaaS).

compute. virtualization) – Software components required to run management – Operational processes – Governance policies tailored for the environment or enterprise. systems and services organizations >50 of IBM’s top cloud computing experts represent the core team A process of continuous improvement helps ensure that the reference architecture is both responsive to changing client and security requirements and incorporates technology developments via IBM products and evolving design specifications. The CC RA provides specifications for – the physical components of a cloud implementation (network.IBM Cloud Computing Reference Architecture IBM Cloud Computing Reference Architecture: Development Process Development led by the IBM Cloud Computing Architecture Board Comprising technology leaders from IBM Research and IBM’s software. 5 © 2011 IBM Corporation . Derived from extensive client interaction combined with IBM’s extensive capabilities and experience in building enterprise-class IT systems. storage.

IBM Cloud Computing Reference Architecture The IBM Cloud Computing Reference Architecture covers are broad range of important cloud-specific topics 6 © 2011 IBM Corporation .

IBM Cloud Computing Reference Architecture Structure of the IBM Cloud Computing Reference Architecture There are two deliverables for each work product of the RA – Document: Detailed description of the work product. for simplified consumption and quick start IBM Cloud Computing Reference Architecture Captures cloudspecific architectural decisions made on any other work product Use Cases Non-functional Requirements Functional (=use cases) and non-functional requirements against the other RA work products Cross-domain work products Defines all cloudspecific standards Architecture Overview Defines architectural building blocks Product-agnostic “Cloudified” management processes for operating cloud services with cloudscale-efficiency Architectural Decisions Architectural Decisions The RA is defined according the Unified Method Framework (UMF) Simplifies field adoption since all IBM field architects attend UMF training by default Service Flows Standards Cross-cutting work product encompassing all security aspects relevant in the context of the CC RA. Rating and Accounting BSS Decomposition Consumability © 2011 IBM Corporation . Security Component Model Refines architecture overview to the next level of detail Operational Model Deployment-level view of the reference architecture Consistent & prescriptive architecture across all technical domains Domain-specific work products Each work product includes one or more “applied patterns” – An applied pattern illustrates how the respective work product could be used / was used in a specific 7 implementation Performance & Scalability Cloud Service Creation Multi-tenancy “Production cloud” Virtualization Management Hybrid Cloud Resiliency Metering. important for indepth work – Presentation: Summary of the document.

including prescriptive guidance with respect to implementation Detailed definition of BSS domains and how they should be implemented from a product perspective How to optimize the end to end experiences related to cloud services © 2011 IBM Corporation . storage and network 8 Architecture & implementation considerations for implementing a hybrid cloud Resiliency considerations for implementing a cloud Details on metering. Rating and Accounting BSS Decomposition Consumability Example for how to implement a cloud management system for offering production-level cloud services Definition for how to use virtualization management across server. Architecture Overview Service Flows Standards Security Component Model Operational Model Considerations for implementing multitenancy in a cloud environment Domain-specific work products Performance & Scalability Cloud Service Creation Multi-tenancy “Production cloud” Virtualization Management Hybrid Cloud Resiliency Metering. rating and accounting.IBM Cloud Computing Reference Architecture IBM Cloud Computing Reference Architecture: Domain work product details IBM Cloud Computing Reference Architecture How to implement a cloud to achieve optimal performance & scalability Use Cases Non-functional Requirements Cross-domain work products Architectural Architectural Decisions Decisions Guide for creating cloud services and how to exploit management functions.

• Continuously ongoing harvesting process due to additional learnings during each phase 9 • Continuous improvement of CC RA content based on feedback from CC RA exploiters & stakeholder • Be clear about which parts of the RA are already addressed in today’s IBM cloud offerings and which aspects still have to be addressed • Today’s cloud implementations are not necessarily optimal implementations (due to time & resource constraints)  Need forward-looking guidance on ideal target implementation •Examples are: • generalization of CCMP services • layered cloud services • NFRs. due to constrained time lines).IBM Cloud Computing Reference Architecture The IBM Cloud Computing Reference Architecture – Aggregating past & present experience and future requirements CC RA = Harvesting (“Learning from cloud deployments in the past?”) + Refinement (“Improve the CC RA content presently available”) + Forward looking (“Which future topics are relevant for cloud computing”) • Harvest learnings & material from cloud implementations while factoring out short cuts taken by implementation team (e. e. resiliency • Hybrid clouds © 2011 IBM Corporation .g.g. security.

IBM Cloud Computing Reference Architecture How to implement a cloud using the IBM Cloud Computing Reference Architecture 1  There is a well-defined process for using the RA to implement a cloud service – A cloud is constituted by a CCMP implementation and an arbitrary number of cloud services delivered and managed by it  A dedicated presentation and document is available describing the process for using the RA to develop the management aspects for a cloud service  RA work products also serve as authoritative reference on specific technical topics for education purposes Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview 3 Define cloud service and CCMPimplementation details 3b Service Flows Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process + Use Cases Architecture Overview Component Model Operational Model Architectural Decisions 3a Security Performance & Scalability Virtualization Management Resiliency Metering. Rating and Accounting Standards + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a cloud service & CCMP implementation + Consumability BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” 10 © 2011 IBM Corporation .

operating and managing this cloud service Hybrid Cloud Multi-tenancy “Production cloud” Capture cloud service / CCMP-implementation specific architectural decisions. based on RAlevel AOD Create cloud service / CCMP implementationspecific component model. Reference RAlevel operational model Cloud Service Creation + Use Cases Architecture Overview Component Model Operational Model Architectural Decisions + Non-functional Requirements Document cloud service-specific use cases. Create cloud service / CCMP implementationspecific architecture overview. Work products serving as the basis for a cloudspecific work product: All “cross-domain” work products plus “Cloud Service Creation” 11 Document cloud service-specific decisions made for each step of the cloud service creation process. Reference RAlevel component model Define cloud-service / CCMP implementation-specific standards being used.IBM Cloud Computing Reference Architecture Using the CC RA: Which work products have to be created on a per cloud service basis?  The RA contains two types of work products 1. Refer to RA-level service flows. Leverage experience documented as part of ADs being part of the RA Work product to be created on a per cloud service basis © 2011 IBM Corporation . Use the RA-level work product as a reference for step definitions and product recommendations Create cloud service / CCMP implementationspecific service flows. Reference RA-level standard definitions Service Flows Create cloud service / CCMP implementationspecific operational model. Rating and Accounting BSS De-composition Assess end to end experience creating. Reference RA-level use cases serving as a basis Standards Security Performance & Scalability Virtualization Management + Consumability Document cloud service-specific NFRs. Reference RA-level NFRs serving as a basis Resiliency Metering. Work products only serving as a reference documentation for specific aspects of implementing a new cloud: All “domainspecific” work products except “Cloud service creation” 2.

IBM Cloud Computing Reference Architecture Cloud Computing Reference Architecture Details 12 © 2011 IBM Corporation .

IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions d ocumented in the RA and make implementationspecific ones throughout the entire process Define requirements and use im plementation guidance for cloud service and CCMP im plementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture o verview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security s n o i s i c e D l a r u t c e t i h c r A 3a Performance & Scalability Virtualization Management Resiliency Metering. Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” s d r a d n a t S + Non-functional Requirements Leverage guidance on specific technical areas as in put for developing a CCMP implementation + Consumability Cloud Service Creation 13 © 2011 IBM Corporation .

Resiliency. Partner Ecosystems Cloud Service Integration Tools Sof tware-as-a-Service Cloud “New Service” Operational Support Services (OSS) Business Support Services (BSS) Service Creation Tools Platf orm-as-a-Service Consumer In-house IT Exploit runtime functions Inf rastructure-as-a-Service Inf rastructure Security. Performance & Consumability Governance © 2011 IBM Corporation . Focus is on the management aspects as they apply generically across all types of cloud services – Provide detailed description of basic terminology relevant for creating cloud services – Provide prescriptive product recommendations relevant for each cloud service creation step and tooling around that – Provide illustrative examples (“applied patterns”) for how a new cloud service can be created 14 Cloud Service Consumer Cloud Services Cloud Service Provider Can be on any Can be on any Common Cloud aaS-layer aaS-layer Management Platform (CCMP) Business-Processas-a-Service Exploit Management (OSS & BSS) functions Cloud Service Creator Existing & 3rd party services.IBM Cloud Computing Reference Architecture “Cloud Service Creation” – Scope and Overview Objective: Describe all aspects around developing a new cloud service – Scope is end-to-end process for developing a new cloud service.

IBM-hosted) . software & process legacy and requirements. processes and operations staff? Yes Outsourcers IT organizations within enterprises Although having different motivations.different delivery models for management software (“buildit-yourself” vs.IBM Cloud Computing Reference Architecture Developing cloud services – four major segments: Overview Existing management tooling. there is a common approach for creating cloud services across all segments Yes Want to own IT infrastructure & have runtime & mgmt software installed onpremise? No ISVs Communication Service Providers & new Cloud Service Providers Different scenarios for offering cloud services require .different levels of integration with existing management tools No 15 © 2011 IBM Corporation .

Developing a cloud service means developing using & integrating runtime & management functions in a way that IT capabilities can be delivered as-a-service. modify & use cloud service instances Management functions (operational & business) Cloud Service (*-aaS) e.IBM Cloud Computing Reference Architecture Anatomy of a Cloud service – Highlevel overview The internal structure of a cloud service is the integration of all runtime and management functions used to deliver. rating. etc.g. provisioning. patch management.g. e. etc. VM-aaS. high availability. metering.g. Cloud Cloud Cloud service service service instances instances instances delivers Cloud Service Consumer B delivers Cloud Cloud Cloud service service service instances instances instances E. Cloud Service Consumer C Example – Julieanswers. entitlement. hypervisors. backup & restore. WAS instances. VMs. monitoring. run and manage instances of the respective cloud service. operates Runtime functions E.com cloud service: . web & application servers.TivoliLive monitoring the health of the julieanswers app and the underlying IHS/WAS/DB2 installation . Storage-aaS. storage capacity.Billing tool . load balancers. business process & portal engines. database management systems. etc.Julieanswers ear file . etc. network isolation zones. WAS-aaS. compute power.IHS/WAS/DB2 running the julieanswers ear file . incident & problem management.Virtual machines running IHS/WAS/DB2 . storage volumes. analytics engines. automated delivery & self-service mgmt. defined in the CC Reference Architecture Cloud Cloud Cloud service service service instances instances instances delivers Cloud Service Consumer A Request. web conferencing sessions.BCRS to backup the julieanswers db2 database 16 Cloud Service Provider Operations staff © 2011 IBM Corporation . WebConf-aaS.g.

web conference. delivered WAS cluster must be highly available Examples: Backup all VMs. implement custom app (e. problem & asset mgmt process is specific to cloud service  customization needed Examples: HA for management system. backup DB of LotusLive application 9. queue. entitlements need to be configured. Implement authentication. price . Implement security functions 10. data protection.05/fraudAnalysis 17 © 2011 IBM Corporation . Implement cloud service specific billing metrics 11. auditing. SLA of cloud service. hypervisor swap file size. # of DB transactions. $0. 3-tier business app. $0. LotusLive) Examples: VM. etc.g. virtual IP address. Implement monitoring metrics & event correlation rules 6. Implement incident. Register cloud service to service catalog 1 11 1 1 11 * 1 * 1 11 * 11 1 1 1 * 1 * 1 $$ $ A cloud service must be registered to the service catalog to be externally accessible. Define unit of delivery & rating 1 * 1 1 4. Implement rates for charging cloud service consumption 12.IBM Cloud Computing Reference Architecture 12 steps towards creating a cloud service 2. Implement backup approach ! Select existing agent / implement new agent for monitoring JVM heapsize. $0. # of processes.02/webconference. Incident. incl. etc. GB/month. Examples: $0. management scope Examples: Select off-the-shelf hypervisor (VMaaS).11/VMhour. Examples: “Create VM. problem and asset mgmt processes 7.19/MBsTransferred. change max # of seats for LotusLive web conf 5. add more nodes to WAS cluster. distributed app. file system. Implement self-service delivery & management functionality * Describe function. Implement resiliency SLA 8. RDBMS. # of users/webconf/hour. governance & audit Examples: CPU/hour. Implement runtime functionality App MW OS Server Storage Network 11 11 * 11 3. etc.

Impact Tivoli Service Request Manager & TAMIT Tivoli System Automation Tivoli Storage Mgr Tivoli Security / ISS portfolio TUAM TUAM TSAM / TSRM Service Provider Edition 3.IBM Cloud Computing Reference Architecture Overview: Recommended management products. Define Unit of delivery & rating 4. Implement incident. VMware. problem and asset mgmt processes 7. Filenet. Cognos. Implement rates for charging cloud service consumption 12. DB2. Windows. WAS. Linux. Specify cloud service description 2. … n/a (cross-cutting decision) TSAM IBM Tivoli Monitoring. Implement cloud service specific billing metrics 11. Implement monitoring metrics & event correlation rules 6. to be exploited on a per cloud service basis Step 1. Implement backup approach 9. Implement resiliency SLA 8. Implement runtime functionality of the cloud service Products & technologies to build your own cloud service n/a (cross-cutting) KVM. Register cloud service to service catalog 18 © 2011 IBM Corporation . Implement security functions 10. Implement self-service delivery & management functionality 5. Omnibus.

Impact Monitoring agent (ITM). DB2. SQL file. … Rational Dev tools (for app artifacts). Filenet. Define Unit of delivery & rating n/a (cross-cutting decision) n/a n/a 4. Implement cloud service specific billing metrics TUAM No dedicated tooling available Metering collectors Job files Rates persisted in TUAM database 11. jobplans. Implement backup approach Tivoli Storage Mgr TSM Backup agent Backup policy Various various 9. escalations (TSRM) 7. etc. JEE ear file. Linux. Specify cloud service description n/a (cross-cutting) n/a n/a 2. Implement self-service delivery & management functionality TSAM & TPM TSAM SD app TPM ADPE Universal Agent Builder (ITM) Omnibus-internal tooling TSAM Service definition & TPM provisioning workflows 5. VMware. WAS. Implement security functions Tivoli Security & ISS Portfolio 10. 3. no image creation tools available today VM golden master image. Implement incident. Implement resiliency SLA Tivoli System Automation Text editor (no dedicated tooling) HA policy 8. Omnibus. Register cloud service to service catalog TSAM / TSRM Service Provider Edition TSAM/TSRM internal apps Registration persisted in TSAM/TSRM internal database 19 © 2011 IBM Corporation . Implement rates for charging cloud service consumption TUAM UI and CSV file import 12. event correlation rule (Omnibus) 6.IBM Cloud Computing Reference Architecture Overview: Recommended management products. Windows. Cognos. Implement runtime functionality of the cloud service KVM. Implement monitoring metrics & event correlation rules IBM Tivoli Monitoring. problem and asset mgmt processes Tivoli Service Request Manager & TAMIT TSRM-internal apps Incident & problem management workflows. development tools and artifacts to be created on a per cloud service basis Step Products & technologies Building a cloud service hosted within the provider’s premise Development/Config Tool Cloud service specific configuration / artifact 1.

rule Omnibus-int. … Job files. etc. WAS. Rational Dev tools (for app artifacts).*Cloud Computing Reference Architecture (CC RA) – Product & tooling mapping (on-prem products) Cloud Service Provider Cloud Services Common Cloud Management Platform Golden master VM image (runtime) [see runtime] IBM Cloud Computing Reference Architecture Service Definition TSAM SD app Service Manager Business Manager Registration persisted in DB TSAM/TSRMinternal apps TSAM / Tivoli Service Request Manager SP Existing & 3rd party services. JEE ear file. job plans. Windows. SQL file. Linux. no image creation tools available today KVM. Resiliency. Partner Ecosystems Tivoli Service Automation Manager Workflows. DB2. Filenet. tooling Omnibus & Impact HA policy Editor Tivoli System Automation Platform & Virtualization Management Editor Tivoli Usage & Accounting Manager Service Provider Portal & API TAMIT DB entry TAMIT apps TAMIT Consumer In-house IT IaaS Deployment Architect Transition Manager Operations Security & Manager TSM backup agent Risk Manager Customer Care Legend <cloud servicespecific artifact created> <devToolForExploit ing mgmt/runtime component> <runtime/mgmt platform component> Infrastructure Tivoli Storage Manager Security. VMware. Cognos. escalations TSRM-internal apps Tivoli Service Request Manager TPM for OSS – Operational SupportImages Services BSS – Business Support Services Customer Account Management Service Offering Catalog Service Offering Management Service Development Portal & API BPaaS Service Delivery Catalog Cloud Service Integration golden master Tools VM image. metering collectors Editor Tivoli Usage & Accounting Manager Service Automation Management Service Consumer Portal & API TPM workflows APDE SaaS Tivoli Provisioning Manager ITM Agents ITM Agent Builder Provisioning Incident & Problem Managemen t IT Service Level Managemen t Service Creation Tools PaaS IBM Tivoli Monitoring CSV file Event cor. Performance & Consumability Governance © 2011 IBM Corporation 20 .

IBM Cloud Computing Reference Architecture Cloud service creation – Applied patterns overview  Walkthrough all 12 steps per applied pattern while describing implementation-specific decisions per step (incl. ISV • Example cloud service: “Desktop Cloud” 1. It is acknowledged that many real-world implementations won’t map exactly to the applied patterns described here – many will be in a “grey zone” in between. “Enterprise”: 1. the applied patterns serve as good guidelines and blueprints for these custom implementations There will be more applied patterns available in future versions of the RA    21 © 2011 IBM Corporation . However. product selections) 1. WAS The applied patterns should serve as a guideline for anyone who wants to deliver IT capabilities as cloud services.

Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” s d r a d n a t S + Non-functional Requirements Leverage guidance on specific technical areas as in put for developing a CCMP implementation + Consumability Use Cases & Roles 22 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions d ocumented in the RA and make implementationspecific ones throughout the entire process Define requirements and use im plementation guidance for cloud service and CCMP im plementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture o verview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security s n o i s i c e D l a r u t c e t i h c r A 3a Performance & Scalability Virtualization Management Resiliency Metering.

Workload Administrator. © 2011 IBM Corporation . Security Administrator Security & Risk Manager Operations Manager Operator. OS Admin. Virtualization Admin...Cloud Computing User Roles V2 – IBM Cloud Computing Reference Architecture Applied as Actors of CC RA use cases Service Component Developer Offering Manager Service Composer Business Manager Customer Account Manager. IT Administrator Consumer End User Facilities Manager Customer Support & Care 23 IT Administrator specialties: Storage Admin. Data Administrator.. Network Admin. Cloud Education Specialist Cloud Service Creator may include may include Consumer Business Manager Service Integrator Service Manager Cloud Service Provider may act as Cloud Service Consumer Consumer Administrator Tenant Administrator. Business Office Deployment Architect Transition Manager Cloud Service Consultant. Green IT Analyst.

Business Manager. Service Setup  Provision service Service Runtime  Managing compliance with service’s Service Level Agreements (SLA)  Monitor third party supplier SLA  Detect service faults  Determine service impact (from infrastructure faults / degradation)  Prioritise problems based on network impact  Manage long and short term performance targets  Ensure alignment of business and operational support systems  Expert knowledge of the existing cloud infrastructure and good judgment of the impact of a new or changed solution on it  Proficient understanding of the particular service offering and its service instances  Expert automation knowledge  Proficient understanding of capacity/performance issues within and across systems Operations Manager. Deployment Architect. fact based discussions on service quality with internal and external suppliers Main Goal Main Responsibility The focus of a Service Manager is to enable the smoothest service flow possible between all systems. Customer Account Manager. They ensure that the running service is well aligned with business and operational objectives and targets. Green IT Analyst. Cloud Service Creator Main Tasks of their day-to-day job Skills Working with which other roles ? 24 © 2011 IBM Corporation .Example: Service Manager    Services meet their quality objectives Get up-to-date information on service adoption in seconds not days Have meaningful. from business support system to operational support system services. Operator. Network Administrator.IBM Cloud Computing Reference Architecture Detailed Role Description .

security. delete service instances 25 © 2011 IBM Corporation . Create. Self-guided information & education Via F2F or Web Sales channel Enable customers for managed services Development & Test on the Cloud: Developing & testing applications. Monitor infrastructure(s).CC RA V2. Creating & Managing Business Aspects • 38 use cases. modify. changes. delete users. update. delete user groups Request. grouped into 10 packages. view. Creating & Managing Service Offerings. along the cloud service life cycle Consultative Analysis. using development tool instances Desktop on the Cloud: Making use of ‘Anytime. Anywhere’ access to applications. Integrate Cloud & (non-) Cloud env.s Request & View usage & billing reports. information and resources Collaboration in the Cloud: Using social networking services and online collaboration tools Install & configure platform. Manage capacity. Administer secure access Create. events. modify.0 Use Cases IBM Cloud Computing Reference Architecture Creating & Managing Service Offerings Defining the Scope.

Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” s d r a d n a t S + Non-functional Requirements Leverage guidance on specific technical areas as in put for developing a CCMP implementation + Consumability Non-functional requirements 26 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions d ocumented in the RA and make implementationspecific ones throughout the entire process Define requirements and use im plementation guidance for cloud service and CCMP im plementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture o verview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security s n o i s i c e D l a r u t c e t i h c r A 3a Performance & Scalability Virtualization Management Resiliency Metering.

27 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture Non-functional requirements TWP: Scope & Purpose  Consolidate typical Cloud Computing Management Platform Non-Functional Requirements to illustrate the minimal set of non-functional requirements for building a Cloud Management Platform  Reference architecture NFRs can help practitioners collect requirements during any project requirements gathering phase  NFRs are key input to other TWPs including Component Model and Operation Model  NFRs are high level in nature. they should be evaluated along with the lower level CC RA Operational Model to establish the optimum Infrastructure for deploying the proposed solution  Non-Functional requirements of a Cloud management platform are quality requirements or constraints of the platform that must be satisfied. These requirements address major operational and functional areas of the platform in order to ensure the robustness of the system. as such.

IBM Cloud Computing Reference Architecture NFR Context Relationship with other TWP and Domains Architectural Domains and Technical Work Product Inputs* Cloud Delivery Models Metering/ Rating / Accounting Virtualization Management SaaS Performance& Scalability Hybrid Cloud Multi-tenancy Resiliency NF Rs PaaS NFRs IaaS 28 © 2011 IBM Corporation .

IBM Cloud Computing Reference Architecture Non-Functional Requirement TWP document contains the following detailed NFRs… In version 2 of the NFR document we added NFRs from the following areas on top of the version 1:  Applied Pattern NFRs Added .Metering / Accounting: +24 29 © 2011 IBM Corporation .PaaS: +15 .Virtualization management: o Base virtualization: +12 o Network virtualization: +18 .Public Cloud: +20 .Resiliency: +13 .Performance and scalability: +14 .IaaS .Multi-tenancy: +16 .Private Cloud: +17 .IaaS .Hybrid Cloud: +10 NFRs .SaaS – Managed Service Desk: +16  Domain Specific NFRs Added .

IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions d ocumented in the RA and make implementationspecific ones throughout the entire process Define requirements and use im plementation guidance for cloud service and CCMP im plementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture o verview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security s n o i s i c e D l a r u t c e t i h c r A 3a Performance & Scalability Virtualization Management Resiliency Metering. Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” s d r a d n a t S + Non-functional Requirements Leverage guidance on specific technical areas as in put for developing a CCMP implementation + Consumability Consumability 30 © 2011 IBM Corporation .

solutions and services. Consumable solutions: Reduce total cost of ownership Improve time to value Market driver Attributes Reduce support and maintenance costs Consumability framework Key characteristics On-demand self-service Ubiquitous network access Location independent resource pooling Rapid elasticity Flexible pricing models Integration is critical Data Integration / Migration Process Integration UI Mashup Labor simplification drives efficiency Self Service Automation of Management Standardization of Workloads 31 Identify Easy to do business Evaluate Plan Acquire Positive first-use experience Configure Operate Rapidly integrates with existing environment Readily adapts to customer requirements Integrate Deploy Develop Customize Problem Mgmt Simplifies ownership and operation Admin & Maintain Fix & Upgrade © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture What makes a cloud solution consumable? Consumability is a customer-centric term that describes the total customer experience with IBM products.

and market data Understand key workloads for offering Cloud Service Provider Cloud Service Creator Cloud Service Consumer Map key end-to-end tasks Cloud User Roles Identify relevant consumability criteria Identify involved user roles Conduct consumability assessment and gap analysis Describing who is interacting with a cloud service at the different stages of the cloud life cycle Consumability Assessment Using the consumability framework that is modified specifically for cloud solutions. Design Customer Feedback (Validation) Stakeholder Feedback • • 32 Getting ongoing feedback from stakeholders is essential for designing a consumable solution. assess the solution. the next step is to identify key stakeholders whose feedback you need to gather © 2011 IBM Corporation . and work towards closing gaps. Understanding the user roles.IBM Cloud Computing Reference Architecture Designing Consumable Cloud Solutions Gather customer. competitive. identify the consumability goals for a particular solution.

IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions d ocumented in the RA and make implementationspecific ones throughout the entire process Define requirements and use im plementation guidance for cloud service and CCMP im plementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture o verview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security s n o i s i c e D l a r u t c e t i h c r A 3a Performance & Scalability Virtualization Management Resiliency Metering. Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” s d r a d n a t S + Non-functional Requirements Leverage guidance on specific technical areas as in put for developing a CCMP implementation + Consumability Architectural Principles & Overview 33 © 2011 IBM Corporation .

IBM Cloud Computing Reference Architecture Cloud Computing Reference Architecture: Architectural Principles An architectural principle is an overarching guideline or paradigm driving architectural decisions across the entire architecture process on a more granular level. based on an Eliminate-Standardize-Optimize approach 3. and flexible sourcing. infrastructure & infrastructure / platform cloud services across cloud services to reduce CapEx & OpEx and time-to-market 4. and time-to-deliver/time-to-change metrics. Support Lean Service Management (“Lightweight Principle”): Support lean and lightweight service management policies. Identify and Leverage Commonalities (“Economies-of-scale Principle”): Identify and leverage commonality in cloud service design. processes. with a single management platform 34 © 2011 IBM Corporation . Define and Manage Cloud Services generically along their Lifecycle (“Genericity Principle“): Define service templates and manage service instances generically along their lifecycle.  Support I/P/S/BPaaS cloud services in a generic fashion. self-service access. when realizing cloud characteristics such as elasticity. Design for Cloud-Scale Efficiencies (“Efficiency Principle”): Design for cloud-scale efficiencies.  Radical exploitation of high degree of standardization in cloud environments to reduce management costs. and technologies. across I/P/S/BPaaS. 1.  Overarching objective of Driving down costs (¢/ServiceInstanceHour) and time-to-response by orders of magnitude 2.  Maximum sharing of mgmt components.

provider and creator whereas multiple roles can be fulfilled by the same organization/person Offered cloud services. Partner Ecosystems Cloud Service Integration Tools Business-Processas-a-Service Sof tware-as-a-Service Operational Support Services (OSS) Platf orm-as-a-Service Business Support Services (BSS) Service Creation Tools CCMP is one element of the overall cloud computing reference architecture Defines operational and business support services commonly needed for delivering and managing any cloud service (I/P/S/BPaaS) Doesn’t imply a single. Resiliency. CCMP is typically implemented by a wellintegrated set of mgmt products Consumer In-house IT Inf rastructure-as-a-Service Inf rastructure Security. required Management services (CCMP) and underlying infrastructure are defined. Performance & Consumability Governance 35 © 2011 IBM Corporation . Next level of drill-down defined for each architectural element Cloud Service Consumer Cloud Services Cloud Service Provider Common Cloud Management Platform (CCMP) Cloud Service Creator Existing & 3rd party services.IBM Cloud Computing Reference Architecture Cloud Computing Reference Architecture (CC RA) – Overview CC RA architecture overview diagram lays defines basic elements of any cloud service environment Three main roles: Cloud service consumer. monolithic implementation of a CCMP.

with the possible exception of limited user-specific application configuration settings. python. firewalls. network. 2009 IBM MI and IPR definition bridge between Gartner and IDC. . or even individual application capabilities. in IaaS “the consumer does not manage or control the underlying cloud infrastructure […]”. network. Draft NIST Working Definition of Cloud Computing. load balancers). The consumer does not manage or control the underlying cloud infrastructure. network. deployed applications. SaaS or BPaaS. 1. it is not about the virtualization technology being used. servers. or storage.g. Aug 19. NIST1 IaaS The capability provided to the consumer is to rent processing. java. NIST1 PaaS The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created applications using programming languages and tools supported by the provider (e.g. web-based email). For example. or storage […]”. storage. servers. So this essentially about the tasks the operations staff of the provider takes on.Net). which can include operating systems and applications. May 14.. operating systems. and other fundamental computing resources where the consumer is able to deploy and run arbitrary software. BPaaS SaaS The capability provided to the consumer is to use the provider's applications running on a cloud infrastructure and accessible from various client devices through a thin client interface such as a Web browser (e. networks. but the consumer has control over the deployed applications and possibly application hosting environment configurations. storage.. For example. self-service provisioning. operating systems. 2010 © 2011 IBM Corporation . The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems. elastic scaling and usage metering or pricing) via the Internet with access via Web-centric interfaces and exploiting Web-oriented cloud architecture. storage. 36 National Institute of Standards and Technologies. etc.IBM Cloud Computing Reference Architecture Cloud service model definitions Term Term Definition Definition Source Source Business process services are any business process (horizontal or vertical) delivered through the Cloud IBM2 service model (Multi-tenant. it’s possible to use hypervisor-level virtualization to realize PaaS.. servers. The BPaaS provider is responsible for the related business function(s). operating systems.. 2. and possibly select networking components (e. in PaaS “the consumer does not manage or control the underlying cloud infrastructure. The consumer does not manage or control the underlying cloud infrastructure. NIST1 Note: Across all cloud service models the definition is determined by the management scope covered by the provider.g.

Resiliency.risk and compliance management © 2011 IBM Corporation . highlighting some important topics  CCMP defines all management functions commonly needed for the automated delivery & management of any cloud service  Components are grouped in two major categories: Operational Support Services (OSS) and Business Support Services (BSS) – OSS: Responsible for managing the runtime components of cloud services – BSS: Responsible for all business / finance related aspects of cloud services  Economies of scale can be achieved by managing multiple cloud services with the same set of mgmt components (see architectural principles) 37 Cloud Service Consumer Cloud Services Cloud Service Provider Common Cloud Management Platform Creator •Flexible support of delivery models Service Manager Business Manager Usage Metering and Accounting Cloud Service •Interpret and Execute Existing &and Management Plans BuildServices 3 party BPaaS services. build and manage images for cloud services Virtualized Resource Management •Deploy cloud services on virtualized resources •Manage virtual resources Deployment Architect Transition Manager Operations Manager Security & Risk Manager Customer Care Inf rastructure Security. integrity.IBM Cloud Computing Reference Architecture Cloud Computing Reference Architecture Overview Diagram – CCMP drill-down. image. Performance & Consumability Security Governance •Design for Multi-Tenancy •Protect assets through Isolation. •Orchestrate Management Componentry rd Service Automation Management Support OSS – Operational Partner Ecosystems Service Delivery Catalog BSS – Business Support Services Customer Account Management Service Offering Catalog Service Offering Management Cloud Service Integration Tools I A & a P t n m p o l D c i v r e S Service Automation Management I P A & l a t r o P r e m u s n o C e c i v r e S SaaS Contracts & Agreement Management Service Request Management Order Management Service Request Management Change & Configuration Management Incident & Problem Management IT Asset & License Management Image Lifecycle Management IT Service Level Management Capacity & Performance Management Subscription Management Pricing Entitlement Management Provisioning Service Creation Tools PaaS Monitoring & Event Management Metering Rating Billing Consumer In-house IT IaaS Platform & Virtualization Management Clearing & Settlement Accounts Payable Accounts Receivable Image Management Service Provider Portal & API •Design.

Performance & Consumability 38 Governance © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture Cloud Computing Reference Architecture (CC RA) – Overall drill-down Cloud Service Consumer Cloud Services Consumer End user Cloud Service Provider Common Cloud Management Platform OSS – Operational Support Services BPaaS Service Manager Business Manager Cloud Service Creator Service Component Developer Cloud Service Integration Tools Existing & 3rd party services. Partner Ecosystems BSS – Business Support Services Customer Account Management Service Offering Catalog Service Offering Management Pg BM s c a f r e t nt I m I P A Service Delivery Catalog Service Composer I A & a P t n m p o l D c i v r e S Service Automation Management I A & l a t P m u s n o C c i v r e S Service Integrator SaaS Contracts & Agreement Management Service Request Management Order Management Offering Manager m g M e r a w t f o S s c a f r e t n I I P A Service Request Management Change & Configuration Management Incident & Problem Management IT Asset & License Management Image Lifecycle Management Subscription Management Pricing Entitlement Management IT Service Level Management Capacity & Performance Management Metering Rating Billing Consumer Business Manager Service Creation Tools Service Management Development Tools Provisioning I P A Business Processes Applications g M m r o f t a l P s c a f r e t n I Consumer Inhouse IT PaaS Monitoring & Event Management Platform & Virtualization Management Clearing & Settlement Accounts Payable Accounts Receivable Service Runtime Development Tools Software Development Tools t m g n a M c i v r e S I P A IaaS e c u t s a r f n I s c a f r e n I t m g M Middleware Infrastructure Service Provider Portal & API Deployment Architect Transition Manager Operations Manager Security & Risk Manager Customer Care Image Creation Tools Consumer Administrator Inf rastructure Security. Resiliency.

Performance & Consumability 39 Governance © 2011 IBM Corporation . Performance & Consumability drill-down Cloud Service Consumer Cloud Services Existing & 3rd party services. Resiliency. System & Service Assurance Data and Information Protection Access & Identity Lifecycle Management Resiliency Data Resiliency Configuration for Resiliency Resiliency Monitoring / Analysis Resiliency Compliance Assessment Resiliency Policy Management Availability & Continuity Management Consumability Ease of Doing Business Positive First Use Experience Rapidly Integrates Readily Adapts Simplified Operations Governance Data policy enforcement Security Entitlement Security.IBM Cloud Computing Reference Architecture Cloud Computing Reference Architecture (CC RA) – Security. Partner Ecosystems Business-Processas-a-Service Cloud Service Provider Common Cloud Management Platform Cloud Service Creator Cloud Service Integration Tools Software-as-a-Service Platform-as-a-Service Consumer In-house IT Infrastructure-as-a-Service Operational Support Services (OSS) Business Support Services (BSS) Service Creation Tools Infrastructure Security Security Event Management Security Policy Threat & Vulnerability Management Software. Resiliency.

Resiliency.IBM Cloud Computing Reference Architecture Cloud Computing Reference Architecture (CC RA) – Infrastructure drill-down Cloud Service Consumer Cloud Services Existing & 3rd party services. Partner Ecosystems Cloud Service Provider Common Cloud Management Platform Cloud Service Creator Business-Processas-a-Service Software-as-a-Service Cloud Service Integration Tools Operational Support Services (OSS) Platform-as-a-Service Business Support Services (BSS) Infrastructure-as-a-Service Service Creation Tools Inf rastructure Consumer In-house IT Server Processor Storage Drives Network Internal Facilities Location Memory Ephemeral External Power Nodes Persistent Inter-site Security. Performance & Consumability 40 Governance © 2011 IBM Corporation .

service provider consuming 1. plus the consumption of externally provided public cloud services 4.IBM Cloud Computing Reference Architecture Architecture Overview: Applied patterns  Applied Patterns are based on cloud projects where the reference architecture AOD has been used to create cloud implementations. A service provider consumption and value-add architecture overview diagram pattern (i. Applied patterns reflect common scenarios of how a cloud could be implemented: 1. IBM Shared Private Production Cloud 41 © 2011 IBM Corporation .e. IBM Smart Business Development and Test on the IBM Cloud is a sample for a "simple" (public) service provider architecture pattern. The diagram and related descriptions have been used to lead the high-level discussion and to guide decisions on scope for release 1 and following. An architecture overview diagram pattern for a private enterprise where traditional IT is managed in parallel to a private cloud environment. 2. The RA overview diagram has be used to discuss roles and responsibilities for a Desktop cloud project where part of the infrastructure is managed by IBM. a service provider consuming cloud services from another cloud service provider and reselling the same offering -.with different branding and different prices) 5. 3. A service provider "whitelabeling" architecture overview diagram pattern (i. IBM Cloud Service Provider Platform 8.n cloud services from other cloud services. Bio-Informatics Exchange 7.e.. composing them and adding service provider specific value-add functionality on top) 6.

Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” s d r a d n a t S + Non-functional Requirements Leverage guidance on specific technical areas as in put for developing a CCMP implementation + Consumability Component Model 42 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions d ocumented in the RA and make implementationspecific ones throughout the entire process Define requirements and use im plementation guidance for cloud service and CCMP im plementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture o verview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security s n o i s i c e D l a r u t c e t i h c r A 3a Performance & Scalability Virtualization Management Resiliency Metering.

0: Component Model Primary focus on BSS and OSS  BSS and OSS component specifications and toplevel decomposition  Use Case realizations of important use cases (e.g.0 Component Model  Condensed mapping of CC RA 2.IBM Cloud Computing Reference Architecture CC RA 2. Requesting Service Instances)  Extensive UML-based modeling of BSS and OSS component relationships and dependencies  Cross-component view on CC RA 2.0 components with IBM recommended tools 43 © 2011 IBM Corporation .0 domains  Mapping of current IBM cloud implementations to CC RA 2.

Create Rating Scheme . processes and flows involved in realization of use cases  Detailed component diagrams are included to provide information about component interfaces.Create Service Template . .Creating Service Offering incl.IBM Cloud Computing Reference Architecture Use Case Realizations A use-case realization describes how a particular use case is realized within the design model.0 CM describes realization of typical use cases: . relationships and dependencies 44 © 2011 IBM Corporation . in terms of collaborating objects (IRUP).  CC RA 2.Requesting Service Instance  Sequence diagrams help to understand components.

Resiliency.IBM Cloud Computing Reference Architecture IBM recommended products for consuming management functionality as on-premise installations Cloud Service Provider Cloud Services Consumer End user Common Cloud Management Platform OSS – Operational Support Services Service Delivery Catalog TSRM Service Manager Business Manager Service Component Developer Cloud Service Integration Tools Existing & 3rd party services. OMNIbus. ITNM. TBSM TAMIT TSRM SPE TUAM TSRM SPE TUAM TSRM SPE Platform & Virtualization Management Infrastructure Mgmt Interfaces VMControl TPC Service Provider Portal & API Service Runtime Development Tools Software Development Tools Security & Risk Manager Customer Care API IaaS Deployment Architect Transition Manager Operations Manager Image Creation Tools Consumer Administrator Infrastructure TAM TDS TFIM Security. Partner Ecosystems TSRM SPE BSS – Business Support Services Customer Account Management TSRM SPE Service Offering Catalog TSRM SPE Service Offering Management TSRM SPE Service Development Portal & API BP Mgmt Interfaces API BPaaS Service Composer Service Automation Management TSAM TSRM SPE CCMDB TADDM Incident & Problem Managemen t TSRM TSRM SPE TSRM SPE Service Consumer Portal & API Service Integrator Offering Manager Software Mgmt Interfaces API SaaS Consumer Business Manager Platform Mgmt Interfaces API TSRM Provisioning TPM TPM IT Service Level Managemen TSLA t TNSQM TSRM SPE TSRM SPE TSRM SPE Service Creation Tools Service Management Development Tools Consumer Inhouse IT Business Processes Applications Middleware Infrastructure Service Management PaaS ITM. Performance & Consumability TSA MP TSA AM TSM 45 Governance © 2011 IBM Corporation .

IBM Cloud Computing Reference Architecture IBM recommended tools for consuming management functionality as a hosted offering Cloud Service Provider Cloud Services Consumer End user Common Cloud Management Platform OSS – Operational Support Services Service Delivery Catalog Tivoli Live Service Manager Service Manager Business Manager Service Component Developer Cloud Service Integration Tools Existing & 3rd party services. Partner Ecosystems BSS – Business Support Services Customer Account Management Service Offering Catalog Service Offering Management Service Development Portal & API BP Mgmt Interfaces API BPaaS Service Composer Service Automation Management Service Consumer Portal & API Service Integrator Offering Manager Software Mgmt Interfaces API SaaS Consumer Business Manager Platform Mgmt Interfaces API Tivoli Live Service Manager Incident & IT Service Problem Level Provisioning Managemen Managemen Tivoli Live t t Service Manager Service Creation Tools Service Management Development Tools Consumer Inhouse IT Business Processes Applications Middleware Infrastructure Service Management PaaS Tivoli Live Tivoli Live Service Manager Platform & Virtualization Management Infrastructure Mgmt Interfaces Service Runtime Development Tools Software Development Tools Security & Risk Manager Customer Care API IaaS Service Provider Portal & API Deployment Architect Transition Manager Operations Manager Image Creation Tools Consumer Administrator Infrastructure Security. Resiliency. Performance & Consumability 46 BCRS Governance © 2011 IBM Corporation .

IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions d ocumented in the RA and make implementationspecific ones throughout the entire process Define requirements and use im plementation guidance for cloud service and CCMP im plementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture o verview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security s n o i s i c e D l a r u t c e t i h c r A 3a Performance & Scalability Virtualization Management Resiliency Metering. Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” s d r a d n a t S + Non-functional Requirements Leverage guidance on specific technical areas as in put for developing a CCMP implementation + Consumability Operational Model 47 © 2011 IBM Corporation .

0: Operational Model Updates Primary focus on leveraging existing cloud implementations in IBM and other CC RA work products  Show how components are to be realized and deployed in a cloud-specific fashion  Harvest architectural patterns from existing cloud implementations (e. SBDTC)  RSA models for each level of elaboration which can be leveraged by adopters  System walkthroughs for major functional areas in Use Case Model and Component Model  Implementation guidance on realizing CC RA using IBM recommended tools identified in Component Model  Identify critical decision points and requirements used to guide the implementation 48 © 2011 IBM Corporation .g.IBM Cloud Computing Reference Architecture CC RA 2.

noting important considerations specific to Cloud  Walkthroughs show how the component operates in the context of the CCMP 49 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture The Operational Model emphasizes how a Cloud deployment differs  Adopter guidance on key decision points related to Cloud  Addresses each node and component realization specifically.

IBM Cloud Computing Reference Architecture Operational Model includes guidance for adopters to enable application to engagements  Implementation guidance includes: – Applied patterns showing how CC RA can be adapted to engagement-specific requirements – Recommended tool selection aligned with component mappings in the Component Model – Identification of architectural decisions and considerations of which practitioners need to be aware 50 © 2011 IBM Corporation .

Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” s d r a d n a t S + Non-functional Requirements Leverage guidance on specific technical areas as in put for developing a CCMP implementation + Consumability Service Flows 51 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions d ocumented in the RA and make implementationspecific ones throughout the entire process Define requirements and use im plementation guidance for cloud service and CCMP im plementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture o verview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security s n o i s i c e D l a r u t c e t i h c r A 3a Performance & Scalability Virtualization Management Resiliency Metering.

IBM Cloud Computing Reference Architecture CC RA –Service Flows TWP: Scope & Purpose  Defines all operational processes (“service flows”) required for managing cloud services based on a CCMP deployment. by building on high degree of standardization present in any cloud environment.  Service flows depend on service management components as defined in the CC RA component model – CCMP components are required for automating as many tasks as possible. 52 © 2011 IBM Corporation . – These service flows are focused on reducing labor costs for management to a minimum.

Monitoring Performance and Capacity Mgmt Service Level Management / Metering Service Request Management Continuity Mgmt © 2011 IBM Corporation . • Aimed at delivering cloud management processes for cost-competitive cloud infrastructures Manual as-is process Automated to-be process • Implementation of cloud-optimized service management processes • • • • • • • 53 Configuration and Asset Mgmt Patch / Provisioning / Image Mgmt Incident / Problem Mgmt. and opportunity for optimization to dramatically reduce labor costs. standardization.IBM Cloud Computing Reference Architecture CC RA Service Flows Content: Overview Service flows processes differences from standard IT management processes • Leverages reduced (eliminate) scope of management.

Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” s d r a d n a t S + Non-functional Requirements Leverage guidance on specific technical areas as in put for developing a CCMP implementation + Consumability Standards 54 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions d ocumented in the RA and make implementationspecific ones throughout the entire process Define requirements and use im plementation guidance for cloud service and CCMP im plementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture o verview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security s n o i s i c e D l a r u t c e t i h c r A 3a Performance & Scalability Virtualization Management Resiliency Metering.

APIs BSS UI Portal Cloud Domain Model and Terminology Cloud Management & Orchestration (Service Consumability Templates) Management Standards Security Virtualization (OVF.. assure solution portability. and which an organization chooses to implement as a basis for 'good practice'.0 Standards Conte By means of adhering to and driving the xt evolution of standards we ease adoption of our platform. Storage) Scop • Existing Cloud Computing and Management e Standards • Standards that are currently being defined • Standards that need to be defined (recommended standards) 1 2 3 3 5 1 1 1 4 6 2 1 1 6 1 8 7 8 8 4 1 4 1 5 6 7 8 A standard can be defined as something with a pre-described specification. © 2011 IBM Corporation 55 . Images Mgmt. recognized as having authoritative value. that is measurable. avoid vendor lock-in. Network.IBM Cloud Computing Reference Architecture Context and Scope of CC RA 2. and enable an ecosystem of partners around our platform.

IBM Cloud Computing Reference Architecture CC RA 2.0 Standards – Core Domain Model Overview 56 © 2011 IBM Corporation .

0 documents.0 Standards – Cloud Domain Model  Create a central... Virtualization 57 © 2011 IBM Corporation . authoritative domain model and terminology to be used consistently in cloud solutions  Cover core concepts that are common across cloud solutions.0  Make consistent with models that are defined or are being defined in IBM (e.0 and RA 2.g. and make consistent with RA 2.IBM Cloud Computing Reference Architecture CC RA 2. CDM) Security Roles Hybrid Cloud Core Concepts BSS . and their touch points to specific disciplines – Do not dive into specific domains to avoid duplication of work  Strong focus on (1) defining core concepts/terms and (2) defining how those concepts are related to each other  Collect input from RA 1.

IBM Cloud Computing Reference Architecture
1 3 3b
Leverage architectural decisions d ocumented in the RA and make implementationspecific ones throughout the entire process

Define requirements and use im plementation guidance for cloud service and CCMP im plementation Cloud Service Creation

2
Create cloud service and CCMP implementationspecific architecture o verview

Define cloud service and CCMPimplementation details

Service Flows

+
Use Cases

Architecture Overview

Component Model

Operational Model

Security

s n o i s i c e D l a r u t c e t i h c r A

3a
Performance & Scalability Virtualization Management Resiliency Metering, Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud”

s d r a d n a t S

+
Non-functional Requirements

Leverage guidance on specific technical areas as in put for developing a CCMP implementation

+
Consumability

Architectural Decisions

58

© 2011 IBM Corporation

IBM Cloud Computing Reference Architecture

Architectural Decisions TWP: Introduction & Purpose
 AD documents important decisions about any aspect of the architecture including the structure of the system, the provision and allocation of function, the contextual fitness of the system and adherence to standards  Consolidate ADs from key offerings, architectural domains and TWPs to provide a single place to find important ADs that illustrate rationale and justification of architectural decisions  Develop standard reusable artefacts that can be consumed by offering and engagement architects  Prove a reference of documented decisions that can help practitioners to: - avoid unnecessary reconsideration of the same issues - preserve design integrity in the provision of functionality and its allocation to system components - ensure that the architecture is extensible and can support an evolving system

59

© 2011 IBM Corporation

IBM Cloud Computing Reference Architecture

Scope Context - Capture ADs from key cloud offerings and architectural domains & TWPs Architectural Domain Subset*
Technical Work Products Cloud Delivery Models

Use Cases & Roles

SaaS
Managed Service Desk

Architecture Overview

PaaS

Security

Component Model

Operational Model

IaaS
(Public & private cloud)

Standards

Non Functional Requirements Service Flows

60

© 2011 IBM Corporation

SaaS – Managed Service Desk – 11 ADs  Domain specific Ads .IaaS .IaaS .Performance and scalability – 5 ADs 61 © 2011 IBM Corporation .Hybrid Cloud – 7 ADs .Metering / Accounting – 4 ADs .Resiliency – 1 AD .Public Cloud – 14 ADs .Private Cloud – 18 ADs .Virtualization management – 17 ADs .IBM Cloud Computing Reference Architecture Architectural Decision TWP Word Document Contains the following detailed ADs… In version 2 of the AD document we added decisions from the following areas on top of the decisions from version 1:  Applied Pattern Architecture Decisions .

Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” s d r a d n a t S + Non-functional Requirements Leverage guidance on specific technical areas as in put for developing a CCMP implementation + Consumability Security 62 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions d ocumented in the RA and make implementationspecific ones throughout the entire process Define requirements and use im plementation guidance for cloud service and CCMP im plementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture o verview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security s n o i s i c e D l a r u t c e t i h c r A 3a Performance & Scalability Virtualization Management Resiliency Metering.

Server. Access and Entitlement Management Data and Information Protection Management Threat and Vulnerability Management IT Service Management Command and Control Management Security Policy Management Risk and Compliance Assessment Physical Asset Management Security Services and Infrastructure Security Info and Event Infrastructure Identity. Access and Entitlement Infrastructure Host and End-point Security Security Policy Infrastructure Crypto. System and Service Assurance Identity. Key and Certificate Infrastructure Service Management Infrastructure Storage Security Application Security Network Security Physical Security Code and Images Security Service Levels Designs Policies Identities and Attributes Operational Context Events and Logs IT Security Knowledge Data Repositories and Classification Config Info and Registry © 2011 IBM Corporation . Compliance (GRC) People and Identity IT Infrastructure: Network.IBM Cloud Computing Reference Architecture IBM Security Framework: Business Security Reference Model Governance. Risk. End Point Data and Information Application and Process Physical Infrastructure Architectural Principles 63 Foundational Security Management Software.

64 © 2011 IBM Corporation . Only by combining foundational controls with activity/data specific controls can organizations meet their cloud security needs.IBM Cloud Computing Reference Architecture Activity/Data Driven Cloud Security Organizations need to adopt a strategy for cloud security that considers the unique attributes of the cloud as well as the activities and data the cloud is being utilized for.

Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” s d r a d n a t S + Non-functional Requirements Leverage guidance on specific technical areas as in put for developing a CCMP implementation + Consumability Performance & Scalability 65 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture 1 Define requirements and use im plementation guidance for cloud service and CCMP im plementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture o verview 3 Define cloud service and CCMPimplementation details 3b Service Flows Leverage architectural decisions d ocumented in the RA and make implementationspecific ones throughout the entire process + Use Cases Architecture Overview Component Model Operational Model Security s n o i s i c e D l a r u t c e t i h c r A 3a Performance & Scalability Virtualization Management Resiliency Metering.

Linux Technology Center (STG). and Goals Measurement methods and Metrics of Service Levels Roadmaps from Tivoli. and SoNAS (STG) 66 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture Performance & Scalability WG: Scope Performance and scalability relevant Scenarios & Use Cases Diga e nn s d Sino izgf CMb CPa sd e ahetu rcitcr e Architecture/ Operational Patterns for Performance and Scalability Consumable outcomes Performance and scalability service level KPIs.

Facilities © 2011 IBM Corporation . Network. Storage. CoR. and Pre-fetching – Pre-create/hibernate/resume VM 67 67 Virtualized Infrastructure – Server.IBM Cloud Computing Reference Architecture Architectural Patterns Initial focus on these CCMP Components Common Cloud Management Platform BSS Business Support System  Deployment patterns for OSS components – Multiple Virtualization Management domains – Horizontal Scaling of Provisioning components – Horizontal Scaling of Service Automation components – Multiple OSS domains Service Delivery Catalog OSS Operational Support System Service Templates Service Request Management Provisioning Service Automation Management  High Scale Low Touch Virtualization Management Virtualization Mgmt  Patterns and strategies for rapid provisioning – CoW boot disk of remote read-only images – Local caching of remote images and CoW root disk of local read-only image – Local caching of remote images and only transferring image delta – Use a combination of CoW.

2 Functions – 4.4 Measurements & metrics  3 Deployment patterns for CCMP OSS components – 3.IBM Cloud Computing Reference Architecture Outline of the WP document  1 Introduction – 1.3 Key Performance Indicators and Goals – 2.2 Influencing Scenarios and Factors – 2. and Measurements – 2.1 Scope of this document – 1.1 Architecture – 4.2 Supporting work products & references – 1. CoR.3 Local caching of remote images and only transferring image delta – 5. and Pre-fetching – 5.4 Multiple OSS domains 68  4 High Scale Low Touch virtualization management – 4. KPIs.3 Results – 4.3 Horizontal scaling of Service Automation components – 3.1 CoW boot disk of remote readonly images – 5.4 Use a combination of CoW. Use Cases.5 Pre-create/hibernate/resume VM  6 Applied Pattern: Compute Cloud  7 References © 2011 IBM Corporation .4 Targeted scenarios and use cases  5 Virtual systems rapid provisioning strategies – 5.1 Use Cases and Actors – 2.1 Multiple Virtualization Management domains – 3.2 Local caching of remote images and CoW root disk of local read-only image – 5.3 Legal Remark  2 Scenarios.2 Horizontal scaling of Provisioning components – 3.

Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” s d r a d n a t S + Non-functional Requirements Leverage guidance on specific technical areas as in put for developing a CCMP implementation + Consumability Virtualization Management – Base 69 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture 1 Define requirements and use im plementation guidance for cloud service and CCMP im plementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture o verview 3 Define cloud service and CCMPimplementation details 3b Service Flows Leverage architectural decisions d ocumented in the RA and make implementationspecific ones throughout the entire process + Use Cases Architecture Overview Component Model Operational Model Security s n o i s i c e D l a r u t c e t i h c r A 3a Performance & Scalability Virtualization Management Resiliency Metering.

scaling. Partner Ecosystems BSS – Business Support Services Customer Account Management Service Offering Catalog Service Offering Management BPaaS Service Delivery Catalog I A & a P t n m p o l D c i v r e S Service Automation Management I A & l a t P m u s n o C c i v r e S SaaS PaaS Contracts & Agreement Management Service Request Management Order Management Service Request Management Change & Configuration Management Incident & Problem Management IT Asset & License Management Image Lifecycle Management IT Service Level Management Capacity & Performance Management Subscription Management Pricing Entitlement Management Provisioning Monitoring & Event Management Metering Rating Billing Platform & Virtualization Management Clearing & Settlement Accounts Payable Accounts Receivable IaaS Deployment Architect Transition Manager Service Provider Portal & API Operations Manager Security & Risk Manager Inf rastructure © 2011 IBM Corporation . notification up)  Defines the capabilities and services for the management of virtual resources and the underlying physical resources  Base virtualization divided into 2 main sub components – Platform Management – Virtual Resource Management  Network and Storage Virtualization are sub teams and discussed separately Cloud Service Provider  Details what functions/subcomponents should be part of the Virtualization/Platform Management component – Definition of scope and functions  What is important for implementation/options in cloud environments for these functions – Considerations and what options are there. scaling and architecture decisions – Ex: local storage vs shared storage the implications there wrt Performance.Base  Component of the OSS layer – provides common interface across hetergenous infrastucture & value-add functions above infrastructure (pooling. placement. resiliency of the VMs  What standards/recommendations are there for implementations 70 Cloud Services Common Cloud Management Platform OSS – Operational Support Services Service Manager Business Manager Existing & 3rd party services. mobility. pros and cons – Performance.IBM Cloud Computing Reference Architecture Virtualization Management .

reporting. and patching of system firmware and hypervisor software. licensing. restart virtual servers – Relocation • Provides ability to move a virtual resource from one physical machine to another • May happen as a result of a failure. etc – Reservation • Reserves virtual resources for future use • Provides a reservation interface – Image Repository • Library of virtual appliances which can be deployed to create workloads – Deployment and Undeployment • Creation and deletion of virtual systems and network/storage resources at the request of the provisioning layer • Provides for intelligent allocation across the pool. Network and Storage infrastructure • Virtualization management component handles placement/allocation across the pool and optimization of the pool. – Bare Metal installation/distribution • Install and distribute OS and hypervisor software and agents – Platform health monitoring and reporting • Monitors health of physical systems and hypervisors • Used for billing services and SLAs 71 © 2011 IBM Corporation . may include over commit of physical resources – Instance Image Management • Provides management of deployed instances of the images. or planned maintenance  Platform Management – Discovery of physical resources • Library or catalog of discovered resources • Inventory such as options. stop. • Resource allocation can be based on a variety of criteria and factors such as energy. predicted failure.IBM Cloud Computing Reference Architecture Virtualization and Platform Management  Virtualization Management – Virtualization Platform Abstraction • Common interface to request and access virtual resources • Enables commonality for the higher level functions in the BSS and OSS layers – Virtual Resource Pooling • Ability to manage a set of virtualization infrastructure as a single entity or “pool” • Includes Compute. including ability to capture images – Management of virtual servers • Provides interface to start. availability. OS – Platform Software Maintenance • Monitoring. firmware.

IBM Cloud Computing Reference Architecture Virtualization and Platform Management  Standards – Platform management • DMTF CIM. Cloudburst. component model. SNMP – Virtualization management • DMTF OVF • Libvirt • Activation engine . Telco scenario 72 © 2011 IBM Corporation . resiliency. etc  Applied Patterns – Private cloud.VSAE  Non-Functional Requirements – Mostly centers around performance and scaling which is critical in a cloud environment – Details Documented in the NFR document  Input provided to other work products for performance.

IBM Cloud Computing Reference Architecture 1 Define requirements and use im plementation guidance for cloud service and CCMP im plementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture o verview 3 Define cloud service and CCMPimplementation details 3b Service Flows Leverage architectural decisions d ocumented in the RA and make implementationspecific ones throughout the entire process + Use Cases Architecture Overview Component Model Operational Model Security s n o i s i c e D l a r u t c e t i h c r A 3a Performance & Scalability Virtualization Management Resiliency Metering. Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” s d r a d n a t S + Non-functional Requirements Leverage guidance on specific technical areas as in put for developing a CCMP implementation + Consumability Virtualization Management – Networking 73 © 2011 IBM Corporation .

74 © 2011 IBM Corporation . – Capability extensions for virtual networking architecture and services. – Private networks w/in cloud infrastructure (with variation of access over Internet)..IBM Cloud Computing Reference Architecture Virtualization Management – Networking Summary  Identify BSS/OSS core components that are relevant to cloud (virtual) networking.  Identify a set of important cloud networking connectivity types (and patterns) to support cloud users (customers): – Shared cloud infrastructure network(s).e. CIM). – Private cloud to cloud virtual network (including hybrid cloud – from customer’s network to cloud). critical for supporting cloud networking as part of infrastructure authoritative topology DB.  Identify/define resources in resource model (i.

75 © 2011 IBM Corporation .e. connecting cloud services to virtual networks and automated network provisioning)..  Identify IBM products/assets that provide foundations for building out support for cloud networking and automated network provisioning.IBM Cloud Computing Reference Architecture Virtualization Management – Networking TWP Summary  Define subcomponents (and their expected capabilities) and services of Networking Virtualization Management in Virtualization and Platform Management overall component.  Relate cloud networking to on-going standard work in DMTF SVPC WG for virtual networking within OVF.  Extend cloud use cases to include networking connectivity (i.  Identify Architecture Decisions and NonFunctional Requirements related to networking.

IBM Cloud Computing Reference Architecture 1 Define requirements and use im plementation guidance for cloud service and CCMP im plementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture o verview 3 Define cloud service and CCMPimplementation details 3b Service Flows Leverage architectural decisions d ocumented in the RA and make implementationspecific ones throughout the entire process + Use Cases Architecture Overview Component Model Operational Model Security s n o i s i c e D l a r u t c e t i h c r A 3a Performance & Scalability Virtualization Management Resiliency Metering. Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” s d r a d n a t S + Non-functional Requirements Leverage guidance on specific technical areas as in put for developing a CCMP implementation + Consumability Resiliency 76 © 2011 IBM Corporation .

0 Resiliency CC RA 2.0 Resiliency  Defined cloud Resilience architecture  Based on lessons learned from implementations  Mapped architecture to proposed CCMP resilience implementation  Identified required products  NFRs enhancements Key learning from existing cloud implementations  OSS/BSS interdependencies and operational requirements must be considered in coordinated resilience and automation design 77 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture CC RA 2.

Rating and Accounting 78 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture 1 Define requirements and use im plementation guidance for cloud service and CCMP im plementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture o verview 3 Define cloud service and CCMPimplementation details 3b Service Flows Leverage architectural decisions d ocumented in the RA and make implementationspecific ones throughout the entire process + Use Cases Architecture Overview Component Model Operational Model Security s n o i s i c e D l a r u t c e t i h c r A 3a Performance & Scalability Virtualization Management Resiliency Metering. Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” s d r a d n a t S + Non-functional Requirements Leverage guidance on specific technical areas as in put for developing a CCMP implementation + Consumability Metering.

Rating and Accounting Domain addresses: – Different types of metered usage data (3 Key types) and the need to meter both Allocated and Activity based data – BSS-OSS mapping of runtime and design time data flows – Product specific detailed functional gap analysis with tool recommendations – Solution architecture along with implementation guidance  3 Applied Patterns from architecture as applicable to Public. Rating & Accounting: Executive Summary  Metering. Private clouds and an ISV context are explained 79 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture Metering.

 Activity Usage – The result of activity performed by the consumer e. Bytes transferred etc – More suitable as Cost Usage Metric. Websphere Cluster) has been allocated to a particular cloud service. Database.g.IBM Cloud Computing Reference Architecture Terminology: Metered Usage Data Concepts  Allocation Usage – The result of a consumer occupying a resource such that other consumers cannot use it – For example.g. Storage. Network.g. Backup/restore server. the time period IT infrastructure topology (e. CPUs. – More suitable as Service Usage Metric. Servers.  Action Usage – Actions initiated by the consumer that the provider may wish to charge for or track costs against • e. change virtual server configuration – Action may or may not involve manual steps 80 © 2011 IBM Corporation . Memory. CPUSecs.

40/min Server 2 CPU usage = 2.000 CPU mins * $.100 $2.600 Profit Cloud Service Requestor #3 Service B 2 CPUs on Server 1 1 GB 100 server hrs @ $20/ server hr 200 CPU hrs @ $3/ CPU hr 100 GB hrs @ $2/ GB hr 100 DB2 Support hr @ $2/ DB2 Support hr Cloud Service Provider Service A revenue = $5.000 CPU mins * $.100 Service A costs $4.500 CPU mins * $.000 Service B costs = $3.60/min Server 1 software usage = 60 hrs * $15/hr Cloud Service Requestor #2 Service A 3 CPUs on Server 2 4 GB 50 server hrs @ 25/ server hr 150 CPU hrs @ $5/ CPU hr 200 GB hrs @ $3/ GB hr $3.IBM Cloud Computing Reference Architecture Cloud Delivery Requires Allocation and Activity Usage Cloud Service Requestor #1 Service A 4 CPUs on Server 1 2 GB 60 server hrs @ $25/ server hr 240 CPU hrs @ $5/ CPU hr 120 GB hrs @ $3/ GB hr Allocation Usage Service A Costs Activity Usage Cloud Service Provider Server 1 CPU usage = 3.40/min Server 1 software usage = 80 hrs * $15/hr Server 1 labor costs = $40 DB2 Help Desk = $50 Service B revenue = $3.290 Loss 81 Cost and prices are for illustration purposes only © 2011 IBM Corporation .660 Service B Costs Server 1 CPU usage = 5.060 Server 2 software usage = 40 hrs * $10/hr Server 1 labor costs = $40 Server 2 labor costs = $60 Service A costs ==$4.

IBM Cloud Computing Reference Architecture Metering Rating & Accounting: BSS – OSS Mapping BSS Cost/Price Accounting Usage Accounting Usage Reports Billing Records Adjustment Tax Rules Billing Terms Billing Record Generation Rated Usage Reports Contracts & Agreements Rates /Prices Provider’s Rating & Accounting of Usage Accounting Records Qualified Usage Accounting Records Business context Accounting Structures Qualified Usage Accounting Records Generation OSS Correlated Usage Records Service context Usage Data Qualification Rules Correlation & Aggregation Rules (Service) Metered Usage Data Correlation Metered Usage Data: Allocation. Action(Labor) Local context Data Correlation & Aggregation Rules (each source) Metrics Definition Metered Usage Data Generation Instrumented Service Management System 82 Manages Instrumented Service Hosting System © 2011 IBM Corporation . Activity.

Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” s d r a d n a t S + Non-functional Requirements Leverage guidance on specific technical areas as in put for developing a CCMP implementation + Consumability BSS Decomposition 83 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture 1 Define requirements and use im plementation guidance for cloud service and CCMP im plementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture o verview 3 Define cloud service and CCMPimplementation details 3b Service Flows Leverage architectural decisions d ocumented in the RA and make implementationspecific ones throughout the entire process + Use Cases Architecture Overview Component Model Operational Model Security s n o i s i c e D l a r u t c e t i h c r A 3a Performance & Scalability Virtualization Management Resiliency Metering.

which is a set of computer systems and related processes used to deliver the services.44-page doc with the following sections: – BSS positioning within CCMP – Overview of BSS functions required for all realizations – Public Cloud realization – Private Cloud realization – Brief discussion of hybrid cloud and product development realizations – Future direction – BSS as a Service for promoting re-use and modularization 84 © 2011 IBM Corporation . BSS and OSS functions for all IBM Cloud services are provided by the Common Cloud Management Platform (CCMP)  BSS Decomposition RA content .IBM Cloud Computing Reference Architecture Business Support Services Decomposition  Business Support Services (BSS) is a set of components that enables interaction of customers with the service provider. BSS works closely with Operational Support Services (OSS).

0 conceptual CM for Business Support Services Security & Compliance management Customer Account mgmt Customer Account mgmt Customer information mgmt Customer information mgmt User identity mgmt User identity mgmt User access mgmt User access mgmt Customer Management Contracts & agreements mgmt Contracts & agreements mgmt Register contract/agreement Billing Schedule Register contract/agreement Billing Schedule Contracted Rating Contracted Rating Contract generation Contract generation BSS – Business Support Services BSS – Business Support Services Service Offering Management Service Offering Management Offering Lifecylce mgmt Offering Lifecylce mgmt Options configuration & rule mgmt Options configuration & rule mgmt Service Offering management Service Offering Catalog Service Offering Catalog List prices List prices Discount Discount Pricing Pricing Price information mgmt Price information mgmt Price model Price model Service Development Portal Service Consumer Portal 85 Service Service Request mgmt Request mgmt Subscription Subscription mgmt mgmt Metering Metering Subscription Management Entitlement mgmt Entitlement mgmt Entitlement tracking Entitlement tracking Order management Order management Enter & manage order Delivery status monitoring Enter & manage order Delivery status monitoring Manage license/Entitlement Manage license/Entitlement Clearing & settlement Clearing & settlement Royalty mgmt // payment Royalty mgmt payment ISV // Vendor payment ISV Vendor payment Financial Management Accounts Payable Accounts Payable Accounts Receivable Accounts Receivable Rating Rating Billing Billing Financial data release Financial data release Process billing charges Create & release invoice Process billing charges Create & release invoice Service Provider Portal © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture CCMP RA 2.

using Tivoli Service Request Manager – Service Provider Edition + Tivoli Usage and Accounting Manager TSRM-SP provides all these functions Notes on METERING TSRM provides Allocation & Activity-based Metering. TSRM tracks labor. tools. services costs. materials.IBM Cloud Computing Reference Architecture Private Cloud Realization . TUAM provides Usage-based Metering RATING & BILLING TSRM & TUAM provide partial rating functions & bill data generation – but not direct invoicing 86 NO Peering and Settlement NO accounts payable/receiving © 2011 IBM Corporation .

Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” s d r a d n a t S + Non-functional Requirements Leverage guidance on specific technical areas as in put for developing a CCMP implementation + Consumability Hybrid Cloud 87 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture 1 Define requirements and use im plementation guidance for cloud service and CCMP im plementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture o verview 3 Define cloud service and CCMPimplementation details 3b Service Flows Leverage architectural decisions d ocumented in the RA and make implementationspecific ones throughout the entire process + Use Cases Architecture Overview Component Model Operational Model Security s n o i s i c e D l a r u t c e t i h c r A 3a Performance & Scalability Virtualization Management Resiliency Metering.

IBM Cloud Computing Reference Architecture Hybrid Cloud Workstream: Scope and Dimensions  Scope and Purpose: – Use Cases: Identify use cases and scenarios for – – – – hybrid cloud setup. availability. and management Patterns: Identify solution patterns for integration of on-premise with services in public cloud(s) Life-cycle: Identify and define workload migration and life cycle events for services in hybrid cloud Roles: Identify roles associated with hybrid cloud operations and services Decisions: Define architectural decisions for hybrid cloud integration framework and for hybrid cloud management services  Dimensions: – Integration: How to connect on-premise services and data to off-premise counterparts… business data mapping and service integration – Security: How to integrate on-premise/offpremise identities. auditing systems. – Management Perspective: Unified view and capability to manage resources and information onpremise and in off-premise Clouds combined with management and integration of workloads and resources across hybrid cloud – Management: Manage Capacity in the cloud. How to secure management and payload interactions – Monitoring: Integrate monitoring of off-premise infrastructure and applications with on-premise management system. how to ensure proper security of off-premise cloud workload. policies. should use which cloud-based services…service request management of on.and de-provisioning based on Monitoring data). etc. capacity overflow from onpremise to Cloud – Governance: Who can.and off-premise resources 88 © 2011 IBM Corporation . performance. Enable on-premise monitoring and event infrastructure to reach into clouds  Perspectives – Operating Perspective: Seamlessly move peek workloads from on-premise to public Cloud – Sourcing Perspective: Different types of workloads to be provisioned by the most effective Cloud from the perspective of cost. security. does. functionality. provisioning. operations.

Data Cleansing 89 © 2011 IBM Corporation . Query Access.IBM Cloud Computing Reference Architecture Hybrid Cloud: Use Case Scenarios Examples: Examples: Hybrid Cloud Integration Connect off-premise monitoring events to on-premise monitoring system IBM Cloud Hybrid Cloud Integration Database Sync customer records Tivoli Monitoring Server Hybrid Monitoring Example Federate Monitoring info of Workload in IBM Public Cloud Examples: On-premise to off-premise Business Application Integration: Example: On-premise Database to Salesforce Cloud Examples: Private (On Premise Resources) Common Cloud Manageme nt Platform Hybrid Cloud Integration Mgmt and Capacity Overflow of/to Public Cloud Common Cloud Manage mentPlat form Public Cloud Resources (IBM Cloud) Hybrid Cloud Integration LDAP Directory Sync on-premise identity model and directory Governance & Hybrid Workload Management Examples: Governance for acquiring Resources from IBM Compute Cloud and/or Amazon. Workload Management and capacity overflow from CCMP based private Cloud to IBM Compute Cloud ERP Data DB2 Hybrid Cloud Integration Query Access Replication Examples: Security: Directory Integration & Identity Federation Example Synchronize on premise ODW LDAP and LotusLive Domino directory info and facilitate SSO Cognos Apps DB2 Staging DB Cognos BI SIB Staging DB Cognos and other Analytic Applications in the Cloud: Initial Load to Cloud. Change Data Capture Replication to & from Cloud.

Problem & Change Management IT Asset & License Management Virtualization Mgmt Image Lifecycle Management IT Service Level Management Capacity & Performance Management Monitoring.Cloud Management Platform * IBM Cloud Computing Reference Architecture – Hybrid Cloud Model Common Cloud Management Platform BSS Business Support Services Offering Mgmt Order Mgmt Accounting & Billing Contract Mgmt Customer Mgmt Entitlements Invoicing SLA Reporting Metering. Security and Policy Enforcement Cloud Service Broker Private Cloud IBM Development & Test Cloud 3rd Party Cloud Services © 2011 IBM Corporation . Analytics & Reporting Pricing & Rating Subscriber Mgmt Peering & Settlement Service Offering Catalog Service Development Portal Hybrid Cloud Integration: Client Controlled from within the enterprise 90 90 Service Delivery Portal OSS Operational Support Services Service Templates Service Request Management Provisioning Monitoring & Event Management Service Delivery Catalog Updated for Hybrid Cloud API Service Automation Management Configuration Mgmt Incident. Metering.

Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” s d r a d n a t S + Non-functional Requirements Leverage guidance on specific technical areas as in put for developing a CCMP implementation + Consumability Multi-tenancy 91 91 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions d ocumented in the RA and make implementationspecific ones throughout the entire process Define requirements and use im plementation guidance for cloud service and CCMP im plementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture o verview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security s n o i s i c e D l a r u t c e t i h c r A 3a Performance & Scalability Virtualization Management Resiliency Metering.

IBM Cloud Computing Reference Architecture Multi-tenancy .scope Multi-tenancy requirements and customer expectations Don e Partia l Requirements mapping to CC RA component for impact and gap analysis Multi-tenant patterns Leveraging existing multi-tenancy assets and capabilities Specification of how secure Multi-Tenancy should be implemented across the CC RA components 92 © 2011 IBM Corporation .

IBM Cloud Computing Reference Architecture Multi-tenancy deliverables Multi tenant NFRS Use Cases and extensions Component impact analysis Multi-tenancy definition Tenant definition Multi-tenant patterns whitepaper adopted NFR deliverable Use case deliverable Component deliverable adopted adopted 93 93 © 2011 IBM Corporation .

IBM Cloud Computing Reference Architecture Multi-tenant definition Multi-tenancy refers to the ability of services to be offered to multiple user entities (tenants) in a way so that each tenant operates as logically isolated. using physically shared resources. in fact. while. 94 © 2011 IBM Corporation .

The Cloud service instance requested by the Service Owner 1:n Service Resources The resources consumed by the service Application Platforms Virtual Machine Storage Network component 95 95 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture Tenant definition 1 Tenant 1 1 Consumer Business Manager 1:n 1 1:n Consumer Administrator 1 1:n Consumer End User 1:n 1 Service Instance 1 A role within the business entity that manages contracts and optionally approves commission of services from the Cloud The users of the Service A business entity that is contractually responsible for the consumption of Cloud Service from a service provider. A role within the business entity that will request commission and decommission services from the Cloud.

Infrastructure Data center floor Infrastructure Data center floor Infrastructure Data center floor Infrastructure Data center floor Data center floor I Physical-level multi-tenancy Legend: Dedicated Shared II Hypervisor-level multi-tenancy III Operating System-level multi-tenancy IV Platform-level multi-tenancy 96 © 2011 IBM Corporation . Multi-tenancy needs of public and private clouds. 3. Multi-tenancy of managing and manage environments 4. OS OS OS OS Operating System Operating System Operating System Infrastr. Associated multi-tenant characteristics that will have to be supported in any Cloud implementation.IBM Cloud Computing Reference Architecture Multi-tenancy whitepaper Multitenancy service considerations Standardisation Security risk Cost/tenant Low Low High Tenant Tenant Tenant Tenant Tenant Tenant Tenant Tenant Tenant High High Low Tenant App App App App App App App App Application Platform Platform Platform Platform Platform Platform Pla tform Platform 1. Infrastr. Primitive set of patterns of multitenancy 2.

Cloud Computing Reference Architecture 2.0: Overview CC RA team / presented by Mike Buzzetti © 2011 IBM Corporation 1 .

0 –Target audience –How to apply the RA for cloud implementations Cloud Computing Reference Architecture Details 2 08/03/11 © 2011 IBM Corporation 2 .IBM Cloud Computing Reference Architecture Agenda Executive Summary Introduction & Overview –Historical evolution of the Reference Architecture –Structure of the RA 2.

scalability and control The CC RA consists of 21 detailed documents representing best-of-industry knowledge and insight on how to architect. Partner Ecosystems Cloud Service Integration Tools Business-Processas-a-Service Sof tware-as-a-Service Operational Support Services (OSS) Platf orm-as-a-Service Business Support Services (BSS) Service Creation Tools Consumer In-house IT Infrastructure-as-a-Service The CC RA focuses on cloud specifics such as radical cost reduction while achieving high degrees of security. Performance & Consumability Governance © 2011 IBM Corporation Mike Buzzetti notes Existing legacy products and technology can be mapped to to the CCRA since the CCRA shows integration points between new cloud technologies and the existing ones 3 . including IBM Research The IBM Cloud Computing Reference Architecture (CC RA) is reflected in the design of – – – – IBM-hosted cloud services Clouds IBM implements for clients IBM cloud appliances IBM cloud service management products Cloud Service Consumer Cloud Services Cloud Service Provider Common Cloud Management Platform (CCMP) Cloud Service Creator Existing & 3rd party services. software & system experiences. reliability. Resiliency. design and implement clouds 3 08/03/11 Inf rastructure Security.IBM Cloud Computing Reference Architecture IBM Cloud Computing Reference Architecture The IBM CC RA represents the aggregate experience across hundreds of cloud client engagements and the implementation of IBM-hosted clouds – Based on knowledge of IBM’s services.

SOA solutions usually have to have the management built from scratch SOA service reuse is generally only within the organization that delivers the service. “ That basically means that cloud computing supports service orientation SOA solutions usually do not have all the characteristics of cloud simultaneously.IBM Cloud Computing Reference Architecture The IBM Cloud Computing Reference Architecture ensures consistency & quality across IBM development and delivery projects The IBM Cloud Computing Reference Architecture … Is based on open standards Delivers enterprise-class security to meet local. including Infrastructure as a Service (IaaS). top-to-bottom management of cloud infrastructure and cloud services Supports the full spectrum of cloud service models. Software as a Service (SaaS) and Business Process as a Service (BPaaS) Enables the flexible scaling and resiliency required for successful cloud economics and ROI Facilitates seamless integration into existing customers' environments Is based on our industry leading expertise with SOA for building services and serviceoriented architectures 4 08/03/11 © 2011 IBM Corporation SOA is defined by the open group as “an architectural style that supports services orientation Service orientation is a way of thinking of services and services-based development and the outcomes of services. Not all SOA solutions are cloud servers. Platform as a Service (PaaS). regional and national compliance for privacy and governance Combines powerful automation and services management (low touch) with rich business management functions for fully integrated. since cloud requires automated deployment and management 4 .

IBM Cloud Computing Reference Architecture IBM Cloud Computing Reference Architecture: Development Process Development led by the IBM Cloud Computing Architecture Board Comprising technology leaders from IBM Research and IBM’s software. virtualization) – Software components required to run management – Operational processes – Governance policies tailored for the environment or enterprise. Derived from extensive client interaction combined with IBM’s extensive capabilities and experience in building enterprise-class IT systems. systems and services organizations >50 of IBM’s top cloud computing experts represent the core team A process of continuous improvement helps ensure that the reference architecture is both responsive to changing client and security requirements and incorporates technology developments via IBM products and evolving design specifications. storage. compute. The CC RA provides specifications for – the physical components of a cloud implementation (network. 08/03/11 5 © 2011 IBM Corporation 5 .

IBM Cloud Computing Reference Architecture

The IBM Cloud Computing Reference Architecture covers are broad range of important cloud-specific topics

6

08/03/11

© 2011 IBM Corporation

6

IBM Cloud Computing Reference Architecture

Structure of the IBM Cloud Computing Reference Architecture
There are two deliverables for each work product of the RA
– Document: Detailed description of the work product, important for indepth work – Presentation: Summary of the document, for simplified consumption and quick start

IBM Cloud Computing Reference Architecture
Captures cloudspecific architectural decisions made on any other work product

Use Cases

Non-functional Requirements

Functional (=use cases) and non-functional requirements against the other RA work products

Cross-domain work products

Defines all cloudspecific standards

Architecture Overview
Defines architectural building blocks Product-agnostic

“Cloudified” management processes for operating cloud services with cloudscale-efficiency

Architectural Decisions Architectural Decisions

The RA is defined according the Unified Method Framework (UMF)
Simplifies field adoption since all IBM field architects attend UMF training by default

Service Flows

Standards

Cross-cutting work product encompassing all security aspects relevant in the context of the CC RA.

Security

Component Model
Refines architecture overview to the next level of detail

Operational Model
Deployment-level view of the reference architecture

Consistent & prescriptive architecture across all technical domains

Domain-specific work products

Each work product includes one or more “applied patterns”
– An applied pattern illustrates how the respective work product could be used / was used in a specific 7 08/03/11 implementation

Performance & Scalability

Cloud Service Creation

Multi-tenancy

“Production cloud”

Virtualization Management

Hybrid Cloud

Resiliency

Metering, Rating and Accounting

BSS Decomposition

Consumability

© 2011 IBM Corporation

IBM Cloud Computing Reference Architecture

IBM Cloud Computing Reference Architecture: Domain work product details
IBM Cloud Computing Reference Architecture
How to implement a cloud to achieve optimal performance & scalability Use Cases Non-functional Requirements

Cross-domain work products

Architectural Architectural Decisions Decisions

Guide for creating cloud services and how to exploit management functions.

Architecture Overview Service Flows

Standards

Security

Component Model

Operational Model

Considerations for implementing multitenancy in a cloud environment

Domain-specific work products

Performance & Scalability

Cloud Service Creation

Multi-tenancy

“Production cloud”

Virtualization Management

Hybrid Cloud

Resiliency

Metering, Rating and Accounting

BSS Decomposition

Consumability

Example for how to implement a cloud management system for offering production-level cloud services

Definition for how to use virtualization management across server, storage and network 8 08/03/11

Architecture & implementation considerations for implementing a hybrid cloud

Resiliency considerations for implementing a cloud

Details on metering, rating and accounting, including prescriptive guidance with respect to implementation

Detailed definition of BSS domains and how they should be implemented from a product perspective

How to optimize the end to end experiences related to cloud services © 2011 IBM Corporation

resiliency • Hybrid clouds © 2011 IBM Corporation 9 . • Continuously ongoing harvesting process due to additional learnings during each phase 9 08/03/11 • Continuous improvement of CC RA content based on feedback from CC RA exploiters & stakeholder • Be clear about which parts of the RA are already addressed in today’s IBM cloud offerings and which aspects still have to be addressed • Today’s cloud implementations are not necessarily optimal implementations (due to time & resource constraints)  Need forward-looking guidance on ideal target implementation •Examples are: • generalization of CCMP services • layered cloud services • NFRs.g.g. security.IBM Cloud Computing Reference Architecture The IBM Cloud Computing Reference Architecture – Aggregating past & present experience and future requirements CC RA = Harvesting (“Learning from cloud deployments in the past?”) + Refinement (“Improve the CC RA content presently available”) + Forward looking (“Which future topics are relevant for cloud computing”) • Harvest learnings & material from cloud implementations while factoring out short cuts taken by implementation team (e. e. due to constrained time lines).

Rating and Accounting Standards + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a cloud service & CCMP implementation + Consumability BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” 10 08/03/11 © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture How to implement a cloud using the IBM Cloud Computing Reference Architecture 1  There is a well-defined process for using the RA to implement a cloud service – A cloud is constituted by a CCMP implementation and an arbitrary number of cloud services delivered and managed by it  A dedicated presentation and document is available describing the process for using the RA to develop the management aspects for a cloud service  RA work products also serve as authoritative reference on specific technical topics for education purposes Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview 3 Define cloud service and CCMPimplementation details 3b Service Flows Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process + Use Cases Architecture Overview Component Model Operational Model Architectural Decisions 3a Security Performance & Scalability Virtualization Management Resiliency Metering.

Create cloud service / CCMP implementationspecific architecture overview. Reference RA-level standard definitions Service Flows Create cloud service / CCMP implementationspecific operational model. Work products serving as the basis for a cloudspecific work product: All “cross-domain” work products plus “Cloud Service Creation” 11 11 08/03/11 Document cloud service-specific decisions made for each step of the cloud service creation process. Use the RA-level work product as a reference for step definitions and product recommendations Create cloud service / CCMP implementationspecific service flows. Leverage experience documented as part of ADs being part of the RA Work product to be created on a per cloud service basis © 2011 IBM Corporation . Reference RAlevel component model Define cloud-service / CCMP implementation-specific standards being used. Rating and Accounting BSS De-composition Assess end to end experience creating. Reference RA-level NFRs serving as a basis Resiliency Metering. Reference RAlevel operational model Cloud Service Creation + Use Cases Architecture Overview Component Model Operational Model Architectural Decisions + Non-functional Requirements Document cloud service-specific use cases. based on RAlevel AOD Create cloud service / CCMP implementationspecific component model.IBM Cloud Computing Reference Architecture Using the CC RA: Which work products have to be created on a per cloud service basis?  The RA contains two types of work products 1. operating and managing this cloud service Hybrid Cloud Multi-tenancy “Production cloud” Capture cloud service / CCMP-implementation specific architectural decisions. Refer to RA-level service flows. Reference RA-level use cases serving as a basis Standards Security Performance & Scalability Virtualization Management + Consumability Document cloud service-specific NFRs. Work products only serving as a reference documentation for specific aspects of implementing a new cloud: All “domainspecific” work products except “Cloud service creation” 2.

IBM Cloud Computing Reference Architecture Cloud Computing Reference Architecture Details 12 08/03/11 © 2011 IBM Corporation 12 .

IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security n o s D l a us er td in ha ct rS A 3a Performance & Scalability Virtualization Management Resiliency Metering. Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a CCMP implementation + Consumability Cloud Service Creation 13 08/03/11 © 2011 IBM Corporation 13 .

Focus is on the management aspects as they apply generically across all types of cloud services – Provide detailed description of basic terminology relevant for creating cloud services – Provide prescriptive product recommendations relevant for each cloud service creation step and tooling around that – Provide illustrative examples (“applied patterns”) for how a new cloud service can be created 14 08/03/11 Cloud Service Consumer Cloud Services Cloud Service Provider Can be on any Can be on any Common Cloud aaS-layer aaS-layer Management Platform (CCMP) Business-Processas-a-Service Exploit Management (OSS & BSS) functions Cloud Service Creator Existing & 3rd party services. Partner Ecosystems Cloud Service Integration Tools “New Software-as-a-Service Cloud Service” Operational Support Services (OSS) Business Support Services (BSS) Service Creation Tools Platform-as-a-Service Consumer In-house IT Exploit runtime functions Infrastructure-as-a-Service Inf rastructure Security.IBM Cloud Computing Reference Architecture “Cloud Service Creation” – Scope and Overview Objective: Describe all aspects around developing a new cloud service – Scope is end-to-end process for developing a new cloud service. Performance & Consumability Governance © 2011 IBM Corporation . Resiliency.

IBM Cloud Computing Reference Architecture

Developing cloud services – four major segments: Overview
Existing management tooling, processes and operations staff?
Yes

Outsourcers

IT organizations within enterprises

Although having different motivations, software & process legacy and requirements, there is a common approach for creating cloud services across all segments
Yes

Want to own IT infrastructure & have runtime & mgmt software installed onpremise?

No

ISVs

Communication Service Providers & new Cloud Service Providers

Different scenarios for offering cloud services require - different delivery models for management software (“buildit-yourself” vs. IBM-hosted) - different levels of integration with existing management tools

No

15

08/03/11

© 2011 IBM Corporation

IBM Cloud Computing Reference Architecture

Anatomy of a Cloud service – Highlevel overview
The internal structure of a cloud service is the integration 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. defined in the CC Reference Architecture

Cloud Cloud Cloud service service service instances instances instances

delivers

Cloud Service Consumer A

Request, modify & use cloud service instances

Management functions (operational & business) Cloud Service (*-aaS)
e.g. VM-aaS, Storage-aaS, WAS-aaS, WebConf-aaS, etc.

Cloud Cloud Cloud service service service instances instances instances

delivers

Cloud Service Consumer B
delivers
Cloud Cloud Cloud service service service instances instances instances

E.g. automated delivery & self-service mgmt, entitlement, rating, provisioning, monitoring, metering, patch management, high availability, backup & restore, incident & problem management, etc.

operates

Runtime functions
E.g. compute power, hypervisors, storage capacity, network isolation zones, load balancers, web & application servers, database management systems, analytics engines, business process & portal engines, etc.

Cloud Service Consumer C Example – Julieanswers.com cloud service: - Julieanswers ear file - IHS/WAS/DB2 running the julieanswers ear file - Virtual machines running IHS/WAS/DB2 - TivoliLive monitoring the health of the julieanswers app and the underlying IHS/WAS/DB2 installation - Billing tool - BCRS to backup the julieanswers db2 database 16 08/03/11

Cloud Service Provider Operations staff

© 2011 IBM Corporation

IBM Cloud Computing Reference Architecture

12 steps towards creating a cloud service
2. Implement runtime functionality
App MW OS Server Storage Network 11 11 * 11

3. Define unit of delivery & rating
1 * 1 1

4. Implement self-service delivery & management functionality

*

Describe function, price , SLA of cloud service, incl. management scope

Examples: Select off-the-shelf hypervisor (VMaaS), implement custom app (e.g. LotusLive)

Examples: VM, file system, distributed app, virtual IP address, queue, web conference, RDBMS, 3-tier business app, etc.

Examples: “Create VM, add more nodes to WAS cluster, change max # of seats for LotusLive web conf

5. Implement monitoring metrics & event correlation rules

6. Implement incident, problem and asset mgmt processes

7. Implement resiliency SLA

8. Implement backup approach

!

Select existing agent / implement new agent for monitoring JVM heapsize, hypervisor swap file size, # of processes, etc.

Incident, problem & asset mgmt process is specific to cloud service  customization needed

Examples: HA for management system, delivered WAS cluster must be highly available

Examples: Backup all VMs, backup DB of LotusLive application

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

1 11 1 1 11 * 1

* 1

11 * 11 1 1

1 * 1

* 1

$$ $
A cloud service must be registered to the service catalog to be externally accessible, entitlements need to be configured,

Implement authentication, auditing, data protection, governance & audit

Examples: CPU/hour, # of DB transactions, GB/month, # of users/webconf/hour, etc.

Examples: $0.11/VMhour; $0.19/MBsTransferred; $0.02/webconference; $0.05/fraudAnalysis

17

08/03/11

© 2011 IBM Corporation

Implement self-service delivery & management functionality 5. Specify cloud service description 2. Linux.IBM Cloud Computing Reference Architecture Overview: Recommended management products. Implement rates for charging cloud service consumption 12. Implement backup approach 9. DB2. Define Unit of delivery & rating 4. … n/a (cross-cutting decision) TSAM IBM Tivoli Monitoring. WAS. Implement resiliency SLA 8. VMware. Implement runtime functionality of the cloud service Products & technologies to build your own cloud service n/a (cross-cutting) KVM. Windows. to be exploited on a per cloud service basis Step 1. Filenet. Implement cloud service specific billing metrics 11. Impact Tivoli Service Request Manager & TAMIT Tivoli System Automation Tivoli Storage Mgr Tivoli Security / ISS portfolio TUAM TUAM TSAM / TSRM Service Provider Edition 3. Implement incident. Cognos. Implement security functions 10. problem and asset mgmt processes 7. Implement monitoring metrics & event correlation rules 6. Register cloud service to service catalog 18 08/03/11 © 2011 IBM Corporation . Omnibus.

Implement security functions Tivoli Security & ISS Portfolio 10.IBM Cloud Computing Reference Architecture Overview: Recommended management products. no image creation tools available today VM golden master image. Linux. jobplans. Implement self-service delivery & management functionality TSAM & TPM TSAM SD app TPM ADPE Universal Agent Builder (ITM) Omnibus-internal tooling TSAM Service definition & TPM provisioning workflows 5. Impact Monitoring agent (ITM). VMware. development tools and artifacts to be created on a per cloud service basis Step Products & technologies Building a cloud service hosted within the provider’s premise Development/Config Tool Cloud service specific configuration / artifact 1. Implement rates for charging cloud service consumption TUAM UI and CSV file import 12. … Rational Dev tools (for app artifacts). problem and asset mgmt processes Tivoli Service Request Manager & TAMIT TSRM-internal apps Incident & problem management workflows. WAS. Define Unit of delivery & rating n/a (cross-cutting decision) n/a n/a 4. DB2. Register cloud service to service catalog TSAM / TSRM Service Provider Edition TSAM/TSRM internal apps Registration persisted in TSAM/TSRM internal database 19 08/03/11 © 2011 IBM Corporation . Implement backup approach Tivoli Storage Mgr TSM Backup agent Backup policy Various various 9. JEE ear file. etc. Specify cloud service description n/a (cross-cutting) n/a n/a 2. SQL file. event correlation rule (Omnibus) 6. Windows. Implement resiliency SLA Tivoli System Automation Text editor (no dedicated tooling) HA policy 8. Omnibus. Implement runtime functionality of the cloud service KVM. Cognos. Filenet. Implement monitoring metrics & event correlation rules IBM Tivoli Monitoring. 3. escalations (TSRM) 7. Implement cloud service specific billing metrics TUAM No dedicated tooling available Metering collectors Job files Rates persisted in TUAM database 11. Implement incident.

DB2. etc. Partner Ecosystems Tivoli Service Automation Manager Workflows. metering collectors Editor Tivoli Usage & Accounting Manager Service Automation Management Service Consumer Portal & API TPM workflows APDE SaaS Tivoli Provisioning Manager ITM Agents ITM Agent Builder Provisioning Incident & Problem Managemen t IT Service Level Managemen t Service Creation Tools PaaS IBM Tivoli Monitoring CSV file Event cor. rule Omnibus-int. JEE ear file. VMware. Performance & Consumability Governance © 2011 IBM Corporation 20 08/03/11 . no image creation tools available today KVM. escalations TSRM-internal apps Tivoli Service Request Manager TPM for OSS – Operational SupportImages Services BSS – Business Support Services Customer Account Management Service Offering Catalog Service Offering Management Service Development Portal & API BPaaS Service Delivery Catalog Cloud Service Integration golden master Tools VM image. tooling Omnibus & Impact HA policy Editor Tivoli System Automation Platform & Virtualization Management Editor Tivoli Usage & Accounting Manager Service Provider Portal & API TAMIT DB entry TAMIT apps TAMIT Consumer In-house IT IaaS Deployment Architect Transition Manager Operations Security & TSM backup agent Manager Risk Manager Customer Care Legend <cloud servicespecific artifact created> <devToolForExploit ing mgmt/runtime component> <runtime/mgmt platform component> Infrastructure Tivoli Storage Manager Security. job plans. WAS. Cognos. Windows. Filenet. Linux. SQL file.*Cloud Computing Reference Architecture (CC RA) – Product & tooling mapping (on-prem products) Cloud Service Provider Cloud Services Common Cloud Management Platform Golden master VM image (runtime) [see runtime] IBM Cloud Computing Reference Architecture Service Definition TSAM SD app Service Manager Business Manager Registration persisted in DB TSAM/TSRMinternal apps TSAM / Tivoli Service Request Manager SP Existing & 3rd party services. Rational Dev tools (for app artifacts). … Job files. Resiliency.

However. It is acknowledged that many real-world implementations won’t map exactly to the applied patterns described here – many will be in a “grey zone” in between.IBM Cloud Computing Reference Architecture Cloud service creation – Applied patterns overview  Walkthrough all 12 steps per applied pattern while describing implementation-specific decisions per step (incl. product selections) 1. WAS The applied patterns should serve as a guideline for anyone who wants to deliver IT capabilities as cloud services. the applied patterns serve as good guidelines and blueprints for these custom implementations There will be more applied patterns available in future versions of the RA    21 08/03/11 © 2011 IBM Corporation . “Enterprise”: 1. ISV • Example cloud service: “Desktop Cloud” 1.

IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security n o s D l a us er td in ha ct rS A 3a Performance & Scalability Virtualization Management Resiliency Metering. Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a CCMP implementation + Consumability Use Cases & Roles 22 08/03/11 © 2011 IBM Corporation 22 .

Data Administrator.. IT Administrator Consumer End User Facilities Manager Customer Support & Care 23 IT Administrator specialties: Storage Admin. Workload Administrator. Network Admin.. 08/03/11 © 2011 IBM Corporation 23 23 . Security Administrator Security & Risk Manager Operations Manager Operator.. Virtualization Admin. OS Admin. Cloud Education Specialist Cloud Service Creator may include may include Consumer Business Manager Service Integrator Service Manager Cloud Service Provider may act as Cloud Service Consumer Consumer Administrator Tenant Administrator.Cloud Computing User Roles V2 – IBM Cloud Computing Reference Architecture Applied as Actors of CC RA use cases Service Component Developer Offering Manager Service Composer Business Manager Customer Account Manager. Business Office Deployment Architect Transition Manager Cloud Service Consultant. Green IT Analyst.

Network Administrator. They ensure that the running service is well aligned with business and operational objectives and targets. from business support system to operational support system services. Service Setup  Provision service Service Runtime  Managing compliance with service’s Service Level Agreements (SLA)  Monitor third party supplier SLA  Detect service faults  Determine service impact (from infrastructure faults / degradation)  Prioritise problems based on network impact  Manage long and short term performance targets  Ensure alignment of business and operational support systems  Expert knowledge of the existing cloud infrastructure and good judgment of the impact of a new or changed solution on it  Proficient understanding of the particular service offering and its service instances  Expert automation knowledge  Proficient understanding of capacity/performance issues within and across systems Operations Manager. Deployment Architect. Business Manager.Example: Service Manager Main Goal    Services meet their quality objectives Get up-to-date information on service adoption in seconds not days Have meaningful. Cloud Service Creator Main Tasks of their day-to-day job Skills Working with which other roles ? 24 24 08/03/11 © 2011 IBM Corporation 24 . Customer Account Manager. fact based discussions on service quality with internal and external suppliers Main Responsibility The focus of a Service Manager is to enable the smoothest service flow possible between all systems. Operator. Green IT Analyst.IBM Cloud Computing Reference Architecture Detailed Role Description .

changes. Integrate Cloud & (non-) Cloud env. Creating & Managing Service Offerings. Creating & Managing Business Aspects • 38 use cases. along the cloud service life cycle Consultative Analysis. Administer secure access Create. Self-guided information & education Via F2F or Web Sales channel Enable customers for managed services Development & Test on the Cloud: Developing & testing applications. view. Manage capacity. information and resources Collaboration in the Cloud: Using social networking services and online collaboration tools Install & configure platform. update. Create. security.s Request & View usage & billing reports. Monitor infrastructure(s). grouped into 10 packages. modify. Anywhere’ access to applications. modify. events. delete users. delete user groups Request. delete service instances 25 08/03/11 © 2011 IBM Corporation 25 . using development tool instances Desktop on the Cloud: Making use of ‘Anytime.CC RA V2.0 Use Cases IBM Cloud Computing Reference Architecture Creating & Managing Service Offerings Defining the Scope.

Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a CCMP implementation + Consumability Non-functional requirements 26 08/03/11 © 2011 IBM Corporation 26 .IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security n o s D l a us er td in ha ct rS A 3a Performance & Scalability Virtualization Management Resiliency Metering.

27 08/03/11 © 2011 IBM Corporation 27 .IBM Cloud Computing Reference Architecture Non-functional requirements TWP: Scope & Purpose  Consolidate typical Cloud Computing Management Platform Non-Functional Requirements to illustrate the minimal set of non-functional requirements for building a Cloud Management Platform  Reference architecture NFRs can help practitioners collect requirements during any project requirements gathering phase  NFRs are key input to other TWPs including Component Model and Operation Model  NFRs are high level in nature. as such. they should be evaluated along with the lower level CC RA Operational Model to establish the optimum Infrastructure for deploying the proposed solution  Non-Functional requirements of a Cloud management platform are quality requirements or constraints of the platform that must be satisfied. These requirements address major operational and functional areas of the platform in order to ensure the robustness of the system.

IBM Cloud Computing Reference Architecture NFR Context Relationship with other TWP and Domains Architectural Domains and Technical Work Product Inputs* Cloud Delivery Models Metering/ Rating / Accounting Virtualization Management SaaS Performance& Scalability Hybrid Cloud Multi-tenancy Resiliency NF Rs PaaS NFRs IaaS 28 08/03/11 © 2011 IBM Corporation 28 .

IBM Cloud Computing Reference Architecture

Non-Functional Requirement TWP document contains the following detailed NFRs…
In version 2 of the NFR document we added NFRs from the following areas on top of the version 1:  Applied Pattern NFRs Added - IaaS - Public Cloud: +20 - IaaS - Private Cloud: +17 - PaaS: +15 - SaaS – Managed Service Desk: +16  Domain Specific NFRs Added - Performance and scalability: +14 - Multi-tenancy: +16 - Virtualization management: o Base virtualization: +12 o Network virtualization: +18 - Hybrid Cloud: +10 NFRs - Resiliency: +13 - Metering / Accounting: +24

29

08/03/11

© 2011 IBM Corporation

29

IBM Cloud Computing Reference Architecture
1 3 3b
Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process

Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation

2
Create cloud service and CCMP implementationspecific architecture overview

Define cloud service and CCMPimplementation details

Service Flows

+
Use Cases

Architecture Overview

Component Model

Operational Model

Security

n o s D l a us er td in ha ct rS A

3a
Performance & Scalability Virtualization Management Resiliency Metering, Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud”

+
Non-functional Requirements

Leverage guidance on specific technical areas as input for developing a CCMP implementation

+
Consumability

Consumability

30

08/03/11

© 2011 IBM Corporation

30

IBM Cloud Computing Reference Architecture

What makes a cloud solution consumable?
Consumability is a customer-centric term that describes the total customer experience with IBM products, solutions and services. Consumable solutions: Reduce total cost of ownership Improve time to value Market driver Attributes Reduce support and maintenance costs

Consumability framework

Key characteristics On-demand self-service Ubiquitous network access Location independent resource pooling Rapid elasticity Flexible pricing models Integration is critical Data Integration / Migration Process Integration UI Mashup Labor simplification drives efficiency Self Service Automation of Management Standardization of Workloads
31 31 03.08.11

Identify Easy to do business Evaluate Plan Acquire Positive first-use experience Configure Operate Rapidly integrates with existing environment Readily adapts to customer requirements Integrate Deploy Develop Customize Problem Mgmt Simplifies ownership and operation Admin & Maintain Fix & Upgrade

© 2011 IBM Corporation

31

Understanding the user roles. assess the solution. the next step is to identify key stakeholders whose feedback you need to gather © 2011 IBM Corporation 32 . Design Customer Feedback (Validation) Stakeholder Feedback • • 32 32 03. competitive. identify the consumability goals for a particular solution. and work towards closing gaps. and market data Understand key workloads for offering Cloud Service Provider Cloud Service Creator Cloud Service Consumer Map key end-to-end tasks Cloud User Roles Identify relevant consumability criteria Identify involved user roles Conduct consumability assessment and gap analysis Describing who is interacting with a cloud service at the different stages of the cloud life cycle Consumability Assessment Using the consumability framework that is modified specifically for cloud solutions.08.IBM Cloud Computing Reference Architecture Designing Consumable Cloud Solutions Gather customer.11 Getting ongoing feedback from stakeholders is essential for designing a consumable solution.

IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security n o s D l a us er td in ha ct rS A 3a Performance & Scalability Virtualization Management Resiliency Metering. Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a CCMP implementation + Consumability Architectural Principles & Overview 33 08/03/11 © 2011 IBM Corporation 33 .

based on an Eliminate-Standardize-Optimize approach 3. across I/P/S/BPaaS. Design for Cloud-Scale Efficiencies (“Efficiency Principle”): Design for cloud-scale efficiencies. and flexible sourcing.  Overarching objective of Driving down costs (¢/ServiceInstanceHour) and time-to-response by orders of magnitude 2. processes.  Support I/P/S/BPaaS cloud services in a generic fashion. Identify and Leverage Commonalities (“Economies-of-scale Principle”): Identify and leverage commonality in cloud service design. and technologies.  Maximum sharing of mgmt components.  Radical exploitation of high degree of standardization in cloud environments to reduce management costs. 1. when realizing cloud characteristics such as elasticity. Define and Manage Cloud Services generically along their Lifecycle (“Genericity Principle“): Define service templates and manage service instances generically along their lifecycle. self-service access.IBM Cloud Computing Reference Architecture Cloud Computing Reference Architecture: Architectural Principles An architectural principle is an overarching guideline or paradigm driving architectural decisions across the entire architecture process on a more granular level. and time-to-deliver/time-to-change metrics. infrastructure & infrastructure / platform cloud services across cloud services to reduce CapEx & OpEx and time-to-market 4. with a single management platform 34 08/03/11 © 2011 IBM Corporation 34 . Support Lean Service Management (“Lightweight Principle”): Support lean and lightweight service management policies.

IBM Cloud Computing Reference Architecture Cloud Computing Reference Architecture (CC RA) – Overview CC RA architecture overview diagram lays defines basic elements of any cloud service environment Three main roles: Cloud service consumer. Next level of drill-down defined for each architectural element Cloud Service Consumer Cloud Services Cloud Service Provider Common Cloud Management Platform (CCMP) Cloud Service Creator Existing & 3rd party services. CCMP is typically implemented by a wellintegrated set of mgmt products Consumer In-house IT Inf rastructure-as-a-Service Inf rastructure Security. Performance & Consumability Governance 35 08/03/11 © 2011 IBM Corporation 35 . Partner Ecosystems Cloud Service Integration Tools Business-Processas-a-Service Sof tware-as-a-Service Operational Support Services (OSS) Platf orm-as-a-Service Business Support Services (BSS) Service Creation Tools CCMP is one element of the overall cloud computing reference architecture Defines operational and business support services commonly needed for delivering and managing any cloud service (I/P/S/BPaaS) Doesn’t imply a single. required Management services (CCMP) and underlying infrastructure are defined. provider and creator whereas multiple roles can be fulfilled by the same organization/person Offered cloud services. monolithic implementation of a CCMP. Resiliency.

it’s possible to use hypervisor-level virtualization to realize PaaS. which can include operating systems and applications.Net). etc. network. May 14. and possibly select networking components (e. NIST1 PaaS The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created applications using programming languages and tools supported by the provider (e. . self-service provisioning. network.g.IBM Cloud Computing Reference Architecture Cloud service model definitions Term Term Definition Definition Source Source Business process services are any business process (horizontal or vertical) delivered through the Cloud IBM2 service model (Multi-tenant. and other fundamental computing resources where the consumer is able to deploy and run arbitrary software. operating systems. servers. storage. load balancers). For example.g. or storage […]”. The BPaaS provider is responsible for the related business function(s). python. elastic scaling and usage metering or pricing) via the Internet with access via Web-centric interfaces and exploiting Web-oriented cloud architecture. networks. storage.. servers. in PaaS “the consumer does not manage or control the underlying cloud infrastructure. storage. The consumer does not manage or control the underlying cloud infrastructure. NIST1 IaaS The capability provided to the consumer is to rent processing. with the possible exception of limited user-specific application configuration settings. it is not about the virtualization technology being used. deployed applications. 36 36 National Institute of Standards and Technologies.. 2. Draft NIST Working Definition of Cloud Computing. operating systems.g. java. For example. 1. BPaaS SaaS The capability provided to the consumer is to use the provider's applications running on a cloud infrastructure and accessible from various client devices through a thin client interface such as a Web browser (e. web-based email). but the consumer has control over the deployed applications and possibly application hosting environment configurations. servers. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems. So this essentially about the tasks the operations staff of the provider takes on.. 2009 IBM MI and IPR definition bridge between Gartner and IDC. 2010 08/03/11 © 2011 IBM Corporation . or even individual application capabilities. firewalls. in IaaS “the consumer does not manage or control the underlying cloud infrastructure […]”. or storage. operating systems. NIST1 Note: Across all cloud service models the definition is determined by the management scope covered by the provider. The consumer does not manage or control the underlying cloud infrastructure. SaaS or BPaaS. Aug 19.. network.

Resiliency. build and manage images for cloud services Virtualized Resource Management •Deploy cloud services on virtualized resources •Manage virtual resources Deployment Architect Transition Manager Operations Manager Security & Risk Manager Customer Care Inf rastructure Security. integrity. Performance & Consumability Security Governance •Design for Multi-Tenancy •Protect assets through Isolation. highlighting some important topics  CCMP defines all management functions commonly needed for the automated delivery & management of any cloud service  Components are grouped in two major categories: Operational Support Services (OSS) and Business Support Services (BSS) – OSS: Responsible for managing the runtime components of cloud services – BSS: Responsible for all business / finance related aspects of cloud services  Economies of scale can be achieved by managing multiple cloud services with the same set of mgmt components (see architectural principles) 37 08/03/11 Cloud Service Consumer Cloud Services Cloud Service Provider Common Cloud Management Platform Creator •Flexible support of delivery models Service Manager Business Manager Usage Metering and Accounting Cloud Service •Interpret and Execute Existing &and Management Plans BuildServices 3rd p arty BPaaS services.risk and compliance management © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture Cloud Computing Reference Architecture Overview Diagram – CCMP drill-down. •Orchestrate Management Componentry Cloud Service Integration Tools Partner Ecosystems Service Automation Management Sup port OSS – Operational Service Delivery Catalog BSS – Busin ess Sup port Services Customer Account Management Service Offering Catalog Service Offering Management I P A & l a t r o P t n e m p o l e v e D e c i v r e S Service Automation Management I A & l a t P m u s n o C c i v r e S SaaS Contracts & Agreement Management Service Request Management Order Management Service Request Management Change & Configuration Management Incident & Problem Management IT Asset & License Management Image Lifecycle Management IT Service Level Management Capacity & Performance Management Subscription Management Pricing Entitlement Management Provisioning Service Creation Tools PaaS Monitoring & Event Management Metering Rating Billing Consumer In-house IT IaaS Platform & Virtualization Management Clearing & Settlement Accounts Payable Accounts Receivable Image Management Service Provider Portal & API •Design. image.

Partner Ecosystems BPaaS P B s c a f r et tm ng IM OSS – Operational Support Services Service Delivery Catalog BSS – Business Support Services Customer Account Management Service Offering Catalog Service Offering Management I P A Service Composer I P A & l a t r o P t n e m p o l e v e D e c i v r e S Service Automation Management I A & l a t P m u s n o C c i v r e S m ga M ef rr ae w tt fn oI S s c Service Integrator SaaS Contracts & Ag reement Management Service Request Management Order Management Offering Manager I P A Service Request Management Change & Configuration Management Incident & Problem Management IT Asset & License Management Image Lifecycle Management IT Service Level Management Capacity & Performance Management Subscription Management Pricing Entitlement Management Consumer Business Manager Service Creation Tools Service Management Development Tools Provisioning I P A Business Processes Applications Middleware Infrastructure g M m re o ft tn a lI P s c a f r Consumer Inhouse IT PaaS Monitoring & Event Management Metering Rating Billing Platform & Virtualization Management Clearing & Settlement Accounts Payable Accounts Receivable Service Runtime Development Tools Software Development Tools e c u t s a s c a fr rf e n In tI m g M Consumer Administrator t n e m e g a n a M e c i v r e S I P A IaaS Service Provider Portal & API Deployment Architect Transition Manager Operations Manager Security & Risk Manager Customer Care Image Creation Tools Inf rastructure Security.IBM Cloud Computing Reference Architecture Cloud Computing Reference Architecture (CC RA) – Overall drill-down Cloud Service Consumer Cloud Services Consumer End user Cloud Service Provider Common Cloud Management Platform Service Manager Business Manager Cloud Service Creator Service Component Developer Cloud Service Integration Tools Existing & 3rd party services. Resiliency. Performance & Consumability 38 08/03/11 Governance © 2011 IBM Corporation .

IBM Cloud Computing Reference Architecture Cloud Computing Reference Architecture (CC RA) – Security. Performance & Consumability drill-down Cloud Service Consumer Cloud Services Existing & party services. Performance & Consumability 39 08/03/11 Governance © 2011 IBM Corporation . Resiliency. Partner Ecosystems 3 rd Business-Processas-a-Service Cloud Service Provider Common Cloud Management Platform Cloud Service Creator Cloud Service Integration Tools Software-as-a-Service Platform-as-a-Service Consumer In-house IT Infrastructure-as-a-Service Operational Support Services (OSS) Business Support Services (BSS) Service Creation Tools Infrastructure Security Security Event Management Security Policy Threat & Vulnerability Management Software. System & Service Assurance Data and Information Protection Access & Identity Lifecycle Management Resiliency Data Resiliency Configuration for Resiliency Resiliency Monitoring / Analysis Resiliency Compliance Assessment Resiliency Policy Management Availability & Continuity Management Consumability Ease of Doing Business Positive First Use Experience Rapidly Integrates Readily Adapts Simplified Operations Governance Data policy enforcem ent Security Entitlem ent Security. Resiliency.

IBM Cloud Computing Reference Architecture Cloud Computing Reference Architecture (CC RA) – Infrastructure drill-down Cloud Service Consumer Cloud Services Existing & party services. Performance & Consumability 40 08/03/11 Governance © 2011 IBM Corporation . Partner Ecosystems 3rd Cloud Service Provider Common Cloud Management Platform Cloud Service Creator Business-Processas-a-Service Software-as-a-Service Cloud Service Integration Tools Operational Support Services (OSS) Platform-as-a-Service Business Support Services (BSS) Infrastructure-as-a-Service Service Creation Tools Inf rastructure Consumer In-house IT Server Processor Storage Drives Network Internal Facilities Location Memory Ephemeral External Power Nodes Persistent Inter-site Security. Resiliency.

2. The diagram and related descriptions have been used to lead the high-level discussion and to guide decisions on scope for release 1 and following. An architecture overview diagram pattern for a private enterprise where traditional IT is managed in parallel to a private cloud environment. A service provider consumption and value-add architecture overview diagram pattern (i. Applied patterns reflect common scenarios of how a cloud could be implemented: 1.e. IBM Shared Private Production Cloud 41 08/03/11 © 2011 IBM Corporation 41 .. plus the consumption of externally provided public cloud services 4. IBM Smart Business Development and Test on the IBM Cloud is a sample for a "simple" (public) service provider architecture pattern. composing them and adding service provider specific value-add functionality on top) 6. a service provider consuming cloud services from another cloud service provider and reselling the same offering -. 3. Bio-Informatics Exchange 7. A service provider "whitelabeling" architecture overview diagram pattern (i.n cloud services from other cloud services.with different branding and different prices) 5.e. service provider consuming 1.IBM Cloud Computing Reference Architecture Architecture Overview: Applied patterns  Applied Patterns are based on cloud projects where the reference architecture AOD has been used to create cloud implementations. IBM Cloud Service Provider Platform 8. The RA overview diagram has be used to discuss roles and responsibilities for a Desktop cloud project where part of the infrastructure is managed by IBM.

IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security n o s D l a us er td in ha ct rS A 3a Performance & Scalability Virtualization Management Resiliency Metering. Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a CCMP implementation + Consumability Component Model 42 08/03/11 © 2011 IBM Corporation 42 .

0 Component Model  Condensed mapping of CC RA 2.0: Component Model Primary focus on BSS and OSS  BSS and OSS component specifications and toplevel decomposition  Use Case realizations of important use cases (e.g.0 components with IBM recommended tools 43 08/03/11 © 2011 IBM Corporation 43 . Requesting Service Instances)  Extensive UML-based modeling of BSS and OSS component relationships and dependencies  Cross-component view on CC RA 2.IBM Cloud Computing Reference Architecture CC RA 2.0 domains  Mapping of current IBM cloud implementations to CC RA 2.

IBM Cloud Computing Reference Architecture Use Case Realizations A use-case realization describes how a particular use case is realized within the design model.Create Rating Scheme .Requesting Service Instance  Sequence diagrams help to understand components.Creating Service Offering incl. relationships and dependencies 44 08/03/11 © 2011 IBM Corporation 44 . processes and flows involved in realization of use cases  Detailed component diagrams are included to provide information about component interfaces. . in terms of collaborating objects (IRUP).  CC RA 2.0 CM describes realization of typical use cases: .Create Service Template .

Performance & Consumability TSA MP TSA AM TSM 45 08/03/11 Governance © 2011 IBM Corporation . Partner Ecosystems OSS – Operational Support Services Service Delivery Catalog TSRM BSS – Business Support Services Customer Account Management TSRM SPE Service Offering Catalog TSRM SPE Service Offering Management TSRM SPE Service Development Portal & API BP Mgmt Interfaces API BPaaS Service Composer Service Automation Management TSAM TSRM SPE CCMDB TPM TADDM Incident & IT Service Problem Level Managemen Managemen TSLA t t TSRM TNSQM TSRM SPE TSRM SPE Service Consumer Portal & API Service Integrator Offering Manager Software Mgmt Interfaces API SaaS Consumer Business Manager Platform Mgmt Interfaces API TSRM Provisioning TPM TSRM SPE TSRM SPE TSRM SPE Service Creation Tools Service Management Development Tools Consumer Inhouse IT Business Processes Applications Middleware Infrastructure Service Management PaaS ITM. ITNM.IBM Cloud Computing Reference Architecture IBM recommended products for consuming management functionality as on-premise installations Cloud Service Provider Cloud Services Consumer End user Common Cloud Management Platform TSRM SPE Service Manager Business Manager Service Component Developer Cloud Service Integration Tools Existing & 3rd party services. TBSM TAMIT TSRM SPE TUAM TSRM SPE TUAM TSRM SPE Platform & Virtualization Management Infrastructure Mgmt Interfaces VMControl TPC Service Provider Portal & API Service Runtime Development Tools Software Development Tools Security & Risk Manager Customer Care API IaaS Deployment Architect Transition Manager Operations Manager Image Creation Tools Consumer Administrator Infrastructure TAM TDS TFIM Security. Resiliency. OMNIbus.

Resiliency.IBM Cloud Computing Reference Architecture IBM recommended tools for consuming management functionality as a hosted offering Cloud Service Provider Cloud Services Consumer End user Common Cloud Management Platform OSS – Operational Support Services Service Delivery Catalog Tivoli Live Service Manager Service Manager Business Manager Service Component Developer Cloud Service Integration Tools Existing & 3rd party services. Performance & Consumability 46 08/03/11 BCRS Governance © 2011 IBM Corporation . Partner Ecosystems BSS – Business Support Services Customer Account Management Service Offering Catalog Service Offering Management Service Development Portal & API BP Mgmt Interfaces API BPaaS Service Composer Service Automation Management Service Consumer Portal & API Service Integrator Offering Manager Software Mgmt Interfaces API SaaS Consumer Business Manager Platform Mgmt Interfaces API Tivoli Live Service Manager Provisioning Incident & IT Service Problem Level Managemen Managemen Tivoli Live t t Service Manager Service Creation Tools Service Management Development Tools Consumer Inhouse IT Business Processes Applications Middleware Infrastructure Service Management PaaS Tivoli Live Tivoli Live Service Manager Platform & Virtualization Management Infrastructure Mgmt Interfaces Service Runtime Development Tools Software Development Tools Security & Risk Manager Customer Care API IaaS Service Provider Portal & API Deployment Architect Transition Manager Operations Manager Image Creation Tools Consumer Administrator Infrastructure Security.

Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a CCMP implementation + Consumability Operational Model 47 08/03/11 © 2011 IBM Corporation 47 .IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security n o s D l a us er td in ha ct rS A 3a Performance & Scalability Virtualization Management Resiliency Metering.

SBDTC)  RSA models for each level of elaboration which can be leveraged by adopters  System walkthroughs for major functional areas in Use Case Model and Component Model  Implementation guidance on realizing CC RA using IBM recommended tools identified in Component Model  Identify critical decision points and requirements used to guide the implementation 48 08/03/11 © 2011 IBM Corporation 48 .0: Operational Model Updates Primary focus on leveraging existing cloud implementations in IBM and other CC RA work products  Show how components are to be realized and deployed in a cloud-specific fashion  Harvest architectural patterns from existing cloud implementations (e.g.IBM Cloud Computing Reference Architecture CC RA 2.

noting important considerations specific to Cloud  Walkthroughs show how the component operates in the context of the CCMP 49 © 2011 IBM Corporation 49 .IBM Cloud Computing Reference Architecture The Operational Model emphasizes how a Cloud deployment differs  Adopter guidance on key decision points related to Cloud  Addresses each node and component realization specifically.

IBM Cloud Computing Reference Architecture Operational Model includes guidance for adopters to enable application to engagements  Implementation guidance includes: – Applied patterns showing how CC RA can be adapted to engagement-specific requirements – Recommended tool selection aligned with component mappings in the Component Model – Identification of architectural decisions and considerations of which practitioners need to be aware 50 © 2011 IBM Corporation 50 .

IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security n o s D l a us er td in ha ct rS A 3a Performance & Scalability Virtualization Management Resiliency Metering. Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a CCMP implementation + Consumability Service Flows 51 08/03/11 © 2011 IBM Corporation 51 .

 Service flows depend on service management components as defined in the CC RA component model – CCMP components are required for automating as many tasks as possible. – These service flows are focused on reducing labor costs for management to a minimum. by building on high degree of standardization present in any cloud environment.IBM Cloud Computing Reference Architecture CC RA –Service Flows TWP: Scope & Purpose  Defines all operational processes (“service flows”) required for managing cloud services based on a CCMP deployment. 52 08/03/11 © 2011 IBM Corporation 52 .

standardization. Monitoring Performance and Capacity Mgmt Service Level Management / Metering Service Request Management Continuity Mgmt © 2011 IBM Corporation 53 53 .IBM Cloud Computing Reference Architecture CC RA Service Flows Content: Overview Service flows processes differences from standard IT management processes • Leverages reduced (eliminate) scope of management. and opportunity for optimization to dramatically reduce labor costs. • Aimed at delivering cloud management processes for cost-competitive cloud infrastructures Manual as-is process Automated to-be process • Implementation of cloud-optimized service management processes • • • • • • • 53 08/03/11 Configuration and Asset Mgmt Patch / Provisioning / Image Mgmt Incident / Problem Mgmt.

IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security n o s D l a us er td in ha ct rS A 3a Performance & Scalability Virtualization Management Resiliency Metering. Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a CCMP implementation + Consumability Standards 54 08/03/11 © 2011 IBM Corporation 54 .

APIs BSS UI Portal Cloud Domain Model and Terminology Cloud Management & Orchestration (Service Consumability Templates) Management Standards Security Virtualization (OVF.0 Standards Conte By means of adhering to and driving the xt evolution of standards we ease adoption of our platform.. 08/03/11 © 2011 IBM Corporation 55 55 . avoid vendor lock-in.IBM Cloud Computing Reference Architecture Context and Scope of CC RA 2. and enable an ecosystem of partners around our platform. recognized as having authoritative value. assure solution portability. Images Mgmt. and which an organization chooses to implement as a basis for 'good practice'. Network. that is measurable. Storage) Scop • Existing Cloud Computing and Management e Standards • Standards that are currently being defined • Standards that need to be defined (recommended standards) 1 2 3 3 5 1 1 1 4 6 2 1 1 6 1 8 7 8 8 4 1 4 1 5 6 7 8 A standard can be defined as something with a pre-described specification.

0 Standards – Core Domain Model Overview 56 © 2011 IBM Corporation 56 .IBM Cloud Computing Reference Architecture CC RA 2.

and their touch points to specific disciplines – Do not dive into specific domains to avoid duplication of work  Strong focus on (1) defining core concepts/terms and (2) defining how those concepts are related to each other  Collect input from RA 1..0 documents.0 and RA 2.0  Make consistent with models that are defined or are being defined in IBM (e. CDM) Security Roles Hybrid Cloud Core Concepts BSS .g.0 Standards – Cloud Domain Model  Create a central. authoritative domain model and terminology to be used consistently in cloud solutions  Cover core concepts that are common across cloud solutions. Virtualization 57 08/03/11 © 2011 IBM Corporation 57 ..IBM Cloud Computing Reference Architecture CC RA 2. and make consistent with RA 2.

IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security n o s D l a us er td in ha ct rS A 3a Performance & Scalability Virtualization Management Resiliency Metering. Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a CCMP implementation + Consumability Architectural Decisions 58 08/03/11 © 2011 IBM Corporation 58 .

ensure that the architecture is extensible and can support an evolving system 59 08/03/11 © 2011 IBM Corporation 59 . the provision and allocation of function. the contextual fitness of the system and adherence to standards  Consolidate ADs from key offerings.preserve design integrity in the provision of functionality and its allocation to system components .avoid unnecessary reconsideration of the same issues .IBM Cloud Computing Reference Architecture Architectural Decisions TWP: Introduction & Purpose  AD documents important decisions about any aspect of the architecture including the structure of the system. architectural domains and TWPs to provide a single place to find important ADs that illustrate rationale and justification of architectural decisions  Develop standard reusable artefacts that can be consumed by offering and engagement architects  Prove a reference of documented decisions that can help practitioners to: .

IBM Cloud Computing Reference Architecture Scope Context .Capture ADs from key cloud offerings and architectural domains & TWPs Architectural Domain Subset* Technical Work Products Cloud Delivery Models Use Cases & Roles SaaS Managed Service Desk Architecture Overview PaaS Security Component Model Operational Model IaaS (Public & private cloud) Standards Non Functional Requirements Service Flows 60 08/03/11 © 2011 IBM Corporation 60 .

Hybrid Cloud – 7 ADs .Metering / Accounting – 4 ADs .IaaS .IaaS .SaaS – Managed Service Desk – 11 ADs  Domain specific Ads .Performance and scalability – 5 ADs 61 08/03/11 © 2011 IBM Corporation 61 .Virtualization management – 17 ADs .IBM Cloud Computing Reference Architecture Architectural Decision TWP Word Document Contains the following detailed ADs… In version 2 of the AD document we added decisions from the following areas on top of the decisions from version 1:  Applied Pattern Architecture Decisions .Public Cloud – 14 ADs .Private Cloud – 18 ADs .Resiliency – 1 AD .

Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a CCMP implementation + Consumability Security 62 08/03/11 © 2011 IBM Corporation 62 .IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security n o s D l a us er td in ha ct rS A 3a Performance & Scalability Virtualization Management Resiliency Metering.

Security by default 3. The top layer is the IBM Top and Control the Security Risk and Compliance Physical Asset Management Management Assessment Security Framework. Access and Security Policy Service Management Event Infrastructure Certificate Infrastructure Infrastructure middle and bottom layer Entitlement Infrastructure respectively. mechanisms and software components Architectural Principles Foundational Security Management Software. Compliance (GRC) People and Identity IT Infrastructure: Network. Access and Entitlement Management Data and Information Protection Management Threat and Vulnerability Management IT Service Management . Server. Security Services and Infrastructure the management of The blueprint separates security from the Info and implementation of security. Multiple levels of protection 10. Consistency in approaches. whichCrypto. System and Service Assurance Identity. Risk. Design for regulations 5. The framework is commonly represented by the graphic you see on the right. Keyrepresented in the are and Security Identity. the IT organization can focus on getting the policy and needed controls correctly defined and can better monitor and assess how completely and effectively the policies are being enforced. Design for sharing 8. End Point Data and Information Application and Process Physical Infrastructure This diagram is the CommandLevel view ofPolicy blueprint. which provides the business context Management or business perspective of security. Openness 2. and technical controls that can be deployed into the IT landscape and the organization. Infrastructure A product-agnostic and solution-agnostic approach to defining security capabilities. Security is model-driven 12. Separation of management. Design for privacy 6. Architecture Principles in the Blueprint 1. Security-critical resources must be aware of their security context 13. The Services and Infrastructures layer represents the security capabilities needed to enforce policies and their integration points into the IT infrastructure. Design for extensibility 7.IBM Cloud Computing Reference Architecture IBM Security Framework: Business Security Reference Model Governance. Design for accountability 4. Design for consumability 9. operational procedures. enforcement and accountability 11. Identities and Events and Code and Policies Attributes Logs Images A common vocabulary to use in more detailed discussions Data Repositories Security Service Levels and Classification Config Operational IT Security Architectural principles that Designs valid Info and are across Context domains and deployment all Registry Knowledge environments 63 08/03/11 © 2011 IBM Corporation Based on researching many customer related scenarios A roadmap to assist in designing and deploying security solutions Storage Security Host and End-point Security Application Security Network Security Physical Security The security management layer represents the capabilities needed to translate the business view of security concerns into policies. By separating security management from security implementation.

Only by combining foundational controls with activity/data specific controls can organizations meet their cloud security needs.IBM Cloud Computing Reference Architecture Activity/Data Driven Cloud Security Organizations need to adopt a strategy for cloud security that considers the unique attributes of the cloud as well as the activities and data the cloud is being utilized for. 64 08/03/11 © 2011 IBM Corporation 64 .

IBM Cloud Computing Reference Architecture 1 Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview 3 Define cloud service and CCMPimplementation details 3b Service Flows Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process + Use Cases Architecture Overview Component Model Operational Model Security n o s D l a us er td in ha ct rS A 3a Performance & Scalability Virtualization Management Resiliency Metering. Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a CCMP implementation + Consumability Performance & Scalability 65 08/03/11 © 2011 IBM Corporation 65 .

and Goals Measurement methods and Metrics of Service Levels Roadmaps from Tivoli. Linux Technology Center (STG).IBM Cloud Computing Reference Architecture Performance & Scalability WG: Scope Performance and scalability relevant Scenarios & Use Cases Diga e nn s d Sino izgf C Pa C bs Me d ahetu r itcr c e Architecture/ Operational Patterns for Performance and Scalability Consumable outcomes Performance and scalability service level KPIs. and SoNAS (STG) 66 08/03/11 © 2011 IBM Corporation 66 .

CoR. Storage. Facilities © 2011 IBM Corporation 67 . and Pre-fetching 67 – Pre-create/hibernate/resume VM 67 08/03/11 Virtualized Infrastructure – Server.IBM Cloud Computing Reference Architecture Architectural Patterns Initial focus on these CCMP Components Common Cloud Management Platform BSS Business Support System  Deployment patterns for OSS components – Multiple Virtualization Management domains – Horizontal Scaling of Provisioning components – Horizontal Scaling of Service Automation components – Multiple OSS domains Service Delivery Catalog OSS Operational Support System Service Templates Service Request Management Provisioning Service Automation Management  High Scale Low Touch Virtualization Management Virtualization Mgmt  Patterns and strategies for rapid provisioning – CoW boot disk of remote read-only images – Local caching of remote images and CoW root disk of local read-only image – Local caching of remote images and only transferring image delta – Use a combination of CoW. Network.

3 Horizontal scaling of Service Automation components – 3.2 Functions – 4.3 Results – 4.4 Measurements & metrics  3 Deployment patterns for CCMP OSS components – 3.2 Influencing Scenarios and Factors – 2.2 Local caching of remote images and CoW root disk of local read-only image – 5. and Pre-fetching – 5.2 Horizontal scaling of Provisioning components – 3.4 Use a combination of CoW.1 CoW boot disk of remote readonly images – 5.1 Use Cases and Actors – 2.1 Scope of this document – 1. Use Cases.2 Supporting work products & references – 1.5 Pre-create/hibernate/resume VM  6 Applied Pattern: Compute Cloud  7 References © 2011 IBM Corporation 68 . KPIs.1 Architecture – 4.3 Key Performance Indicators and Goals – 2.IBM Cloud Computing Reference Architecture Outline of the WP document  1 Introduction – 1.3 Legal Remark  2 Scenarios. CoR.3 Local caching of remote images and only transferring image delta – 5.1 Multiple Virtualization Management domains – 3.4 Targeted scenarios and use cases  5 Virtual systems rapid provisioning strategies – 5.4 Multiple OSS domains 68 08/03/11  4 High Scale Low Touch virtualization management – 4. and Measurements – 2.

Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a CCMP implementation + Consumability Virtualization Management – Base 69 08/03/11 © 2011 IBM Corporation 69 .IBM Cloud Computing Reference Architecture 1 Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview 3 Define cloud service and CCMPimplementation details 3b Service Flows Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process + Use Cases Architecture Overview Component Model Operational Model Security n o s D l a us er td in ha ct rS A 3a Performance & Scalability Virtualization Management Resiliency Metering.

scaling and architecture decisions – Ex: local storage vs shared storage the implications there wrt Performance. mobility. pros and cons – Performance.IBM Cloud Computing Reference Architecture Virtualization Management . placement.Base  Component of the OSS layer – provides common interface across hetergenous infrastucture & value-add functions above infrastructure (pooling. Partner Ecosystems BSS – Business Support Services Custom er Account Management Service Offering Catalog Service Offering Management BPaaS Service Delivery Catalog I P A & l a t r o P t n e m p o l e v e D e c i v r e S Service Automation Management I A & l a t P m u s n o C c i v r e S SaaS Contracts & Agreement Management Service Request Management Order Management Service Request Management Change & Configuration Management Incident & Problem Management IT Asset & License Management Image Lifecycle Management IT Service Level Management Capacity & Performance Management Subscription Management Pricing Entitlement Management Provisioning PaaS Monitoring & Event Management Metering Rating Billing Platform & Virtualization Management Clearing & Settlement Accounts Payable Accounts Receivable IaaS Deployment Architect Transition Manager Service Provider Portal & API Operations Manager Sec urity & Risk Manager Inf rastructure © 2011 IBM Corporation 70 . notification up)  Defines the capabilities and services for the management of virtual resources and the underlying physical resources  Base virtualization divided into 2 main sub components – Platform Management – Virtual Resource Management  Network and Storage Virtualization are sub teams and discussed separately Cloud Service Provider  Details what functions/subcomponents should be part of the Virtualization/Platform Management component – Definition of scope and functions  What is important for implementation/options in cloud environments for these functions – Considerations and what options are there. resiliency of the VMs  What standards/recommendations are there for implementations 70 08/03/11 Cloud Services Common Cloud Management Platform OSS – Operational Support Services Service Manager Business Manager Existing & 3rd party services. scaling.

and patching of system firmware and hypervisor software. reporting. predicted failure. Network and Storage infrastructure • Virtualization management component handles placement/allocation across the pool and optimization of the pool. – Bare Metal installation/distribution • Install and distribute OS and hypervisor software and agents – Platform health monitoring and reporting • Monitors health of physical systems and hypervisors • Used for billing services and SLAs 71 08/03/11 © 2011 IBM Corporation 71 . restart virtual servers – Relocation • Provides ability to move a virtual resource from one physical machine to another • May happen as a result of a failure. including ability to capture images – Management of virtual servers • Provides interface to start. stop. or planned maintenance  Platform Management – Discovery of physical resources • Library or catalog of discovered resources • Inventory such as options.IBM Cloud Computing Reference Architecture Virtualization and Platform Management  Virtualization Management – Virtualization Platform Abstraction • Common interface to request and access virtual resources • Enables commonality for the higher level functions in the BSS and OSS layers – Virtual Resource Pooling • Ability to manage a set of virtualization infrastructure as a single entity or “pool” • Includes Compute. availability. licensing. firmware. • Resource allocation can be based on a variety of criteria and factors such as energy. OS – Platform Software Maintenance • Monitoring. may include over commit of physical resources – Instance Image Management • Provides management of deployed instances of the images. etc – Reservation • Reserves virtual resources for future use • Provides a reservation interface – Image Repository • Library of virtual appliances which can be deployed to create workloads – Deployment and Undeployment • Creation and deletion of virtual systems and network/storage resources at the request of the provisioning layer • Provides for intelligent allocation across the pool.

VSAE  Non-Functional Requirements – Mostly centers around performance and scaling which is critical in a cloud environment – Details Documented in the NFR document  Input provided to other work products for performance. Cloudburst. SNMP – Virtualization management • DMTF OVF • Libvirt • Activation engine . Telco scenario 72 08/03/11 © 2011 IBM Corporation 72 . resiliency. component model. etc  Applied Patterns – Private cloud.IBM Cloud Computing Reference Architecture Virtualization and Platform Management  Standards – Platform management • DMTF CIM.

IBM Cloud Computing Reference Architecture 1 Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview 3 Define cloud service and CCMPimplementation details 3b Service Flows Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process + Use Cases Architecture Overview Component Model Operational Model Security n o s D l a us er td in ha ct rS A 3a Performance & Scalability Virtualization Management Resiliency Metering. Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a CCMP implementation + Consumability Virtualization Management – Networking 73 08/03/11 © 2011 IBM Corporation 73 .

g.Leverage work from ITM.  Identify/define resources in resource model (i.e. – Private cloud to cloud virtual network (including hybrid cloud – from customer’s network to cloud). critical for supporting cloud networking as part of infrastructure authoritative topology DB. …) Competitors (HP. etc. Cisco FabricPath. Director.IBM Cloud Computing Reference Architecture Virtualization Management – Networking Summary  Identify BSS/OSS core components that are relevant to cloud (virtual) networking. matching capabilities for physical networks . CIM).  Identify a set of important cloud networking connectivity types (and patterns) to support cloud users (customers): – Shared cloud infrastructure network(s). We need to develop comprehensive capability for managing virtual networks. – Capability extensions for virtual networking architecture and services. These are the focus of several startups. 74 08/03/11 © 2011 IBM Corporation Virtualization driving changes in network infrastructure.. Hybrid Clouds and CSP Clouds have additional requirements for scaling. Solarwinds) . creating new opportunities for network management Network requirements for virtualization and cloud are similar. – Private networks w/in cloud infrastructure (with variation of access over Internet). especially for Enterprise/private clouds. -Lead in supporting optimization of new data center networks (e. TRILL. concurrent updates.

75 08/03/11 © 2011 IBM Corporation Virtualization driving changes in network infrastructure. …) Competitors (HP. etc.g.IBM Cloud Computing Reference Architecture Virtualization Management – Networking TWP Summary  Define subcomponents (and their expected capabilities) and services of Networking Virtualization Management in Virtualization and Platform Management overall component. matching capabilities for physical networks . concurrent updates. Cisco FabricPath. TRILL. We need to develop comprehensive capability for managing virtual networks. -Lead in supporting optimization of new data center networks (e.  Identify Architecture Decisions and NonFunctional Requirements related to networking..  Relate cloud networking to on-going standard work in DMTF SVPC WG for virtual networking within OVF.Leverage work from ITM.e.  Identify IBM products/assets that provide foundations for building out support for cloud networking and automated network provisioning. especially for Enterprise/private clouds. creating new opportunities for network management Network requirements for virtualization and cloud are similar.  Extend cloud use cases to include networking connectivity (i. Director. Hybrid Clouds and CSP Clouds have additional requirements for scaling. connecting cloud services to virtual networks and automated network provisioning). Solarwinds) . These are the focus of several startups.

Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a CCMP implementation + Consumability Resiliency 76 08/03/11 © 2011 IBM Corporation 76 .IBM Cloud Computing Reference Architecture 1 Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview 3 Define cloud service and CCMPimplementation details 3b Service Flows Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process + Use Cases Architecture Overview Component Model Operational Model Security n o s D l a us er td in ha ct rS A 3a Performance & Scalability Virtualization Management Resiliency Metering.

IBM Cloud Computing Reference Architecture CC RA 2.0 Resiliency  Defined cloud Resilience architecture  Based on lessons learned from implementations  Mapped architecture to proposed CCMP resilience implementation  Identified required products  NFRs enhancements Key learning from existing cloud implementations  OSS/BSS interdependencies and operational requirements must be considered in coordinated resilience and automation design 77 08/03/11 © 2011 IBM Corporation .0 Resiliency CC RA 2.

IBM Cloud Computing Reference Architecture 1 Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview 3 Define cloud service and CCMPimplementation details 3b Service Flows Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process + Use Cases Architecture Overview Component Model Operational Model Security n o s D l a us er td in ha ct rS A 3a Performance & Scalability Virtualization Management Resiliency Metering. Rating and Accounting 78 08/03/11 © 2011 IBM Corporation 78 . Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a CCMP implementation + Consumability Metering.

Rating and Accounting Domain addresses: – Different types of metered usage data (3 Key types) and the need to meter both Allocated and Activity based data – BSS-OSS mapping of runtime and design time data flows – Product specific detailed functional gap analysis with tool recommendations – Solution architecture along with implementation guidance  3 Applied Patterns from architecture as applicable to Public.IBM Cloud Computing Reference Architecture Metering. Rating & Accounting: Executive Summary  Metering. Private clouds and an ISV context are explained 79 08/03/11 © 2011 IBM Corporation 79 .

 Action Usage – Actions initiated by the consumer that the provider may wish to charge for or track costs against • e. Websphere Cluster) has been allocated to a particular cloud service. change virtual server configuration – Action may or may not involve manual steps 80 08/03/11 © 2011 IBM Corporation 80 . Database. Network. CPUSecs. CPUs. Backup/restore server. Bytes transferred etc – More suitable as Cost Usage Metric.g. the time period IT infrastructure topology (e. – More suitable as Service Usage Metric.g. Storage.IBM Cloud Computing Reference Architecture Terminology: Metered Usage Data Concepts  Allocation Usage – The result of a consumer occupying a resource such that other consumers cannot use it – For example. Memory.  Activity Usage – The result of activity performed by the consumer e. Servers.g.

600 Profit Cloud Service Requestor #3 Service B 2 CPUs on Server 1 1 GB 100 server hrs @ $20/ server hr 200 CPU hrs @ $3/ CPU hr 100 GB hrs @ $2/ GB hr 100 DB2 Support hr @ $2/ DB2 Support hr Cloud Service Provider Service A revenue = $5.40/min Server 1 software usage = 80 hrs * $15/hr Server 1 labor costs = $40 DB2 Help Desk = $50 Service B revenue = $3. To determine if the service is Profit or Loss 2.60/min Server 1 software usage = 60 hrs * $15/hr Cloud Service Requestor #2 Service A 3 CPUs on Server 2 4 GB 50 server hrs @ 25/ server hr 150 CPU hrs @ $5/ CPU hr 200 GB hrs @ $3/ GB hr $3.40/min Server 2 CPU usage = 2.100 Service A costs $4. To Maximize Cloud Utilization 3.290 Loss 81 08/03/11 Cost and prices are for illustration purposes only © 2011 IBM Corporation 1.500 CPU mins * $.000 CPU mins * $.000 CPU mins * $.060 Server 2 software usage = 40 hrs * $10/hr Server 1 labor costs = $40 Server 2 labor costs = $60 Service A costs ==$4.IBM Cloud Computing Reference Architecture Cloud Delivery Requires Allocation and Activity Usage Cloud Service Requestor #1 Service A 4 CPUs on Server 1 2 GB 60 server hrs @ $25/ server hr 240 CPU hrs @ $5/ CPU hr 120 GB hrs @ $3/ GB hr Allocation Usage Service A Costs Activity Usage Cloud Service Provider Server 1 CPU usage = 3.660 Service B Costs Server 1 CPU usage = 5.100 $2.000 Service B costs = $3. Network bandwidth type service metrics require to measure usage 81 .

Action(Labor) Local context Data Correlation & Aggregation Rules (each source) Metrics Definition Metered Usage Data Generation Instrumented Service Management System 82 08/03/11 Manages Instrumented Service Hosting System © 2011 IBM Corporation 82 . Activity.IBM Cloud Computing Reference Architecture Metering Rating & Accounting: BSS – OSS Mapping BSS Cost/Price Accounting Usage Accounting Usage Reports Billing Records Adjustment Tax Rules Billing Terms Billing Record Generation Rated Usage Reports Contracts & Agreements Rates /Prices Provider’s Rating & Accounting of Usage Accounting Records Qualified Usage Accounting Records Business context Accounting Structures Qualified Usage Accounting Records Generation OSS Correlated Usage Records Service context Usage Data Qualification Rules Correlation & Aggregation Rules (Service) Metered Usage Data Correlation Metered Usage Data: Allocation.

Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a CCMP implementation + Consumability BSS Decomposition 83 08/03/11 © 2011 IBM Corporation 83 .IBM Cloud Computing Reference Architecture 1 Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview 3 Define cloud service and CCMPimplementation details 3b Service Flows Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process + Use Cases Architecture Overview Component Model Operational Model Security n o s D l a us er td in ha ct rS A 3a Performance & Scalability Virtualization Management Resiliency Metering.

IBM Cloud Computing Reference Architecture Business Support Services Decomposition  Business Support Services (BSS) is a set of components that enables interaction of customers with the service provider. BSS and OSS functions for all IBM Cloud services are provided by the Common Cloud Management Platform (CCMP)  BSS Decomposition RA content . which is a set of computer systems and related processes used to deliver the services. BSS works closely with Operational Support Services (OSS).44-page doc with the following sections: – BSS positioning within CCMP – Overview of BSS functions required for all realizations – Public Cloud realization – Private Cloud realization – Brief discussion of hybrid cloud and product development realizations – Future direction – BSS as a Service for promoting re-use and modularization 84 08/03/11 © 2011 IBM Corporation 84 .

0 conceptual CM for Business Support Services Security & Compliance management Customer Account mgmt Customer Account mgmt Customer information mgmt Customer information mgmt User identity mgmt User identity mgmt User access mgmt User access mgmt Customer Management Contracts & agreements mgmt Contracts agreements mgmt Register contract/agreement Billing Schedule Register Billing Schedule Contracted Rating Contracted Rating Contract generation Contract generation BSS – Business Support Services 08/03/11 Service Offering Management Service Offering Management Offering Lifecylce mgmt Offering Lifecylce mgmt Options configuration & rule mgmt Options configuration rule Service Offering management Service Offering Catalog Service Offering Catalog List prices List prices Discount Discount Pricing Pricing Price information mgmt Price information mgmt Price model Price model Service Development Portal Service Consumer Portal 85 Service Service Request mgmt Request mgmt Subscription Subscription mgmt mgmt Metering Metering Subscription Management Entitlement mgmt Entitlement mgmt Entitlement tracking Entitlement tracking Order management Order management Enter & manage order Delivery status monitoring Enter & manage order Delivery status monitoring Manage license/Entitlement Manage license/Entitlement Clearing & settlement Clearing & settlement Royalty mgmt // payment Royalty mgmt payment ISV // Vendor payment ISV Vendor payment Financial Management Accounts Payable Accounts Payable Accounts Receivable Accounts Receivable Rating Rating Billing Billing Financial data release Financial data release Process billing charges Create & release invoice Process billing charges Create & release invoice Service Provider Portal © 2011 IBM Corporation .IBM Cloud Computing Reference Architecture CCMP RA 2.

services costs. TSRM tracks labor. tools.using Tivoli Service Request Manager – Service Provider Edition + Tivoli Usage and Accounting Manager TSRM-SP provides all these functions Notes on METERING TSRM provides Allocation & Activity-based Metering.IBM Cloud Computing Reference Architecture Private Cloud Realization . materials. TUAM provides Usage-based Metering RATING & BILLING TSRM & TUAM provide partial rating functions & bill data generation – but not direct invoicing 86 08/03/11 NO Peering and Settlement NO accounts payable/receiving © 2011 IBM Corporation 86 .

Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a CCMP implementation + Consumability Hybrid Cloud 87 08/03/11 © 2011 IBM Corporation 87 .IBM Cloud Computing Reference Architecture 1 Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview 3 Define cloud service and CCMPimplementation details 3b Service Flows Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process + Use Cases Architecture Overview Component Model Operational Model Security n o s D l a us er td in ha ct rS A 3a Performance & Scalability Virtualization Management Resiliency Metering.

provisioning. Enable on-premise monitoring and event infrastructure to reach into clouds  Perspectives – Operating Perspective: Seamlessly move – Sourcing Perspective: Different types of peek workloads from on-premise to public Cloud – Management: Manage Capacity in the cloud. – Management Perspective: Unified view and capability to manage resources and information onpremise and in off-premise Clouds combined with management and integration of workloads and resources across hybrid cloud – Governance: Who can. how to ensure proper security of off-premise cloud workload. and management  Dimensions: – Integration: How to connect on-premise services and data to off-premise counterparts… business data mapping and service integration – Patterns: Identify solution patterns for integration of on-premise with services in public cloud(s) – Life-cycle: Identify and define workload migration and life cycle events for services in hybrid cloud – Roles: Identify roles associated with hybrid cloud operations and services – Decisions: Define architectural decisions for hybrid cloud integration framework and for hybrid cloud management services – Security: How to integrate on-premise/offpremise identities. policies. security. performance.IBM Cloud Computing Reference Architecture Hybrid Cloud Workstream: Scope and Dimensions  Scope and Purpose: – Use Cases: Identify use cases and scenarios for hybrid cloud setup. How to secure management and payload interactions – Monitoring: Integrate monitoring of off-premise infrastructure and applications with on-premise management system. availability. capacity overflow from onpremise to Cloud workloads to be provisioned by the most effective Cloud from the perspective of cost.and off-premise resources 88 08/03/11 © 2011 IBM Corporation 88 88 . does. operations. auditing systems. should use which cloud-based services…service request management of on. etc. functionality.and de-provisioning based on Monitoring data).

Workload Management and capacity overflow from CCMP based private Cloud to IBM Compute Cloud ERP Data DB2 Hybrid Cloud Integration Query Access Replication Examples: Security: Directory Integration & Identity Federation Example Synchronize on premise ODW LDAP and LotusLive Domino directory info and facilitate SSO Cognos Apps DB2 Staging DB Cognos BI SIB Staging DB Cognos and other Analytic Applications in the Cloud: Initial Load to Cloud.IBM Cloud Computing Reference Architecture Hybrid Cloud: Use Case Scenarios Examples: Examples: Hybrid Cloud Integration Connect off-premise monitoring events to on-premise monitoring system IBM Cloud Hybrid Cloud Integration Database Sync customer records Tivoli Monitoring Server Hybrid Monitoring Example Federate Monitoring info of Workload in IBM Public Cloud Examples: On-premise to off-premise Business Application Integration: Example: On-premise Database to Salesforce Cloud Examples: Private (On Premise Resources) Common Cloud Manageme nt Platform Hybrid Cloud Integration Mgmt and Capacity Overflow of/to Public Cloud Common Cloud Manage mentPlat form Public Cloud Resources (IBM Cloud) Hybrid Cloud Integration LDAP Directory Sync on-premise identity model and directory Governance & Hybrid Workload Management Examples: Governance for acquiring Resources from IBM Compute Cloud and/or Amazon. Data Cleansing 89 08/03/11 © 2011 IBM Corporation 89 89 . Query Access. Change Data Capture Replication to & from Cloud.

Security and Policy Enforcement Cloud Service Broker Private Cloud IBM Development & Test Cloud 3rd Party Cloud Services © 2011 IBM Corporation 90 90 .Cloud Management Platform * IBM Cloud Computing Reference Architecture – Hybrid Cloud Model Common Cloud Management Platform BSS Business Support Services Offering Mgmt Order Mgmt Accounting & Billing Contract Mgmt Customer Mgmt Entitlements Invoicing SLA Reporting Metering. Analytics & Reporting Pricing & Rating Subscriber Mgmt Peering & Settlement Service Offering Catalog Service Development Portal Hybrid Cloud Integration: Client Controlled from within the enterprise 90 90 08/03/11 Service Delivery Portal OSS Operational Support Services Service Templates Service Request Management Provisioning Monitoring & Event Management Service Delivery Catalog Updated for Hybrid Cloud API Service Automation Management Configuration Mgmt Incident. Problem & Change Management IT Asset & License Management Virtualization Mgmt Image Lifecycle Management IT Service Level Management Capacity & Performance Management Monitoring. Metering.

Rating and Accounting BSS De-composition Hybrid Cloud Multi-tenancy “Production cloud” + Non-functional Requirements Leverage guidance on specific technical areas as input for developing a CCMP implementation + Consumability Multi-tenancy 91 91 08/03/11 © 2011 IBM Corporation 91 .IBM Cloud Computing Reference Architecture 1 3 3b Leverage architectural decisions documented in the RA and make implementationspecific ones throughout the entire process Define requirements and use implementation guidance for cloud service and CCMP implementation Cloud Service Creation 2 Create cloud service and CCMP implementationspecific architecture overview Define cloud service and CCMPimplementation details Service Flows + Use Cases Architecture Overview Component Model Operational Model Security n o s D l a us er td in ha ct rS A 3a Performance & Scalability Virtualization Management Resiliency Metering.

IBM Cloud Computing Reference Architecture Multi-tenancy .scope Multi-tenancy requirements and customer expectations Don e Partia l Requirements mapping to CC RA component for impact and gap analysis Multi-tenant patterns Leveraging existing multi-tenancy assets and capabilities Specification of how secure Multi-Tenancy should be implemented across the CC RA components 92 08/03/11 © 2011 IBM Corporation 92 .

IBM Cloud Computing Reference Architecture Multi-tenancy deliverables Multi tenant NFRS Use Cases and extensions Component impact analysis Multi-tenancy definition Tenant definition Multi-tenant patterns whitepaper adopted NFR deliverable Use case deliverable Component deliverable adopted adopted 93 93 08/03/11 © 2011 IBM Corporation 93 .

in fact. 94 08/03/11 © 2011 IBM Corporation 94 . while. using physically shared resources.IBM Cloud Computing Reference Architecture Multi-tenant definition Multi-tenancy refers to the ability of services to be offered to multiple user entities (tenants) in a way so that each tenant operates as logically isolated.

The Cloud service instance requested by the Service Owner 1:n Service Resources The resources consumed by the service Application Platforms Virtual Machine Storage Network component 95 95 08/03/11 © 2011 IBM Corporation 95 . A role within the business entity that will request commission and decommission services from the Cloud.IBM Cloud Computing Reference Architecture Tenant definition 1 Tenant 1 1 Consumer Business Manager 1:n 1 1:n Consumer Administrator 1 1:n Consumer End User 1:n 1 Service Instance 1 A role within the business entity that manages contracts and optionally approves commission of services from the Cloud The users of the Service A business entity that is contractually responsible for the consumption of Cloud Service from a service provider.

Primitive set of patterns of multitenancy 2. OS OS OS OS Operating System Operating System Operating System Infrastr.IBM Cloud Computing Reference Architecture Multi-tenancy whitepaper Multitenancy service considerations Standardisation Security risk Cost/tenant Low Low High Tenant Tenant Tenant Tenant Tenant Tenant Tenant Tenant Tenant High High Low Tenant App App App App App App App App Application Platform Platform Platform Platform Platform Platform Platform Platform 1. Infrastr. Multi-tenancy of managing and manage environments 4. 3. Multi-tenancy needs of public and private clouds. Associated multi-tenant characteristics that will have to be supported in any Cloud implementation. Infrastructure Data center floor Infrastructure Data center floor Infrastructure Data center floor Infrastructure Data center floor Data center floor I Physical-level multi-tenancy Legend: Dedicated Shared II Hypervisor-level multi-tenancy III Operating System-level multi-tenancy IV Platform-level multi-tenancy 96 08/03/11 © 2011 IBM Corporation 96 .

Sign up to vote on this title
UsefulNot useful