8/6/2019 IBM Cloud Aneb Jak Na to II

1/13

2011 IBM Corporation

Cloud Computing Reference Architecture 2.0:Pehled

8/6/2019 IBM Cloud Aneb Jak Na to II

2/13

2011 IBM Corporation

IBM Cloud Computing Reference Architecture

2

The IBM Cloud Computing Reference Architecture zajiuje konzistenci& kvalitu nap vvojem a dodnm projektu

The IBM Cloud Computing Reference Architecture Je zaloeno na otevench standardechZaruuje enterprise-class security pro zabezpeen bezpenostnch norem na rovni

lokln, reginln a nrodn

Kombinace vkonn automatizace a zen slueb (low touch) s bohatou sadou sluebpro zen obchodnch proces, top-to-bottom zen kloudov infrastuktury a cloudovchsluebPodporuje pln spektrum model scloudovch slueb vetn Infrastructure as a Service

(IaaS), Platform as a Service (PaaS), Software as a Service (SaaS) a Business Process

as a Service (BPaaS)Dovoluje flexibiln klovatelsnost a stabilitu pro ekonomick provozovn cloudu azabezpeen ROIZajiuje bezproblmovou integraci do stvajcho zkaznickho prostedJe zaloeno na nejlep analze a doporuench z jednotlivch obor s SOA

architekturou

8/6/2019 IBM Cloud Aneb Jak Na to II

3/13

2011 IBM Corporation

IBM Cloud Computing Reference Architecture

3

Cloud Computing Reference Architecture (CC RA) Role

Ti hlavn role (cloud service

consumer, provider anddeveloper)

Cloud service Consumer lovk, nebo organizace kterpouv sluby cloudu. Pstuppes samoobslun katalogslueb

Cloud Service Provider Organizace odpovdn zaprovozovn a podporucloudovch slueb

Cloud Service Creator Organizace zodpovdn zatvorbu cloudovch slueb.Vtinou je tak Cloud ServiceProvider

Cloud ServiceConsumer

Cloud Service Provider

Common CloudManagement Pl

OperationalSupportServices

(OSS)

Cloud Services

Infrastructure-as-a-Service

Platform-as-a-Service

Software-as-a-Service

Business-Process-as-a-Service

CloudService

IntegrationTools

Consumer In-house IT

Existing & 3 rd partyservices, Partner

Ecosystems

8/6/2019 IBM Cloud Aneb Jak Na to II

4/13

2011 IBM Corporation

IBM Cloud Computing Reference Architecture

4

Cloud Computing Reference Architecture (CC RA) Overall drill-downCloud Computing Reference Architecture (CC RA) Overall drill-down

Cloud Service Provider Cloud ServiceConsumer

Cloud Services

PaaS

SaaS

BPaaS

Common CloudManagement Platform

Cloud ServiceIntegration

Tools

Consumer In-house IT

Applications

BusinessProcesses

OSS Operational SupportServices

BSS BusineServices

SubscriptionManagement P

Metering R

Clearing &Settlement AP

Customer Account

Management

SOC

Contracts &Agreement

Management

SR

Man

Consumer BusinessManager

Consumer Enduser

ServiceManager

ServiceIntegrator

S er v i c e M a n a g e m e n t

S er v i c e C o n s u m er P or t al & A P I

A P I

A P I

A P I

Existing &3 rd partyservices,

Partner Ecosystems

ProvisioningIncident &Problem

Management

IT ServiceLevel

Management

Service Automation Management

Service Delivery Catalog

ServiceRequest

Management

Change &ConfigurationManagement

ImageLifecycle

Management

Monitoring &Event

Management

IT Asset &License

Management

Capacity &PerformanceManagement

Platform & Virtualization Management

P l a t f o r m M g m t I n t e r f a c e s

S o f t w a r e M g m t I n t e r f a c e s

B P M g m t

I n t e r f a c e s

2011 IBM Corporation

8/6/2019 IBM Cloud Aneb Jak Na to II

5/13

2011 IBM Corporation

IBM Cloud Computing Reference Architecture

5

Cloud Service Creation

8/6/2019 IBM Cloud Aneb Jak Na to II

6/13

2011 IBM Corporation

IBM Cloud Computing Reference Architecture

6

Krok nezbytnch pro vytvoen cloudovch slueb

5. Implement monitoring metrics &event correlation rules

6. Implement incident, problemand asset mgmt processes

7. Implementresiliency SLA

Select existing agent / implementnew agent for monitoring JVMheapsize, hypervisor swap filesize, # of processes, etc.

Select existing agent / implementnew agent for monitoring JVMheapsize, hypervisor swap filesize, # of processes, etc.

Incident, problem & asset mgmtprocess is specific to cloudservice customization needed

Incident, problem & asset mgmtprocess is specific to cloudservice customization needed

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

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

2. Implement runtimefunctionality

3. Define unit of delivery &rating

Describe function, price , SLA of cloud service, incl. managementscope

Describe function, price , SLA of cloud service, incl. managementscope

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

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

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

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

10. Implement cloud servicespecific billing metrics

11. Implement rates for chargingcloud service consumption

9. Implementsecurity functions

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

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

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

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

Implement authentication,auditing, data protection,governance & audit

Implement authentication,auditing, data protection,governance & audit

8. Implement backupapproach

Examples: Backup all VMs,backup DB of LotusLiveapplication

Examples: Backup all VMs,backup DB of LotusLiveapplication

4. Implement self-service delivery& management functionality

Examples: Create VM, add morenodes to WAS cluster, changemax # of seats for LotusLive webconf

Examples: Create VM, add morenodes to WAS cluster, changemax # of seats for LotusLive webconf

12. Register cloud serviceto service catalog

A cloud service must beregistered to the service catalogto be externally accessible,entitlements need to beconfigured,

A cloud service must beregistered to the service catalogto be externally accessible,entitlements need to beconfigured,

Storage Network 11**

11

**

**11 11

11

1111

11 11

11**

11

**11 11

11

1111

11 11

11**11

**

** 11 11

111111

1111

$$$$$$

Server OSMWApp

!

8/6/2019 IBM Cloud Aneb Jak Na to II

7/13 2011 IBM Corporation

IBM Cloud Computing Reference Architecture

7

Step Products & technologies to build your own cloud service

1. Specify cloud service description n/a (cross-cutting)

2. Implement runtime functionality of the cloud service KVM, VMware, Linux, Windows, WAS, DB2, Cognos, Filenet,

3. Define Unit of delivery & rating n/a (cross-cutting decision)

4. Implement self-service delivery & management functionality TSAM

5. Implement monitoring metrics & event correlation rules IBM Tivoli Monitoring, Omnibus, Impact

6. Implement incident, problem and asset mgmt processes Tivoli Service Request Manager & TAMIT

7. Implement resiliency SLA Tivoli System Automation

8. Implement backup approach Tivoli Storage Mgr

9. Implement security functions Tivoli Security / ISS portfolio

10. Implement cloud service specific billing metrics TUAM

11. Implement rates for charging cloud service consumption TUAM

12. Register cloud service to service catalog TSAM / TSRM Service Provider Edition

Pehled doporuench nstroj a technologi pro jednotlive kroky pi vznikuslueb

8/6/2019 IBM Cloud Aneb Jak Na to II

8/13 2011 IBM Corporation

IBM Cloud Computing Reference Architecture

8

Cloud Service Provider

8/6/2019 IBM Cloud Aneb Jak Na to II

9/13 2011 IBM Corporation

IBM Cloud Computing Reference Architecture

99

Cloud service model definitionsTermTerm DefinitionDefinition SourceSource

IaaS

infrastruktura jako sluba (z "Infrastructure as a Service") v tomto ppad poskytovatelslueb se zavazuje poskytnout infrastrukturu jako slubu. (=Hardware)

NIST1

PaaS

Platforma jako sluba (z "Platform as a Service") poskytovatel v PAAS modelu poskytujekompletn prostedky pro podporu celho ivotnho cyklu tvorby a poskytovn webovchaplikac a slueb pln k dispozici na Internetu, bez monosti staen softwaru. TypickyOperan systm + middleware (databze, aplikan server...)

NIST1

SaaS

Software jako sluba (ze "Software as a Service") aplikace je licencovna jako slubapronajman uivateli. Pkladem me bt znm sada aplikac Google Apps . U IBMnapklad www.lotuslive.com

NIST1

Business process jako sluba napklad ProcurementBPaaS

IBM2

8/6/2019 IBM Cloud Aneb Jak Na to II

10/13 2011 IBM Corporation

IBM Cloud Computing Reference Architecture

10

Infrastructure drill-downInfrastructure drill-down

Cloud ServiceConsumer

Cloud Service Provider

Common Cloud Manag

OperationalSupport Services

(OSS)

Cloud Services

Infrastructure-as-a-Service

Platform-as-a-Service

Software-as-a-Service

Business-Process-as-a-Service

CloudService

IntegrationTools

Consumer In-house IT

Infrastructure

Server Storage Network

Processor Drives Internal

Existing & 3 rd partyservices, Partner

Ecosystems

2011 IBM Corporation

8/6/2019 IBM Cloud Aneb Jak Na to II

11/13 2011 IBM Corporation

IBM Cloud Computing Reference Architecture

11

Security, Resiliency, Performance & Consumability drill-downSecurity, Resiliency, Performance & Consumability drill-down

Cloud Service Provider Cloud ServiceConsumer

Cloud ServiceIntegration

Tools

Consumer

In-house IT

Common Cloud M

OperationalSupportServices

(OSS)

Cloud Services

Infrastructure-as-a-Service

Platform-as-a-Service

Software-as-a-Service

Business-Process-as-a-Service

Infrastructure

Existing & 3 rd partyservices, Partner

Ecosystems

11 2011 IBM Corporation

8/6/2019 IBM Cloud Aneb Jak Na to II

12/13

2011 IBM Corporation

IBM Cloud Computing Reference Architecture

12 GovernanceSecurity, Resiliency, Performance & Consumability

Cloud Service Provider

Cloud Services

IaaS

PaaS

SaaS

BPaaS

Common CloudManagement Platform

Cloud ServiceIntegration

Tools

Consumer In-house IT

Infrastructure

Middleware

Applications

BusinessProcesses

OSS Operational SupportServices

BSS Business SupportServices

Customer Account

Management

ServiceOfferingCatalog

ServiceOffering

Management

TransitionManager

DeploymentArchitect

OperationsManager

Service Provider Portal & API

Consumer Administrator

Consumer BusinessManager

Consumer Enduser

Service CreationTools

ServiceManagementDevelopment

Tools

Service RuntimeDevelopment

Tools

SoftwareDevelopment

Tools

Image CreationTools

ServiceComponentDeveloper

Infrastructure

Security &Risk Manager

Customer Care

ServiceManager

BusinessManager

ServiceComposer

OfferingManager Service

Integrator

S er v i c

e

M an

a g em

en

t

S er v i c e

C on

s um

er P

or t al & A P I

S er v i c eD

ev el o pm

en

t P

or t al & A P I

A P I

A P I

A P I

A P I

Existing &3rd partyservices,Partner

Ecosystems

ProvisioningIncident &Problem

Management

IT ServiceLevel

Management

Service Automation Management

Service Delivery Catalog

Platform & Virtualization Management

Infrastructure

MgmtInterfaces

Platform Mgmt

Interfaces

SoftwareMgmt

Interfaces

BPMgmt

Interfaces

Pouit IBM Tivoli produktyPouit IBM Tivoli produkty

TSAM

TSRM

TPM

TSRM

TSLATNSQM

TSRM

CCMDBTADDM

TAMIT

TPM

VMControl

TPC

TSA MPTSA AM TSM

TAMTDSTFIM

TSRM SPE

TSRM SPE

TSRM SPE TSRM SPE

TSRM SPE TSRM SPE

TSRM SPE TSRM SPE

TSRM SPE

TSRM SPE

TSRM SPETUAM

TSRM SPETUAM

TSRM SPEITM, ITNM,OMNIbus,

TBSM

2011 IBM Corporation

8/6/2019 IBM Cloud Aneb Jak Na to II

13/13

2011 IBM Corporation

IBM Cloud Computing Reference Architecture

13

Metering, Rating & AccountingCloud ServiceRequestor #1

Service A4 CPUs on Server 12 GB60 server hrs @ $25/ server hr 240 CPU hrs @ $5/ CPU hr 120 GB hrs @ $3/ GB hr

Cloud ServiceRequestor #2

Service A3 CPUs on Server 24 GB50 server hrs @ 25/ server hr 150 CPU hrs @ $5/ CPU hr 200 GB hrs @ $3/ GB hr

Cloud Service

Requestor #3

Service B2 CPUs on Server 11 GB100 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 Costs

Server 1 CPU usage = 3,000 CPU mins * $.40/min

Server 2 CPU usage = 2,500 CPU mins * $.60/min

Server 1 software usage = 60 hrs * $15/hr

Server 2 software usage = 40 hrs * $10/hr

Server 1 labor costs = $40

Server 2 labor costs = $60

$3,060

$2,600

Service A revenue = $5,660

Service A costs = $4,100

Cloud Service Provider

Service B revenue = $3,000

Service B Costs

Server 1 CPU usage = 5,000 CPU mins * $.40/min

Server 1 software usage = 80 hrs * $15/hr

Server 1 labor costs = $40

DB2 Help Desk = $50

Service B costs = $3,290

Profit

Loss

Allocation Usage Activity Usage

Service A costs = $4,100

Cost and prices are for illustration purposes only