Cloud Computing как новая технологияпредоставления инфраструктурных сервисовпо требованиюYuri Demchenko
University of Amsterdam
RELARN2010 Conference
27 September – 1 October 2010, Russia

Outline Cloud Computing – IaaS, SaaS, PaaS Страндартизация в области Cloud Computing и ИКТ конвергенция Европейские проекты
 Composable Services Architecture (CSA) Services Lifecycle Management Обсуждение - Возможные направления исследованийRELAN2010

Cloud Computing

Slide_2

Cloud Computing – Новая технологияили Маркетинговый прием?
 Первые массовые упоминания начиная с 2007-2008
 Amazon clouds – Elastic Computer Cloud (EC2), Elastic Storage (ES2) Первое свободное програмное обеспечение – Eucalyptus (2008) В настоящее время - множество Теперь после 2-х летнего маркетингового бума – “облака” везде ивсе в “облаках” Большие коммерческие организации наиболее активны, используявозможность лучшей утилизации свободных компьютерных ресурсов иобслуживания широкой массы мелких потребителей Вовлечение университетов в Clouds – начиная с конца 2009
 Включая Университет АмстердамаRELAN2010

Cloud Computing

Slide_3

Cloud Computing – Определение Определение Cloud Computing в документе NIST
http://csrc.nist.gov/groups/SNS/cloud-computing/cloud-def-v15.doc
 “Cloud Computing is a model for enabling convenient, on-demand network

access to a shared pool of configurable computing resources (e.g.,
networks, servers, storage, applications, and services) that can be rapidly
provisioned and released with minimal management effort or service
provider interaction.” Cloud Computing является моделью для удобного сетевого доступа потребованию к разделяемым компьютерным ресурсам (например,сетевые ресурсы, серверы, запоминающие устройства), которые могутбыть быстро предоставлены с минимальными административнымизатратами или взаимодействием с провайдером Предложенное определение включает 5 существенных
характеристик/признаков, 3 модели/типа услуг, 4 модели внедренияRELAN2010

Cloud Computing

Slide_4

Cloud Computing – 5 признаков
 On-demand self-service – Потребитель может самостоятельно
запросить необходимые ресурсы, такие как серверное время,запоминающие устройства, которые будут автоматическисконфигурированы с минимальным человеческим участием.
 Broad network access – Ресурсы и сервисы доступны по сети сиспользованием упрощенного интерфейса (позволяя использоватьразличные thin или thick клиенты, например, рабочие станции,ноутбуки, PDA, мобильные устройства) Resource pooling – обьединение множества индивидульныхресурсов и использование общего интрефейса Rapid elasticity – возможность увеличения выделенных ресурсовбез переконфигурации предоставленной инфраструктуры
 Measured Service – контроль качества и учет предоставляемыхуслуг
RELAN2010

Cloud Computing

Slide_5Базовые модели предоставления услуг в Clouds SaaS – Software as a Service
 PaaS – Platform as a Service
 IaaS – Infrastructure as a Service Ранее называлась Hardware as a Service (HaaS) или Utility Computing(еще до Грид) Необходимые технологические решения Логическая абстракция ресурсов Агрегатирование, фрагментация, композиция ресурсов Виртуализация Управление жизненным циклом предоставляемых по требованиюресурсов и сервисов– Состояние– Учет– Устойчивость, надежность, безопасностьRELAN2010

Cloud Computing

Slide_6

Cloud Computing – 4 модели внедрения
 Private cloud - Инфраструктура Cloud, созданная для целейпредприятия; может управляться самой организацией или третьейстороной, принадлежать самому предприятию или третьей стороне.
 Community cloud - Инфраструктура Cloud, созданная группой
предприятий и обслуживающая определенное сообщество,имеющее общие цели или задачи (например, проект, уровеньбезопасности); может существовать как часть предприятийучастников или предоставляться третьей стороной.
 Public cloud - Инфраструктура Cloud, доступная для широкой массыпользователей, включая крупную промышленность ииндивидуальных пользователей. Как правило, публичные услугиcloud предоставляются специализорованными провайдерами.
 Hybrid cloud – гибридная модель, которая может включать
различные типы инфраструктурных компонентов
RELAN2010

Cloud Computing

Slide_7Стандартизация (1) NIST (National Institute of Standards and Technology) Имеет специальную рабочую группу и известен своим концептуальнм

определением Cloud Computing

 DMTF – Distributed Management Forum/Task Force Стандартизация в области виртуализации компьютерных ресурсов

 ITU-T – New Generation Network (NGN) и модель конвергенциикоммуникационных услуг/инфраструктуры и компьютерных ресурсов Y-seria standards

 TeleManagement Forum (TMF) NGOSS – New Generation Operations Systems and Software (former eTOM

– Telecommunications Operations Model)
 SDF – Service Delivery Framework– Управление жизненным циклом ресурсов и сервисов – Request, Reservation,Deployment, Operation, Decommissioning
 SLA Management Framework
RELAN2010

Cloud Computing

Slide_8Стандартизация (2) - ITU-T Y-seria NGN Recommendations
 ITU-T REC Y.2232 (01/2008) NGN convergence service model andscenario using Web Services
 ITU-T REC Y.2234 (09/2008) Open service environment capabilities
for NGN ITU-T REC Y.2012 (09/2006) Functional requirements and architectureof the NGN release 1
 ITU-T REC Y.2011 (10/2004) General principles and general reference
model for Next Generation Networks
 ITU-T REC Y.2201 (04/2007) NGN release 1 requirements
 ITU-T REC Y.2701 (04/2007) Security requirements for NGN release 1
 Security requirements to NGN and its interfaces (e.g., UNI, NNI, ANI) byapplying X.805
 Uses trust model based on NE supporting the functional Y.2012 entities

RELAN2010

Cloud Computing

Slide_9

T-REC-Y.2234-200809 Open service environment capabilities forNGN (1)Extended NGN architecture positioning the OSERELAN2010

Cloud Computing

Slide_10Стандартизация (3) - TMF Service Delivery Framework (SDF)

Main goal – automation of the whole service delivery and operation process (TMF,http://www.tmforum.org/), including End-to-end service management in a multi-service providers environment
 End-to-end service management in a composite, hosted and/or syndicatedservice environment
 Management functions to support a highly distributed service environment,
for example unified or federated security, user profile management,
charging etc.
 Any other scenario that pertains to a given phase of the service lifecycle
challenges, such as on-boarding, provisioning, or service creation

RELAN2010

Cloud Computing

Slide_11

SDF Reference Architecture (re-factored from SDF)
Design16
SDF Service Design
Management (ISS)

DeploySDF Service
Repository (ISS)910
SDF Service
Lifecycle Metadata
Repository (ISS)1711
SDF Service Lifecycle
Metadata
Coordination (ISS)SDF Service
Deployment
Management (ISS)

2Operate

SDF Service State
Monitor (ISS)6
SDF Service Provisng
Mngnt (MSS)SDF Service
Instance

6
SDF Service Quality/
Problem Mngnt (MSS)

13SDF Service Resource
Fulfillment (ISS)SDF Service Resource
Monitor (ISS)7
SDF Service Usage
Mngnt (MSS)SDF MSSRELAN2010

Composite Services
provisioned on-demand

12131415
SDF Service Resource
Usage Monitor (ISS)

4SDF ISS

Cloud Computing

81 – Service Instance2 - Service Management Interface
3 – Service Functional Interface
4 - Management Support Service (SDFMSS)
8 - Infrastructure Support Service (ISS)
DESIGN stage
9 - Service Repository
10 - Service Lifecycle Metadata
Repository
16 - Service Design Management
DEPLOYMENT stage
10 - Service Lifecycle Metadata
Repository
11 - Service Lifecycle Metadata
Coordinator
17 - Service Deployment Management
OPERATION stage
5 - Service Provisioning Management
6 - Service Quality/Problem Management
7 - Service Usage Monitor
12 - Service State Monitor
13 - Service Resource Fulfillment
14 - Service Resource Monitor
15 - Resource Usage Monitor

Slide_12Стандартизация (4) – Open Grid Forum (OGF) OCCI WG – Open Cloud Computing Interface Опубликованы ряд документов, определяющихXML-формат запросавыполнения задач в Cloud Базовым протоколом является REST (в отличие от SOAP,
используемого в Web Services) ISOD RG (планируемая) – On-Demand Infrastructure Services
Provisioning Создание исследовательской группы инициировано проектами

GEYSERS, GEANT3, NOVI – все с участием Университета Амстердама Будет рассматривать вопросы виртуализации инфраструктурныхсервисов
– Фактически реализация модели Infrastructure as a Service Исследование существующих стандартов и решений для созданиябазовой архитектуры и компонентов для виртуализациираспределенной инфраструры сетевых и компьютерных ресурсовRELAN2010

Cloud Computing

Slide_13Основные Европейские проекты по Clouds
 RESERVOIR – Виртуализация компьютерных ресурсов и созданиеоткрытого базового пограммного обеспечения для Clouds(middleware) OpenNebula – Cloud middleware Claudia – Service Manager/Services Layer middleware 4WARDS – Виртиализация сетевых ресурсов GEANT3 JRA3 Task 3 – Composable Services
 Composable Services Architecture (CSA) Виртуализация услуг и ресурсов для Европейских научных сетей

 GEYSERS Расширенное внедрение CSA
 Предложена адаптация TMF Service Delivery Framework (SDF)

RELAN2010

Cloud Computing

Slide_14

GEYSERS Project – Цель и задачи
GEYSERS – Infrastructure provider’s view “Today’s telecom operators face the need for providing users with dynamic highcapacity and high-performance optical networks connectivity services tightly
bounded with IT resources”

Новая архитектура, позволяющая Координированное и оптимизированное совместное предоставлениеоптических каналов и компьютерных ресурсов Фактически, реализация модели IaaS Clouds Предоставление услуг конечным пользователям к распределенным многодоменным ресурсам, вкючая от множества провайдеров Реализация новой бизнес-модели создания и работы провайдеров иоператоров виртуальных ресурсов (VIP – Virtual Infrastructure Provider, VIO Virtual Infrastructure Operator)
 Enhanced GMPLS/PCE control plane for dynamic control and re-planning of
infrastructure resources (Net + Any IT) based on End Users and Network
Operator requirement and SLA Оптимизация энергопотребеленияRELAN2010

Cloud ComputingSlide_15GEYSERS Architecture (1)Roles

Application

Application

Application/service
ProviderApplication Interface

Network Control Plane (Extended GMPLS Control Plane)
Extended GMPLS

Extended GMPLS

NetworkOperator

Logical Infrastructure Composition Layer

Infrastructure
ProviderIT Infrastructure

Storage
RELAN2010

Network Infrastructure

Optical infrastructure

IT Infrastructure

Resources
Computing

16
Slide from the GEYSERS Project presentation (Courtesy Sergi Figuerola)
Cloud Computing
Slide_16

GEYSERS Architecture (2)Application Service
Provider (ASP)

Service Consumer
Service Middleware Layer (SML)
Virtual IT Management

Application Service
Provider (ASP)

NIPS UNI

Virtual Infrastructure
Operator (VIO)

GEYSERS

Network Control Plane (NCP)

Virtual Infrastructure

Logical Infrastructure and Composition Layer (LICL)

Virtual Infrastructure
Provider (VIP)

Virtual Resource Pool

Physical Infrastructure
Resources Provider (PIP)
Infrastructures (Optical + Any-IT)
RELAN2010

Cloud Computing

Slide_17

GEYSERS Architecture (3)Service Middleware Layer (SML)

Service Middleware Layer (SML)

Virtual IT Management

Virtual IT Management

NCP

NCP
Virtual Infra.

VIP1

Virtual Infra.

VIPn

GEYSERS

Service Consumer

VIOn

VIO1

Service Consumer

Virtual Resource PoolPIP1
RELAN2010

PIPn
Cloud Computing

Slide_18

GEYSERS – Основные технологические проблемы итребования Общая (абстрактная/логичекская ) модель сетевых и компютерныхресурсов Возможность комбинирования и разделения ресурсов (Pooling,Partitioning, Aggregation, Composition) Управление жизненным циклом предоставляемых по требованиюресурсов Возможность «эластичного» изменения ресурсов Быстрое восстановление после сбоя или миграция ресурсов Создание динамических ассоциаций безопасности (Security Federations)и федеративный доступ к ресурсам (Federated Access) Изоляция логических/виртуальных ресурсов, работающих на однойфизической платформе Проблема безопасности и контроля доступа

RELAN2010

Cloud Computing

Slide_19

GEYSERS Service Delivery Workflow

Service Request/
SLA Negotiation

Replanning

Services
Provisioning
Workflow
by VIP

Service Request/
SLA Negotiation

Composition/
Reservation

Planning/Design

Deployment
Deployment(Instant&Config&Synchro)
Recovery/
Migration

Operation&Monitoring(by VIO)

ReCompositionRegistr&Synchro
Network+ITServices
Provisioning
Workflowby VIO

Geysers SDF supports
both• Geysers
infrastructuredevelopment anddeployments, and• its operation for ondemand
Infrastructureservices
provisioning by VIO

Recovery/
Migration

Operation(Monitoring)

Decommissioning
Decommissioning

RELAN2010

Cloud Computing

Slide_20Типовая инфраструктура для e-Science

Control &Monitoring

User A

Instrument(Manufactoring)

Grid
Storage T0

GridCenter

Grid
Storage T1

GridCenter

Grid
Storage T1

Visualisation
User K
User P
Visualisation
Computing
Cloud

Permanent link
High Speed link provisioned on demand
Link provisioned on-demandRELAN2010

Cloud Computing

CloudStorageПриборы иуправлениеэкспериментомВычислительные
ресурсыЗапоминающиеустройстваВизуализация
Grids & Clouds

Slide_21

Composable Services Layered Model

Application Layer

Virtualisation Layer

 Application Layer hosts application
related protocols
 GEMBus Messaging Infrastructure (GMI)
includes Messaging Layer

Composition & Orchestration Layer

 Virtualisation(Composition&Orchestration) Layer
Logical Abstraction Layer

Messaging Layer

Network&Transport Layer

RELAN2010

 Network&Transport Layer should allow
using/binding to standards
communication and security protocol
 Composable services are defined as“dynamically re-configured virtualisedservices” according to OSIMM model

Cloud Computing

Slide_22

Composable Services Architecture (CSA) –Version 0.11 – Simplified/Deprecated
GEMBus provides common
dynamically configurable
messaging infrastructure for
Composable services
communication.

Applications and User Terminals

Control & Management(Orchestration,Operation)

ComposableServices
Middleware(GEMBus)

Composition Layer(Comp. Services)

Logical Abstraction Layer for Component Services and Resources

StorageResources

Network Infrastructure

GEMBus is an ongoingdevelopment in the GN3
JRA3 Task 3 “ComposableServices” activity

ComputeResources

Component Services & Resources

RELAN2010

Cloud Computing

Slide_23

Composable Services Architecture – Version 0.13
Applications and User Terminals

UserClient

Proxy (adaptors/containers) – Composed/Virtualised Services and Resources

Control &Management
Plane(Operation,Orchestration)

Composition
Layer/Serv

Composable Services Middleware(GEMBus)MD SLC

Registry

Logging(Reservation
SLA
Negotiatn)

Security

Composable
Services
lifecycle/provisioning
stages(1) Request(2) Composition/Reservation(3) Deployment(4) Operation(5) Decommissioning

Logical Abstraction Layer for Component
Services and Resources

Proxy (adaptors/containers) - Component Services and Resources

StorageResources

ComputeResources

Network Infrastructure
Component Services & Resources

RELAN2010

Cloud Computing

Control/Mngnt Links

Data Links

Slide_24

Composable Services Lifecycle/Provisioning Workflow
Main stages/phases
Service Request/
SLA NegotiationComposition/Reservation
Re-Composition

ServiceLifecycle
MetadataService(SL MD)

DeploymentOperation(Monitoring)Provisiong
SessionManagntRe-Composition should addressincremental infrastructure changes
Recovery/Migration can use SL-MD
to initiate resources resynchronisation but may require recomposition

The whole workflow is supported by theService Lifecycle Metadata Service(SL MD)

Decommissioning

RELAN2010

Additional stages

Registr&Synchro
Recovery/Migration

Service Request (including SLAnegotiation)
Composition/Reservation (akadesign)
Deployment, including
Reqistration/Synchronisation
Operation (including Monitoring)
Decommissioning

Cloud Computing

Slide_25

Composable Services Architecture – Version 0.13
Lifecycle stages workflow
4Serv

UserClient

4 3

Serv

Applications and User Terminals

4

Serv

Proxy (adaptors/containers) – Composed/Virtualised Services and Resources

13

2

Control &Management
Plane

1(Operation,Orchestration)

4(1) Request(2) Composition/Reservation(3) Deployment(4) Operation(5) Decommissioning

23Composition
Layer /Serv

Composable Services Middleware(GEMBus/GESB)(ReservationSLA
Negotiatn)

2
MD SLC

RegistryLogging

Security

ComposableServices
lifecycle/provisioning
stagesMD SLC – Service
Lifecycle Metadata

3 2

GEMBus – GEANT
Multidomain Bus
Logical Abstraction Layer for Component
Services and Resources

3 2

GESB – Geysers ESB
44
Proxy (adaptors/containers) - Component Services and Resources

StorageResources

ComputeResources

Network Infrastructure
Component Services & Resources

RELAN2010

3 2

Cloud Computing

Control/Mngnt Links

Data Links
Slide_26

CSA functional elements interaction(1) Request
 User Client -> Control and Management(2) Composition/ Reservation
 Control&Mngnt -> Registry -> Composition/Reservation Serv -> (LogicalAbstract -> Resr Adapters) -> LC Metadata Serv

(3) Deployment
 Control&Mngnt -> Composition/Reservation Serv -> (Logical Abstract ->Resr Adapters) -> LC Metadata Serv -> User Client(4) Operation
 User Client -> Control&Mngnt (Orchestration) -> Rsr Adapters ->Virtualised/Composed Applications(5) Decommissioning Control&Mngnt -> LC Metadata Serv -> (Logical Abstract -> Resr Adapters)
RELAN2010

Cloud Computing

Slide_27

GEMBus Infrastructure for Composable Service
GEMBus Component Services
Service 1

Service 2

Service 3

Service 4(CSrvID,SesID)(CSrvID,SesID)(CSrvID,SesID)(CSrvID,SesID)

Message HandlingRouting

Configuration

Interceptors(AspOrient)

GEMBus

GEMBus Messaging
Infrastructure (GMI)GEMBusRegistry

Composition &Orchestration

Security Service

Logging Service

GEMBus Infrastructure Services

GEMBus provides common dynamically configurable messaging infrastructure for
Composable services communication
RELAN2010

Cloud Computing

Slide_28

Example Service Composition – Service NX

Service 4(CSrvID,SesID)

UserClient

Composed Service NX(CSrvID,SesID)

Service 3

Service 1

Service 2(CSrvID,SesID)(CSrvID,SesID)(CSrvID,SesID)

Service 4

Composed Service NX(CSrvID,SesID)(CSrvID,SesID)(CSrvID,SesID)

Role and place for
Composition andOrchestration* Composable
services or
GEMBusinfrastructureservice

User
Interface

UserClient

Frontend
CompSrvNX(CSrvID,SesID)(CSrvID,SesID)

Service 3

Service 1

Service 2(CSrvID,SesID)(CSrvID,SesID)(CSrvID,SesID)

CSrvID, SesID – bind component services into the on-demand provisioned Composedservice NX
RELAN2010

Cloud Computing

Slide_29Возможные темы для научных исследований в CloudComputing Архитектура для совместного предоставления сетевых икомпьютерных ресурсов по требованию Управление жизненным циклом услуг, предоставляемых потребованию Инфраструктура безопасности для распределенных динамическихуслуг Общее описание ресурсов, поддерживающее весь эволюционныйжизненный цикл Physical Resource (PR) – Logical Resource (LR) – Virtual Resource (VR)RELAN2010

Cloud Computing

Slide_30

Дополнительная информация ITU-T NGN Architecture Security Services Lifecycle Management Model GEMBus functional model details

RELAN2010

Cloud Computing

Slide_31

Y.2011 General principles and general reference
model for NGNNGN Basic Reference Model (NGN BRM)

RELAN2010

Cloud Computing

Slide_32

Y.2011 General principles and general reference
model for NGNY.2011 General Functional Model
RELAN2010

Cloud Computing

Slide_33

T-REC-Y.2234-200809 Open service environment capabilities forNGN (1)Extended NGN architecture positioning the OSERELAN2010

Cloud Computing

Slide_34

Proposed Security Services Lifecycle Management Model
Security Service request and generation of the GRI that will serve as a provisioning session identifier
and will bind all other stages and related security context.
Reservation session binding that provides support for complex reservation process including required
access control and policy enforcement.

Deployment stage begins after all component resources have been reserved and includes distributionof the security context and binding the reserved resources or services to GRI as a common
provisioning session ID.
Registration&Synchronisation stage (optional) specifically targets possible scenarios with theprovisioned services migration or failover/interruption. In a simple case, the Registration stage binds
the local resource or hosting platform run-time process ID to the GRI as a provisioning session ID.
Operation stage - security services provide access control to the provisioned services and maintain theservice access or usage session.
Decommissioning stage ensures that all sessions are terminated, data are cleaned up and session
security context is recycled.

ServiceRequest(GRI)
RELAN2010

ReservSession
Binding

Deployment &RsrBindRegistr
Synchro(Opt)

Cloud Computing

Operatn
Access

Decommision

Slide_35

Relation between SSLM/SLM stages and supporting general andsecurity mechanisms
SLM
stagesRequestDesign/Reservation
Development

Deployment

Operation

Decomissioning

Process/
Activity

SLA Nego tiation

Service/Resource
Composition Reservation

Composition
Configuration

Orchestration/
SessionManagement

LogoffAccounting

Mechanisms/Methods
SLAV

Workflow

MetadataV(V)VVV

DynamicSecurityAssociatn(V)VV

AuthZ Session
Context

V(V)

VLogging(V)(V)

VRELAN2010

VV

Cloud Computing

VSlide_36

Relation between SSLM and general SLM(a)Services
Lifecycle
StagesServiceRequest(GRI)(b) Security
Services
Lifecycle
StagesDesignDevelopment
Reservation

SecServ
Request(GRI)

Reserv
SessionBinding

Deployment

Deployment &RsrBind

Registr
Synchro(Ext)

OperateMaintain

Decommision

OperatnAccess

Decommision

 Service Request stage may include SLA negotiation
 Security service instantiation may use SLA security context

RELAN2010

Cloud Computing

Slide_37GEMBus Messaging Infrastructure – Functional
Components
Composition(Workflow)

Orchestration(Workflow)

Configurat
Manager
Adaptor

EventsHandler

Composable Service Lifecycle Metadata

Reqster/
Respder

Resolver
RouterRequesterServiceReqSrv
Adaptor
RequesterService

ReqSrv
AdaptorMessage Processor

ProvSrv
AdaptorConfiguratn

LoggerInterceptor
AspectOrient

SesCtxHandler

ProvSrv
Adaptor•Registry
Service•

ProviderService•
ProviderService••
MsgSecurity
An/Az/Policy

RELAN2010

MsgAC
PEP/PDP

Security
Callout

Reqster/
Respder

Ext Security
Services

GEMBus
SecServ

Reqster/
RespderCloud Computing

LoggingServiceMessage Processor
provides actual message
parsing, analysis andtransformation
Composable/Component
services are connected via
Adaptors
GEMBus services areconnected via
Requestor/Responder (RR)
GEMBus security services
invoked from RR orcalled out

Composition&Orchestration
as GEMBus services

Slide_38

GEYSERS Architecture – Service Middleware Layer (SML)RELAN2010

Cloud Computing

Slide_39