IBM Cloud Computing & Common Cloud Management Platform - IAAS

Birgit Schmidt-Wesche, Brian Snitzer, Gerd Breiter, Gerhard Widmayer, Jim Whitmore, Julissa Villareal, Michael Behrendt, 

Rich Caponigro, Rong Chang, Stefan Pappe, Tim Weinmann, Xavier Chotteau (in alphabetic order) 

IBM Cloud Computing & 

Common Cloud Management Platform 

Reference Architecture (CC & CCMP RA) 1.0 

© 2010 IBM Corporation

IBM Cloud Computing & Common Cloud Management Platform Reference Architecture (CC & CCMP RA) 1.0 

2 

Table of Contents 

§ Introduction & Overview 

§ Cloud Computing & 

Common Cloud Management Platform Reference Architecture Details 

– Architectural Principles 

– Roles & Use Cases 

– Non-Functional Requirements 

– Architecture Overview Diagram – CC & CCMP RA 

– CCMP Exploitability 

– Security 

– Component Model 

– Operational Model 

– Service Flows 

– Architectural Decisions 

§ Outlook 

§ References 



Cloud Computing & Common Cloud Management Platform Reference 

Architecture: Overview 

3 

What is an RA? 

A Reference Architecture (RA) provides a blueprint of a to-be-model with a well-defined scope, requirements it 

satisfies, and architectural decisions it realizes. By delivering best practices in a standardized, methodical way, an 

RA ensures consistency and quality across development and delivery projects. It consists of a set of formal 

Unified Method Framework models, defining requirements, functional and operational aspects. 

What is the IBM Cloud Computing Reference Architecture? 

It is a modular cross-IBM framework allowing to understand how different elements in a cloud environment relate 

to each other. It also allows to drill-down on each element (e.g. CCMP) making up the CC RA 

What is the Common Cloud Management 

Platform Reference Architecture – CCMP RA? 

It is a cross-IBM effort for an RA enabling cloud 

economics by optimizing resource and labor 

utilization, and delivering the foundational cloud 

management infrastructure for both 

private and public clouds. 

The CC & CCMP RA served as the basis for: 

• CCMP implementation for “the IBM cloud” 

• IBM Smart Business Development and Test on the IBM cloud 

• IBM Smart Business Development and Test Cloud and 

its resulting private cloud customer projects 

• Test Cloud reference implementation as 

created by the Cloud Center of Excellence 

• …and many more 



CCMP RA – Target Audiences 

4 

Confidential Content 

1. IBM cloud development and operations teams 

– Teams involved in planning, implementing, operating, etc. 

• IBM CCMP implementation 

• Cloud services exploiting CCMP 

– Access to _all_ CCMP RA information 

2. “Other” IBM-internal groups: 

– IBM field people, implementing clouds for customers 

• GTS / GBS / SWG services practitioners implementing private or public clouds for IBM customers 

– IBM internal account working on IBM-internal clouds 

– IBM SW & HW product development teams to understand how their respective product offerings can fit into the 

overall CCMP context 

– IBM market intelligence teams using the CC & CCMP Reference Architecture as a basis for comparing different 

cloud offerings 

– Access to most parts of CCMP RA, but not to “IBM secret sauce” relevant as differentiators for IBM public cloud 

offerings 

3. IBM-external parties 

– Anyone outside of IBM 

– CCMP RA can be used as guideline / blueprint by practitioners implementing clouds for IBM customers. The 

resulting implementation architecture can be passed to the customer, but not the RA by itself 

– The complete CCMP RA as-is will not be published externally, but this presentation and a planned high-level 

overview whitepaper are distributable. 

Public Content 



5 

CCMP Reference Architecture Summary 



The IBM Cloud Computing & Common Cloud Management Platform 

Reference Architecture – Aggregating past, present and future 

Refinement 

(“Improve the CCMP RA content presently 

available”) 

• Continuous improvement of CCMP 

RA content based on feedback from 

CCMP RA exploiters & stakeholder 

• Introduction of new work products 

as needed, such as ITD-relevant 

ones. 

6 

CC & CCMP RA 

= 

Forward looking 

+ + 

(“What are future topics relevant for 

CCMP”) 

• Establish principles and guidance 

in new areas addressing future 

requirements for CCMP. 

• Examples are: 

• generalization of CCMP 

services 

• layered cloud services 

• NFRs, e.g. high availability 

• Hybrid clouds 

Harvesting 

(“Learning from cloud deployments in the 

past?”) 

• Harvest material from CCMP 

implementation, while factoring out 

short cuts taken by implementation 

team (e.g. due to constrained time 

lines). Based on learnings from on 

implementation experience 

• Execute harvesting activities/tasks 

as part of each wave's development 

plans so the work is 

viewed/executed as mainstream to 

the project, not an after the fact 

activity. 



Common Cloud Management Platform Reference Architecture – 

Overall Approach 

7 

Input 

Use Use cases cases 

Use cases 

(representing functional 

requirements 

Non-functional 


Non-functional Requirements 

Requirements 

Requirements 

Use cases and NFRs from: 

• Cloud Client Engagements 

• Computing On Demand 

• Desktop Cloud 

• Developer Cloud 

• ITD 

• LotusLive 

• Research Compute Cloud 

• Test Cloud 

• Virtual Storage Cloud 

… 

• Application of cloudspecific 

architectural 

principles 

• Make architectural 

decisions 


Reference Architecture 

Normalized, common definitions based on input from Cloud efforts 

Requirements input for all other work products 

Use cases 

(represent functional 

requirements) 

Architectural 

Decisions 

Architecture 

Overview 

Diagram 

Service 

Flows 

Component Model 

Operational Model 


Requirements 

Security 

Architecture 

• Each technical work product (TWP) is a word document 

as defined in the Unified Method Framework (UMF) 

• All CCMP RA TWPs should be used as guidance and a 

blueprint for actual CCMP implementations 



CCMP RA – Content summary 

§ Use Cases: Defines CCMP-specific use cases for all roles defined in the CCMP RA. To be used by cloud 

service developers or CCMP implementation teams for defining their implementation-specific use cases. 

§ Non-functional requirements: Defines all non-functional requirements to be considered when creating a 

CCMP implementation or a cloud service on top of CCMP. Includes example values which can be used as 

guidelines. 

§ Architecture Overview Diagram (AOD): Provides overview of the fundamental architectural building 

blocks making up the CC & CCMP RA and introduces basic terminology. 

Also includes guidance on how to exploit CCMP for implementing cloud services. 

§ Architectural Principles: Defines architectural principles serving as a guideline in the definition of all 

other work products (part of architecture overview TWP). 

§ Component Model (CM): Constitutes the next-level-of-detail refinement of the architectural elements 

introduced in the AOD. Defines functional scope for each component and relationship to other 

components. 

§ Operational Model (OM): Constitutes the refinement of the CM towards a physical architecture which can 

be implemented as a real-world deployment. Defined on both logical and physical level. 

§ Security Architecture: Cross-cutting work product encompassing all security aspects relevant in the 

context of the CCMP RA. 

§ Service Flows: Defines processes of how a CCMP implementation must be operated to achieve cloudscale 

efficiencies. 

§ Architectural Decisions: All architectural decisions made across all work products. Very important to 

capture & convey expertise in building a CCMP implementation and enable revisiting decisions and to 

understand rationale in case they turn out to be non-optimal. 

8 



9 

Cloud Computing & Common Cloud Management 

Platform Reference Architecture Details 



10 

Architectural Principles 



11 

Traditional Data Center Management vs. 

“Cloud-like” Management 

The overall objective of Cloud-managed data centers is to automate any type of 

task or situation (by reducing manual intervention) for increasing flexibility and 

reducing operational expenses 

Core Metrics 

Core Disciplines 

IT Management approach 

Administration Tasks 

Problem handling 

Service Consumer Service Provider 

interaction 

Traditionally managed Data 

Center 

“Cloud-managed” data center 

Admin/Server ratio Costs 1:50 – 1:100 1:100’s – 1:1000’s 

Time to provide new service instances 

& changing them Flexibility 

Days / weeks Hours / minutes / seconds 

For Cloud-like efficiencies and 

flexibility, it is not sufficient to 

have the right technology, but 

to also use it in the right way! 



12 

Architectural Principles for 

Common Cloud Management Platform Reference Architecture 

An architectural principle is an overarching guideline or paradigm driving architectural 

decisions across the entire architecture process on a more granular level. 

1. Design for Cloud-Scale Efficiencies (“Efficiency Principle”): 

Design for cloud-scale efficiencies, and time-to-deliver/time-to-change metrics, when realizing cloud characteristics such 

as elasticity, self-service access, and flexible sourcing. 

Overarching objective of Driving down costs (¢/ServiceInstanceHour) and time-to-response by orders of magnitude 

2. Support Lean Service Management (“Lightweight Principle”): 

Support lean and lightweight service management policies, processes, and technologies. 

Radical exploitation of high degree of standardization in cloud environments to reduce management costs, based on 

an Eliminate-Standardize-Optimize approach 

3. Identify and Leverage Commonalities (“Economies-of-scale Principle”): 

Identify and leverage commonality in cloud service design. 

Maximum sharing of mgmt components, infrastructure & infrastructure / platform cloud services across cloud services 

to reduce CapEx & OpEx and time-to-market 

4. Define and Manage Cloud Services generically along their Lifecycle (“Genericity 

Principle“): 

Define service templates and manage service instances generically along their lifecycle, across I/P/S/BPaaS. 

Support I/P/S/BPaaS cloud services in a generic fashion, with a single management platform 

Details are available in CC & CCMP RA TWP: “Introduction, Architectural Principles, Policies, & Guidelines (ARC 309) 

and Architecture Overview (ART 0512)“ 



Service 

Subscription & 

Instantiation 

Service 

Offering 

Creation & 

Registration 

Service 

Template 

Definition 

13 

Lifecycle of a Cloud Service 

Service Catalog 

Manager 

Offering 

IBM / ISV / 

IT Dept 

Subscriber 

(e.g. Line of 

Business) 

Definition 

Subscription & 

Instantiation 

Cloud 

Service 

Cloud Management 

Platform 

Common Resource 

Pools 

Production 

Termination 

Administrator / 

SLM 

Subscriber 

(e.g. Line of 

Business) 

Service 

Operation 

Service 

Instance 

Termination 



14 

Roles & Use Cases 



Common Cloud Use cases & Roles TWP: 

Scope & Purpose 

§ Defines common set of roles present in any cloud computing environment 

§ Defines common set of use cases relevant for any cloud computing environment 

§ The common cloud use cases represent the functional requirements to be 

addressed in all other CCMP RA TWPs (except the NFR TWP). 

15 

For For CCMP CCMP RA RA Consumers: 

When When developing a specific CCMP CCMP implementation … 

--The The Common Cloud Cloud Roles Roles can can either either be be reused reused as-is as-is or or be be used used as as a 

framework to to define define specialized, implementation-specific roles roles 

--Some Some Common Cloud Cloud Use Use Cases Cases can can be be reused reused as-is; as-is; others others have have to to be be 

reused reused and and detailed out out in in the the context context of of the the respective CCMP CCMP implementation. 

All All use use cases cases relevant for for a specific CCMP CCMP implementation must must be be captured in in 

the the use use cases cases TWP TWP specific to to the the respective CCMP CCMP implementation. 



Cloud Computing Roles – Overview 

16 

Cloud Service Consumer Cloud Service Provider 

Consumer 

Business 

Manager 

§ Business / 

financial (e.g. 

approval) 

responsibility for 

consumed 

services 

§ Accounted for 

used services 

instances 

Consumer 

Administrator 

Consumer 

End User 

§ Uses service 

instances 

provided by 

service 

provider 

§ Requests service instances and 

changes of service instances (typically 

on behalf of Consumer Business 

Manager ) 

§ Provides access to services for 

service users 

may act as a 

Service 

Business Manager 

§ Offers all types of services (SPI) 

developed by service developer 

§ Accounts services consumers 

for services potentially offered by 

service provider themselves and 

services offered on behalf of 

service developer 

Service 

Operations Manager 

§ Manages 

technical 

infrastructure 

required for 

providing cloud 

services 

Details are available in CC & CCMP RA TWP: “Common Use Cases (ART 0510)“ 

may include 

Service Providers offer services based on a 

management infrastructure. They may also develop 

services. 

Service Providers can build their services by 

(optionally) consuming services provided by other 

service providers. 

Service Providers can host services developed by other 

service developers (on top of their own services) 

Service 

Transition Manager 

Service 

Security Manager 

§ Responsible for enabling a 

consumer to use the cloud service, 

incl. boarding, integration, and 

process adoption 

Cloud Service Developer 

§ Responsible for 

ensuring that the Service 

Provider appropriately 

manages risks associated 

with development, 

delivery, support and use 

of services 

§ Designs, implements, and 

maintains service templates 

(technical aspect) 

Role + Use Case 

Definitions 

leveraged for DMTF 

Cloud Incubator 



Common Cloud Use Cases 

17 

Consultative Analysis; 

Self-guided information 

& education 

Desktop Cloud: 

Using virtual desktop 

resources 

Developer Cloud: 

Developing 

Applications, using 

dev. tool instances 

Test Cloud: 

Testing 

applications 

Virtual Storage Cloud: 

Storing and retrieving 

information 

… 

Details are available in CC & CCMP RA TWP: “Common 

Use Cases (ART 0510)“ 

Via F2F; Business portal; 

Web-based registration 

& ordering process 

Installing & 

configuring 

platform; Managing 

service templates, 

capacity, changes, 

events; Monitoring 


Viewing 

usage & 

billing 

reports; 

Managing 

service 

contract; 

Admin. of 

user / groups 

Enabling customers for 

managed services, 

ensuring steady-state 

access to resources 

Creating service 

templates; 

Creating 

supporting simple 

or composite 

images 

Initiating service instances; Making changes to service instances; 

Approving / rejecting service instance requests; 

Decommissioning service instances 



CCMP RA: Use case details 

§ CCMP RA Use case TWP describes 28 Use cases. 

§ The CCMP RA use cases are split into two categories: 

– “Concrete” use cases, which are independent of the cloud service exploiting CCMP 

• Examples: “Administering Cloud Management Platform”, “Creating Service 

Offerings”, “Support”, … 

18 

– “Abstract” use cases, which apply generically to any cloud service, but have to be 

specified in the context of the respective cloud service. 

• Examples: 

- “Requesting Service instances” would be specified to “Requesting virtual machine” 

in a compute cloud context, “Requesting file set” in a storage cloud context, 

“Requesting Web conference” in a LotusLive context. 

- “Updating existing service instances” would for example be specified to “change 

CPU/Mem capacity of a virtual machine” in a compute cloud context, “Change file set 

capacity” in a storage cloud context, “Change max. number of web conference 

participants” in a LotusLive context 



19 

Non-Functional Requirements 



CCMP RA – Non-functional requirements TWP: 


§ Defines all non-functional requirements to be considered for the development of a 

CCMP implementation. 

§ Includes cloud-specific example values for each NFR, which can be used as a 

guideline for CCMP implementation teams. 

§ Represents the non-functional requirements to be addressed in all other CCMP 

RA TWPs (except the use cases TWP). 

20 



--Implementation-specific Implementation-specific values values must must be be specified in in the the NFR NFR TWP TWP specific to to 

the the respective CCMP CCMP implementation. 

The The NFRs NFRsto to be be taken taken into into account are are defined defined in in the the CCMP CCMP RA RA NFR NFR TWP, TWP, incl. incl. 

example values values providing guidance. 



The Non-Functional Requirements technical work product gives an idea of the new 

Cloud Computing stakes and challenges, for example ... 

§ Internationalization / Globalization: Basic support requirements address the fundamental 

need of consumers to use Cloud solutions to operate their business in their local language 

and locale. For example, we need to allow them to enter data, such as customer names and 

addresses, dates, and currency into their systems in their local language/locale. 

§ RAS (Reliability, Availability, Serviceability): By definition, a Cloud Management Platform 

must be resilient to failure and to change. The architecture must assume that individual 

components will fail and that their failure must not compromise the availability of the Cloud 

service. This will require a level of built-in redundancy, self-correction, first-failure data 

capture, ‘hot-plug’ capabilities, and isolation/quarantine mechanisms. Taking advantage of 

virtualization and Virtualized System Pools allows the cloud service provider to provide 

advanced RAS characteristics by changing the approach to the problem. 

§ Classes of service: Individual service instances will probably have different classes of 

service depending on the service level agreements between the cloud service consumer and 

the cloud service provider. 

§ Manageability: For the Cloud Service Consumer, they expect their Service Level 

Agreements to be enforced. They also require the ability to easily create, use, manage, and 

potentially retire their service instances. The cloud infrastructure must provide management 

services sufficient to enable the service level agreements. In order to achieve this, no part of 

the architecture is managed as a stand-alone entity. All parts of the architecture must 

participate in an overall Management Stack infrastructure. 

… 

21 



The Common Cloud Management Platform NFR work product addresses the Non- 

Functional Requirements of the Cloud managing environment 

A. The NFR TWP defines, in the context of CCM: 

§ User Experience requirements 

– Consumability 

– Integration/Embeddability 

– Internationalization/Globalization 

– Accessibility 

– Usability 

§ Constraints 

– Physical 

– Network 

§ Green requirements 

– Energy / Facilities 

§ Extensibility/Flexibility reqs. 

§ Standards, Legal & Compliance reqs. 

§ RAS requirements 

– Reliability, Availability, Serviceability 

– Backup and Recovery 

– Disaster Recovery 

– Failure Management 

§ Performance requirements 

– Response Time 

– Capacity Estimates and Planning 

– Scalability (scale-out, scale-up) 

§ Security & Data Privacy reqs. 

§ Portability requirements 

§ Manageability requirements 

§ SLA management requiremets 

22 

B. Each NFR is illustrated 

with the choices made for 

IBM Cloud offerings 

C. Typical metrics are provided per NFR for SLA mgt purposes: 



23 

Architecture Overview Diagram 



Cloud Computing & CCMP Reference Architecture – Overview & Approach 

1. As part of the CCMP RA effort, also the foundational & guiding Cloud Computing 

Reference Architecture (CC RA) was defined. 

2. The IBM Cloud Computing Reference Architecture (CC RA) is structured in a 

modular fashion (similar to the SOA Reference Model) 

24 

– On its highest level of abstraction, it defines a base set of architectural 

elements, which are refined to the next level of detail 

– This modular approach allows refinement of the CC RA architectural 

elements independent from each other by the respective SMEs. 

3. The IBM Common Cloud Management Platform Reference Architecture (CCMP RA) 

is the reference architecture for the CCMP being one fundamental architectural 

elements of the IBM CC RA. 

There are several more areas defined within the CC RA (e.g. virtualized infrastructure, 

I/P/S/BPaaS, service development tools, hybrid clouds, etc.). Each of them should be 

addressed by a similar architectural effort as the CCMP RA does for the CCMP aspects. 

Details are available in CC & CCMP RA TWP: “Introduction, Architectural Principles, Policies, & Guidelines (ARC 309) 

and Architecture Overview (ART 0512)“ 



CC & CCMP RA – Architecture Overview Diagram: 


§ Define the fundamental architectural building blocks making up the Cloud Computing 

Reference Architecture and introduce basic terminology. 

25 

– Define roles relevant for any Cloud Computing environment (Cloud Service 

Consumer/Provider/Developer) 

– Define fundamental architectural elements required per role 

• Cloud Service Consumer: Cloud Service Integration Tools & Consumer In-house IT 

• Cloud Service Provider: CCMP (OSS, BSS, UI), (Virtualized) Infrastructure, Cloud 

Services 

• Cloud Service Developer: Cloud Service Development Tools 

For 

§ Define 

For CCMP CCMP RA 

detailed 

RA Consumers: 

architectural 

Consumers: 

elements for CCMP (OSS, BSS, UI) and fundamental 

When 

architectural When developing developing a 

approach a specific specific CCMP 

for implementing CCMP implementation implementation … 

a CCMP … 

--Use Use the 

– Constitutes the CC CC & CCMP 

the CCMP RA 

basis RA Architecture 

for Architecture Overview 

more fine-grained, Overview to 

component to get get clarity clarity on 

level on which 

definition which CCMP CCMP components 

of CCMP components 

to to implement implement first, 

elements as first, how 

part how to 

of CCMP to realize realize the 

RA the (virtualized) 

Component (virtualized) infrastructure 

Model infrastructure and and which which cloud cloud service service to to 

offer. offer. 

--Use Use the the CC CC & CCMP CCMP RA RA Architecture Architecture Overview Overview to to position position all all elements elements of of your your cloud cloud 

implementation. 




26 

Cloud Computing Reference Architecture (CC RA) – Overview 

Cloud Service 

Consumer 


Integration 

Tools 

Consumer 

In-house IT 

Cloud Service Provider 

Cloud Services 

IT capability provided to Cloud Service Consumer 

(Virtualized) Infrastructure – Server, Storage, Network, Facilities 

Infrastructure for hosting Cloud Services and Common Cloud Management Platform 


BSS – Business Support Services 

Business-level functionality for management of Cloud Services 

OSS – Operational Support Services 

Operational-level functionality for management of Cloud Services 

Security & Resiliency 


Developer 

Service 

Development 

Tools 



27 

CC RA – CCMP Details 


Consumer 

Consumer 

End user 


Integration 

Tools 

Consumer 

Business 

Manager 

Consumer 

In-house IT 

Consumer 

Administrator 



Service Delivery Portal 

API 

BSS 

Business 

Support 

Services 

OSS 

Operational 

Support 

Services 





Offering Mgmt 

Order Mgmt 

General accounting 

Service Templates 

Service Request Management 

Provisioning 

Monitoring & 

Event Management 

Customer Mgmt 

Entitlement Mgmt 

Invoicing Billing 

Contract & agreement Mgmt Opportunity to Order 

Metering, Analytics & Reporting 

Service Delivery Catalog 

Service Automation Management 

Change & Configuration 

Management 

Incident & Problem 


IT Asset & License Management 

Virtualization Mgmt 

Service Provider Portal 

Image Lifecycle Management 

IT Service Level Management 

Capacity & 

Performance Management 

Service Business Manager Service Transition Manager Service Operations Manager 


Pricing & Rating 

Subscriber Mgmt 

Peering & Settlement 

Service Offering 

Catalog 

Service Security Manager 

Service Development Portal 


Developer 

Developer 

Service 

Development 

Tools 

Service Definition 

Tools 

Image Creation 

Tools 



28 

CC RA – CCMP Focus Areas 

Virtualized Resource Management 

– Deploy cloud services on 

virtualized resources 


Consumer 

Consumer 

End user 


Integration 

Tools 

Consumer 

Business 

Manager 

Consumer 

Administrator 


Provisioning 

Monitoring & 




Hybrid Cloud Management 

BSS 

Consumer 

In-house IT 

– Manage virtual resources 


API 

Business 

Support 

Services 

OSS 

Operational 

Support 

Services 

Offering Mgmt 

- Address Security, Monitoring, Order Mgmt 

Connectivity and Management General Aspects accounting 

in Hybrid Clouds 

Security 

– Design for Multi-Tenancy 






Customer Mgmt 



– Protect assets through Isolation, integrity, 

image- risk and compliance management 














Capacity & 





– Interpret and Execute Build- and 

Management Plans 

– Orchestrate Management Componentry 

Image Management 





Developer 

Developer 

– Design, Pricing & Rating build and manage images 

for Subscriber cloud Mgmt services 


Catalog 

Usage Metering and Accounting 

– Flexible support of delivery 

models 

Service 

Development 

Tools 

Service Definition 

Tools 

Image Creation 

Tools 



29 

CCMP RA – BSS Details 


Consumer 


Integration 

Tools 

Consumer 

In-house IT 



BSS 

Business 

Support 

Services 





Offering Mgmt 

Order Mgmt 


Customer Mgmt 











Catalog 


Developer 

Service 

Development 

Tools 



30 

CCMP RA – BSS Details 

Entitlement Management 


Consumer 

– Sets up Account Quota and limits 

– Roles and permissions 


Integration 

Tools 

Consumer 

In-house IT 







BSS 

Business 

Support 

Services 

Usage Metering and Accounting 

• Metered Data used for 

Chargeback and Billing 

• Data insights to ensure 

success of a Cloud service 

Offering Mgmt 

Order Mgmt 


Customer Mgmt 




Metering, Analytics and Reporting 




Subscriber Management 

– Customer On-boarding 





Catalog 


Developer 

– Enable services for consumption 

Services Catalog 

Service 

Development 

Tools 

– Publish list of offered services 

– Track services for effectiveness, 

includes retirement of un-used 

services 



31 

CCMP RA – OSS Details 


Consumer 


Integration 

Tools 

Consumer 

In-house IT 







OSS 

Operational 

Support 

Services 





Provisioning 

Monitoring & 













Capacity & 



Developer 

Service 

Development 

Tools 



32 

CCMP RA – Security & Resiliency Details 


Consumer 


Integration 

Tools 

Consumer 

In-house IT 












Command & Control Security Policy Mgmt Software, System & Service Assurance 

Data Policy Enforcement Identity Lifecycle Mgmt Threat & Vulnerability Mgmt 

Audit & Compliance Mgmt Access Mgmt 

Security 

Security extension to IT Service Mgmt 

Entitlement 

Compliance Officer Security Engineer Security Officer 

Availability & Continuity Mgmt 



Developer 

Service 

Development 

Tools 



33 

CC RA – Cloud Services Details 


Consumer 


Integration 

Tools 

Consumer 

In-house IT 


Services 

User Interface 

API 





Business-Process-as-a-Service 






Software-as-a-Service 

Platform-as-a-Service 

Infrastructure-as-a-Service 


Developer 

Service 

Development 

Tools 



34 

CC RA – Virtualized Infrastructure Details 


Consumer 


Integration 

Tools 

Customer 

In-house IT 






Server Storage Network Facilities 

Processor 

Memory 

Drives 

Ephemeral 

Nodes Persistent 


Internal 

External 

Inter-site 






Location 

Power 


Developer 

Service 

Development 

Tools 



CCMP automatically delivers and manages cloud services using any 

level of virtualization … 

§ Depending on nonfunctional 

requirements 

(isolation, performance, 

etc.) and technical 

constraints, cloud service 

implementers can choose 

from a variety of 

virtualization technologies 

§ CCMP can 

programmatically interface 

with virtualization 

technologies – from lowlevel 


virtualization up to 

application level 

virtualization 

35 

CCMP 

UI 

BSS 

OSS 

manages 

Application-level 

virtualization 

Platform-level virtualization 

OS-level virtualization 

Hypervisor-/Infrastructure 

level virtualization 

Virtualization options 

for Cloud service 

implementations 



Typical Cloud Management Platform Middleware Stack 

based on the CCMP RA (Integrated Service Delivery Manager) 

Workloads 

§ Service measurement 

§ Service reporting 

§ Usage accounting 

§ Auditing and controls 

Tivoli Service 

Automation 

Layer 

§ Automate process 

of instantiating and 

managing a 

distributed IT 

environment. 

Virtualized 

Infrastructure Layer 

§ Virtualized resources 

§ Virtualized aggregation 

§ Physical infrastructure 

36 

x86 

UCS 

Manager 

VM 

Tivoli 

Monitoring 

Web, Collaboration 

and Infrastructure 

Technology 

Highly Threaded 

Throughput-oriented 

Scale Out Capable 

Lower Quality of Service 

Cisco UCS 

VM Partition … 

Hypervisor 

(KVM, (vSphere) VMware, Xen) 

VM PArtition 

VM 

Storage Network 

(Vmax) 

TSAM v7.2 TUAM 

Web 2.0 


Analytics and 

High Performance 

Computing 

Technology 

Compute intensive 

High I/O Bandwidth 

High Memory Bandwidth 

Floating point 

Scale out Capable 

Service 

Request Mgr 

TADDM 

HMC NIM 

Service 

Automation 

Templates 

Transaction 

Processing 

and Database 

Technology 

Scale 

High Transaction Rates 

High Quality of Service 

Handle Peak Workloads 

Resiliency and Security 

Service 

Automation 

Mgr 

TPM 

Provisioning 

Mgr 

Tivoli Process Automation Engine 

Orchestration workflows 

System p / SUN 

Hypervisor 

(PowerVM) 

VM Partition 


VM Partition 

Image 

Library 

VM Control 

Business 

Applications 

Technology 

Scale 

High Quality of Service 

Large Memory Footprint 

Responsive Infrastructure 

Workflows 

HMC 

System z 

Hypervisor 

(zVM) 


Usage 

Reports 

Billing 

Reports 

VM Partition 

VM Partition 

© 2010 IBM Corporation 

End to End Service Management


IBM Cloud Service Provider Platform 

A comprehensive offering to create, deliver and manage cloud services 

37 

§ Unmatched scalability to launch 

and maintain tens of thousands of 

VM’s concurrently 

§ Heterogeneous virtualized 

infrastructure for flexible platform 

choices 

§ Secure multi-tenancy 

§ Workload mobility and 

recoverability for superior 

management 

More than just cloud provisioning – manages the cloud 

infrastructure AND what’s inside the cloud! 



Delivers carrier-grade scale you can trust 

Unmatched carrier-grade scalability and performance to deliver new 

services to market faster than anyone else 

38 

1 million+ 

Virtual machines 

running concurrently 


Core Service Automation Management 

The only solution with the flexibility and choice of network and 

storage options and the ability to span platform architectures 

39 

§ Multi-tenant service catalog 

§ Advanced image management 

§ Extendable via an open API 

§ Automated service provisioning 

§ Web 2.0 self-service portal 

§ Wizard-like service creation 

Visibility, Control and Automation across the service 

delivery and business infrastructure 



Integrated Service Provisioning, Monitoring & Metering 

Improve OPEX and CAPEX by leveraging standards and 

economies of scale 

40 

§ Automated service de-provisioning 

§ Improved standardization 

§ Integrated usage metering 

§ Extendable to in-house BSS 

§ Out-of-the-box monitoring 

§ 10 clicks to IaaS! 

§ Energy efficient hardware 

Deliver new services in days…. days not weeks or months 



41 

How to exploit CCMP for all management aspects of 




CCMP RA – CCMP Exploitability Guide (part of Architecture Overview TWP): 


§ Audience is teams developing cloud services (not CCMP development-related 

teams, as addressed by all other work products) 

§ Defines considerations to be made when implementing a cloud service 

(I/P/S/BPaaS), across CCMP exploitation, (virtualized) infrastructure and cloud 

service specific aspects. 

§ Defines how a cloud service can be implemented by exploiting CCMP 

functionality. 

42 



--the the CCMP CCMP Exploitation Guide Guide helps helps understanding how how elements of ofa a CCMP CCMP 

implementation should should be be exploited by by the the respective cloud cloud service. 

However, the the main main audience are are Cloud Cloud service service implementation teams, teams, not not CCMP CCMP 

implementation teams. 

teams. 



Exploitation of CCMP by Cloud Services 

43 

WebConfaaS 



Virtualized Infrastructure – Server, Storage, Network, Facilities 


API 


BSS 

Business 

Support 

System 

OSS 

Operational 

Support 

System 

BSS-aaS 

Offering Mgmt 

Order Mgmt 

Accounting & Billing 

Contract Mgmt 

Provisioning 

OSS-aaS 



Monitoring & 


WAS-aaS Virtual 

DesktopaaS 

Customer Mgmt 

Entitlements 

Invoicing 

SLA 

Reporting 




Configuration Mgmt 

Incident, Problem & 

Change Management 








Catalog 



Capacity & 




Cloud services used in diagram only for illustration purpose, not normative 

File 

systemaaS 

VM-aaS 



BSS 

OSS 

 

HW Infrastructure 

 

manages 

 

HW 


Each cloud service uses BSS and OSS 

functionality (besides cloud service-specific 

components), much of these functionalities is 

common across cloud services 

Sharing makes a lot of sense from a 

economies-of-scale / cost-sharing and increased 

time-to-market perspective 



Cloud Service – Basic structure / “Anatomy of a cloud service” 

For exposing cloud service 

specific information and 

functionality. 

For offering and selling any 

cloud service, BSS functionality 

is needed. Examples are 

offering management, pricing 

and billing. 

Any cloud service requires 

some level of OSS functionality 

such as service automation 

management, monitoring, 

metering, etc. 

44 

Cloud service specific 

management software 

UI aspects 

BSS aspects 

OSS aspects 

 

HW Infrastructure 

 

 

HW infrastructure 

All involved software components 

– OSS, BSS and cloud service 

specific software – require an 

infrastructure to run. Depending 

on scope and purpose this can be 

a virtualized or non-virtualized 

infrastructure, run within the cloud 

service provider’s data center or 

be purchased as IaaS. 

Cloud service specific software, 

.e.g. any type of runtime software 

on the managed environment, 

e.g. hypervisors as IaaS-specific 

software, middleware platform 

SW for a PaaS cloud service or a 

SaaS application. 



Areas of consideration for implementing cloud services 

Aspect to be considered 

What do I want to expose as a cloud service / what is my “unit of delivery & mgmt” and 

which (self-service) execution functionality? 

What is the scope of management (mgmt up to hypervisor, OS, MW, App) and the 

associated management processes? 

Which underlying provisioning functionality do I need for my cloud service? 

Which assets do I need to maintain (servers, storage, SW licenses, etc.)? 

Which configuration items are relevant for my cloud service? 

Which resources / metrics have to be monitored? 

Which metrics have to be collected historically? 

Which consumer model should be applied (single person, complex org, etc.) 

Which rates should be applied to the metered information? 

Which golden master images do I need? 

Which reports do I need internally & which reports should be exposed to my 

customers? 

Which cloud service-specific UI panels do I want to expose to service consumers? 

Which cloud service-specific runtime functionality do I need? 

45 

Affected CCMP component 

OSS / Service Automation 

All BSS/OSS components, focus on Service Automation 

OSS / Provisioning 

OSS / Asset Management 

OSS / Configuration Management 

OSS / Monitoring 

Metering 

BSS / Customer Management 

BSS / Rating 

OSS / Image Lifecycle Mgmt 

Reporting 

UI / Service Delivery Portal 

Compute, Web conferencing software, analytics 

application, etc. 



46 

Security and Availability 



CCMP RA – Security Architecture TWP (OPS316) : 


§ Defines all (cloud) security-related aspects to be considered when building a 

CCMP implementation, the corresponding managed environment and cloud 

services on top (focus is on CCMP aspects). 

§ Provides a consolidated view of all security-related information across all CCMP 

RA TWPs 

47 



--the the CCMP CCMP RA RA Security Architecture should should be be used used to to understand all all securityrelatedrelated 

concerns, requirements and and guidance to to be be taken taken into into account for for the the 

respective CCMP CCMP implementation. 



Security in CCMP-RA 

§ Security touches all aspects and work products of the CCMP-RA 

§ A consolidated view of Security for the CCMP-RA can be found in 

the CCMP-RA OPS 316 Security Architecture Work Product 

§ The OPS 316 Work Product includes background information about 

Security and Risk Management, as well as, the following topics: 

– Security Requirements 

– Security Roles 

– Security Policies & Controls 

– Security Use Cases 

– Security Non-Functional Requirements 

– Component Model 

– Operational Model 

– Security Services and Service Flows 

§ Since the assumptions, requirements and componentry related to 

Security may vary from design to design, it will be prudent to 

produce a series of OPS 316 documents for common solution 

patterns: 

– Public Cloud pattern with Provider and Subscriber roles, risks 

and requirements 

– Private Cloud pattern with Enterprise roles, risks and 

requirements 

– Hybrid Cloud patterns with both Provider and Enterprise roles, 

48 risks and requirements 

OPS 316 

Introduction & 

Risk Mgmt 

Security 

Requirements 

Roles 

Policies 

& Controls 

Use Cases 

Non-Functional 

Requirements 

Component 

Model 

Operational 

Model 

Services & 

Service Flows 

User use cases 

Sec Mgmt Cases 

Anomaly cases 

Quality 

Metrics 

Components 

Component 

Assemblies 

Security Zones 

Security 

Subsystems 



49 

Common Cloud Management Platform Reference Architecture: 

Architecture Overview Diagram – Availability Needs 

Virtualized Infrastructure – Server, Storage, Network, Facilities 




Services 

API 

BSS 

Business 

Support 

System 

OSS 

Operational 

Support 

System 


API 

Offering Mgmt 

Order Mgmt 

Accounting & Billing 

Contract Mgmt 



Provisioning 

Monitoring & 


Business-Process-as-a-Service 

Software-as-a-Service 

Platform-as-as-Service 

Infrastructure-as-a-Service 

Customer Mgmt 

Entitlements 

Invoicing 

SLA 

Reporting 




Configuration Mgmt 

Incident, Problem & 

Change Management 








Catalog 



Capacity & 






Cloud Services entry level with low 

availability guarantees 

• Consumer could create new cloud service in 

case of outage 

• Additionally selected services will allow also 

to increase high availability (mid-term) 

Virtualized Infrastructure with very high 

availability requirements to prevent mass 

outage 

• Failure of a single blade not as critical as the 

failure of a complete blade landscape 

Common Cloud Management Platform with 

medium (to high) availability needs 

• In case of outage no new cloud services can 

be (but existing ones do not fail) 



50 

Component Model 



CCMP RA – Component Model TWP: 


§ Defines all components required for creating a CCMP implementation and their functional 

scope. 

51 

The CCMP RA component model provides (product-neutral) guidance on how each 

functional CCMP component should be realized when developing a CCMP 


Focus of CCMP RA Component Model is component definition in support of cloud-scale 

efficiencies and costs (CCMP RA architectural principles are applied) – and how 

components are different from the traditional enterprise mgmt scope. 

– Based on coarse-grained architectural elements defined on CCMP RA AOD level 

§ Serves as basis for CCMP RA operational model 


Consumers: 

When When developing developing a specific specific CCMP CCMP implementation implementation … 

--the the CCMP CCMP RA RA Component Component Model Model should should be be used used to to understand understand how how all all components components of of a 

CCMP CCMP implementation implementation should should be be scoped scoped & realized realized in in support support of of achieving achieving cloud-scale cloud-scale 

(cost) (cost) efficiencies efficiencies and and agility. 

agility. 



The CM TWP describes the components & relationships related to 

CCM AOD services 

52 

CCMP services 

& capabilities 

CCMP BSS components & functions 

Details are available in CCMP RA TWP: “Component Model (ART 0515)“ 

CCMP component 

relationships 

CCMP OSS components & functions 

… 

… 



The conceptual CM decomposes CCMP Services in components and subcomponents 

or functions, and provides the related definitions 

Security 

Services 

53 

Business 

Support 

Services 

Definition: 

Capacity planning: Capacity planning is is the process of of determining the 

production capacity needed by by the Cloud service provider to to meet 

changing demands for for its its services. Future Cloud capacity 

requirements can be be determined by by analyzing business trends … 

About 200 definitions 

(51 components, 143 subc/functions) 

Portal services 

Operational 

Support 

Services 

Resiliency 

Services 



The specified CM details the relationships and dependencies between CCMP 

Services, and between components. 

54 

- RSA diagrams and 

textual descriptions of 

the component 

interfaces are provided 

for OSS and BSS: 

Provisioning - pCl2 

Updates CMDB with results 

of of provisioning activities, 

also updates change record 

with workflow status. 

- For each category of CCMP Services the specified CM provides: 

• External component dependency descriptions 

• Internal component dependency descriptions 

- At the end of the document is a component mapping with eligible tools 

OSS component relationships 



55 

Operational Model 



CCMP RA – Operational Model TWP: 


§ Defines CCMP deployment units and how they should be deployed in the 

management environment to meet all (cloud-specific) NFRs such as performance, 

security, resiliency, minimal costs, etc. 

§ Includes so-called “applied patterns” describing concrete, physical operational 

models serving as an example for how to deploy CCMP implementations 

56 



--an an implementation-specific operational model model must must be be created. The The CCMP CCMP RA RA 

Operational model model (incl. (incl. applied applied patterns) provides guidance and andserves serves as as a 

blueprint for for that. 

that. 



Operational Modeling helps ensure the IT infrastructure’s non-functional 

requirements are delivered, within all constraints. 

57 

System Requirements 

HBA User 

UC-SEC-02 Logoff 

UC-SEC-01 

Logon 

UC-ACCNT-01 Manage Accounts 

What do we have to do? 

(Use Case Model) 

A_Off-line 

Customer 

Customer registration 

Customer order creation 

Customer order handling 

A_On-line 

Customer registration 

Shopping lists 

Customer order 

A_Call 

Customer 

Payment details 

handling 

Centre Rep. 

Delivery details 


Customer 

Payment details Product 

registration 

& catalog 


Customer order 

updates 

handling 


Payment details 


AmGro-from- 

A_E-mail 

Home Order Mgt 

System 

System 

Order 

Order exceptions 

exceptions 

Order status Orders 

Credit 

Submitted orders Amendments 

authorisation 

Delivery 

Credit 

Product 

requests 

arrangements 

authorisations 

updates 

A_Warehouse 

Mgt System 

A_Credit 

Sales 

Agency 

Catalogue 

A_non-food 

Application 

data 

updates 

Fulfillment A_Product 

Maintenance 

Fulfillment A_Product 

Maintenance 

Fulfillment 

System 

A_Mgt Info 

A_Catalogue 

A_Applic’n 

System 

System 

Administrator 

How do we fit in? 

(System Context) 

How good does it have to be 

(Non-Functional (Non-Functional Requirements) 

Users 

Customer 

Service 

Representative 

Internal User 

Business Partner 

Delivery 

Channels 

Pervasive/ 

Wireless Devices 

Internet 

Browser 

Intranet Browser 

Internet or 

Extranet Browser 

e-business 

Services 

Registration Function 

Authentication and 

Authorization Function 

Enterprise Inquiry 

Function 

Enterprise Update 

Function 

Enterprise Reporting 

Function 

Messaging & Collaboration 

Function 

Enterprise Administration 

Function 

Resources 

Directory 

Systems 

Legacy 

Applications 

Database(s) 

System 

Monitoring 

Customer 

Relationshup 

management 

External 

Enterprise 

System 

What is our approach? 

(Architecture (Architecture Overview) 

System Architecture System Constraints 

 

DialogueControl 

 

SecurityProcessing AccountProcessing 

 

RelationalDBMS ApplicationServer 

 

AccountMgr 

 

SecurityMgr 

How is the application structured? 

(Component Model) 

Where does everything go? 

(Operational Model) 

What is the current environment? 

(Current IT) 

What other constraints are there? 

(Standards) 

Client 

Node 

External 

Systems 

Node 

E dge S erver Node 

Protoc ol Firewall Node 

Internet 

RED ZONE YELLOW ZONE GREEN ZONE 

Transcoder 

Node 

Reverse 

Proxy 

Node 

Network 

Intrusion 

Detection Node 

Domain Firewall Node 

Content 

Directory and 


Security Node 

Node 

Application 

Integration 

Server 

Hub 

Node 

Node 

Web Portal 

Node 

Personalization 

Node 

Ente rp ri se Firewall Node 

Database 

Server 

Node 

Enterprise 

Systems 

Node 

What Experience do we have? 

(Reference (Reference Models) 

Note: Operational modeling does not cover operations management processes. Cloud-specific operations management processes 

and procedures (e.g., IPC, Metering, Monitoring & Event Mgmt, SLM, etc.) are covered in the services flows deliverable. 

Details are available in CCMP RA TWP: “Operational Model (ART 0522)“ 



Attached View of CCMP ALOM 

58 

Since cloud service implementation 

architecture is beyond the scope of 

the CCMP RA, cloud service is 

modeled as a system actor. 

RSA Topology “Group” is used 

to separate CCMP OSS, BSS, 

and utility services (e.g., 

reporting & analytics) nodes. 

Note: 

• Prefix “A_” is used to name a human/system actor, “ALN_” an ALOM node, and “L_” a location. 

• CCMP ALOM DUs are not shown in the figure. 



CCMP LOM 

Overview 

The LOM nodes are 

defined based upon 

common tier-based 

implementation of an 

IT service. 

Application DUs and 

data DUs are 

deployed on different 

LOM nodes based 

upon common 

infrastructure design 

practices. 

59 



60 

Service Flows 



CCMP RA –Service Flows TWP: 


§ Defines all operational processes (“service flows”) required for managing cloud 

services based on a CCMP deployment. 

61 

– 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. 

§ Service flows depend on service management components as defined in the 

CCMP RA component model – CCMP components are required for automating as 

many tasks as possible. 



--the the CCMP CCMP RA RA Service Flows Flows TWP TWP describes the the management processes to to be be 

applied applied when when managing cloud cloud services via via CCMP. 

CCMP. 



CCMP RA / Cleansheet Service Flows Content: Overview 

62 

Service flows processes differences from standard IT management processes 

• Leverages reduced (eliminate) scope of management, standardization, 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 

• Configuration and Asset Mgmt 

• Patch / Provisioning / Image Mgmt 

• Incident / Problem Mgmt, Monitoring 

• Performance and Capacity Mgmt 

• SLM/Metering 

• Service Request Management 

• Continuity Mgmt 



63 

Architectural Decisions 



What are Architectural Decisions? Why Bother Capturing Them? 

§ “The design decisions that are costly to change” (Grady Booch, 2009) 

§ Definition in SOA Decision Accelerator (part of GTS SOA Infrastructure RA): 

64 

“Architectural decisions capture key design issues and the rationale behind chosen solutions. 

They are conscious design decisions concerning a software system as a whole, or one or 

more of its core components, with impact on non-functional characteristics such as software 

quality attributes.” 

§ From UMF work product description ART 0513 (was: IGS Method ARC 100): 

“The purpose of the Architectural Decisions work product is to: 

– Provide a single place to find important architectural decisions 

– Make explicit the rationale and justification of architectural decisions 

– 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 

– Provide a reference of documented decisions for new people who join the project 

– Avoid unnecessary reconsideration of the same issues” 



Capturing Architectural Decisions 

Example (taken from the URL above): 

AD ID 

Topic hierarchy 

Subject area 

Scope 

Problem statement 

Decision drivers 

Alternatives 

Recommendation 

Decision outcomes 

Background reading 

Related decisions 

Editorial information 

65 

Cmp-04 

Cloud computing 

Data center 

AD name 

CloudDesignAccelerator03 - ConceptualLevel - QoSViewpointsConceptualDecisions - CloudDesignDecisions - CloudManagementPlatformDecisions - 

OperationalSupportSystemsDecisions 

Phase 

Should the OSS only support the management of Infrastructure services or also platform and software services? It often is necessary to manage 

IaaS/PaaS/SaaS within one data center environment and build them on each other. Motivation: Need to understand level on consistency in OSS-level 

mgmt of infrastructure, platform and software services. 

Consistency desired when managing IaaS/PaaS/SaaS (education effort, licensing cost, etc.). 

[1] A single OSS for IaaS, PaaS and SaaS 

[2] One OSS for IaaS, a different one for PaaS + SaaS 

[3] Not applicable 

A single OSS allows maximum consistency and enables simplified integration and combination of infrastructure, platform and software services. So 

option 1: start with IaaS, grow into PaaS and SaaS. 

See CoP presentations and GTO 2009 for an introduction of the cloud/virtualization "stack". See architecture overview diagram of emerging CC RA for 

introduction to OSS capabilities. 

influences Cmp-05 OssMultitenancy 

is influenced by Cce-04 CloudVirtualizationLayers 

OssReach 

Solution outline 

Acknowledgements: original CDA content contributed by Michael Behrendt 

Last modification on 2009-06-17 17:09:25.347000 

Status: initial draft (desclet) 

Todo: harvest architectural knowledge from projects, align with other work products in GTS CC RA 

IPR level: COPYRIGHT-PROTECTED ASSET 

© IBM Research GmbH, 2009. All rights reserved. 

Role 

Infrastructure architect 



66 

Outlook 



Some Key Focus Areas for CCMP RA 2.0 

67 

§ Hybrid Cloud Management 

§ Performance & Scalability 

§ Consumability 

§ Standardization 



68 

Hybrid Cloud Management, Security and Integration 

§ From the Enterprise Client’s perspective: 

§ Integration of applications 

– On-premise to off-premise business 

application connectivity & governance 

§ Data Integration 

– Information exchange and data integration 

across the enterprise and clouds 

§ Monitoring and Management of workloads 

running off-premise on clouds 

– Monitoring on IaaS, PaaS and SaaS level 

– Policy based Workload Governance, 

Provisioning, Scheduling and Management 

– Metering, Accounting 

– Availability 

– Dashboard for service visibility 

§ Security for Hybrids 

– Control security and resilience of services 

(identity management, compliance, 

isolation) 

§ Application and Workload migration 

workbench 

– Tools to support the migration of workloads 

to the cloud 

Initial focus for 'Hybrid Cloud': 

'Provide clients the ability to manage and 

integrate workloads and resources on a cloud 

with their existing processes, management 

and business systems.' 



Open Cloud Standards Leadership 

Driving an Open 

Conversation 

Building a Strong 

Cloud Ecosystem 

Leading with 

IBM’s 

Core Strengths 

Engaging Industry 

Sector 

69 

Prevent 

Proprietary 

Lock-in 

Promote reuse of existing standards 

Establish IBM as a Thought Leader for Open Cloud Solutions 

Lead Open Cloud Manifesto with almost 400 companies 

Lead Open Cloud Use Case Project with 1500 world wide participants, including 

Chinese translation 

Enable alternatives at the Virtualization layer 

Drive a common VM API interfaces for management and image definitions 

Build open source adapters to existing hypervisor implementations 

Drive Application Portability that establishes an ecosystem for the 

development community 

Partner with industry leaders to define common APIs and an image format for 

IaaS, management, storage and beyond. 

Build open source adapters to existing implementations in Apache. 

Move Cloud Focus to Security and Management 

DMTF Audit & Compliance WG, OASIS Identity Management WG 

Future Management Orchestration standardization in OASIS 

Drive adoption of IBM Architecture and Vocabulary by 

Industry\Sector Standards Groups 

World Wide partnership with 

Initial focus in Financial Services, Retail, Telco, Government, & Education. 

Lead SLA Discussions based on Enterprise requirements & trust in IBM 



70 

Literature 



References 

§ The Big Switch by Carr, Nicolas, W.W. Norton & Company, ISBN 978-0-393-06228 

§ The Data Center As A Computer by Barroso, Luiz; Hoelzle, Lars at AbeBooks.co.uk - ISBN 

10: 159829556X - ISBN 13: 9781598295566 - 2008. 

§ Michael Armbrust et al., Above the Clouds: A Berkeley View of Cloud Computing, Feb. 2009 

71 

• http://www.eecs.berkeley.edu/Pubs/TechRpts/2009/EECS-2009-28.pdf 

§ IBM Journal of Research and Development, Volume 53 Issue 4, Breiter, Gerd; Behrendt, 

Michael; Lifecycle and characteristics of services in the world of Cloud Computing 

§ John W. Rittinghouse, James F. Ransome, Cloud Computing. Implementation, Management 

and Security, CRC Press 2009, ISBN 978-1-4398-0680-7 

§ Cloud Computing by C. Baun, M, Kunze, J.Nimis, S.Tai; Springer Verlag; 

ISBN 978-3-642-01593-9 

§ ITK-Kompendium 2010, F.A.Z. Institut, Hrsg, Marlene Neudörfer, S.132-138 Breiter, Gerd, 

Behrendt, Michael, Cloud Computing, ISBN 978-3-89981-731-7 

§ Tivoli Service Automation Manager Solution Guide by Thomas Spatzier 

§ Service Management and Cloud Computing, IBM website: 

• http://www-01.ibm.com/software/tivoli/solutions/cloudcomputing/ 



72 

For more information, please visit: 

ibm.com/cloud 

Or contact me at: 

gbreiter@de.ibm.com 

Thank you! 



73 

Trademarks and Disclaimers 

8 IBM Corporation 1994-2008. All rights reserved. 

References in this document to IBM products or services do not imply that IBM intends to make them available in every country. 

Trademarks of International Business Machines Corporation in the United States, other countries, or both can be found on the World Wide Web at 

http://www.ibm.com/legal/copytrade.shtml. 

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered 

trademarks of Intel Corporation or its subsidiaries in the United States and other countries. 

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. 

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. 

IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce. 

ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office. 

UNIX is a registered trademark of The Open Group in the United States and other countries. 

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. 

Other company, product, or service names may be trademarks or service marks of others. 

Information is provided "AS IS" without warranty of any kind. 

The customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual 

environmental costs and performance characteristics may vary by customer. 

Information concerning non-IBM products was obtained from a supplier of these products, published announcement material, or other publicly available sources and does 

not constitute an endorsement of such products by IBM. Sources for non-IBM list prices and performance numbers are taken from publicly available information, 

including vendor announcements and vendor worldwide homepages. IBM has not tested these products and cannot confirm the accuracy of performance, capability, or 

any other claims related to non-IBM products. Questions on the capability of non-IBM products should be addressed to the supplier of those products. 

All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. 

Some information addresses anticipated future capabilities. Such information is not intended as a definitive statement of a commitment to specific levels of performance, 

function or delivery schedules with respect to any future products. Such commitments are only made in IBM product announcements. The information is presented here 

to communicate IBM's current investment and development activities as a good faith effort to help with our customers' future planning. 

Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any 

user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage 

configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput or performance improvements 

equivalent to the ratios stated here. 

Prices are suggested U.S. list prices and are subject to change without notice. Starting price may not include a hard drive, operating system or other features. Contact 

your IBM representative or Business Partner for the most current pricing in your geography. 

Photographs shown may be engineering prototypes. Changes may be incorporated in production models.

IBM Cloud Computing & Common Cloud Management Platform - IAAS

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?