Composable Services Architecture (CSA)
as a platform for
Dynamically Re-Configured Virtualised Services

Yuri Demchenko, UvA
GN3 Concertation meeting
16 September 2010
TERENA Offices, Amsterdam
connect • communicate • collaborate

Outline

Composable Services Architecture
Composable Services Lifecycle and Workflow
GEMBus as CSA middleware
Issues in CSA and GEMBus
Additional information (TMF SDF, WS vs REST)

GN3-JRA3-T3Discussion

Composable Services Architecture

connect • communicate • collaborate

Slide_2

Composable Services
Composable services defined as “dynamically re-configured
virtualised services”– In accordance with SOA and OSIMM (Open Group Services
Integration Maturity Model) composable services can bepositioned as a highest level
GEMBus (GEANT Multidomain Enterprise Bus) will address
multidomain issues and distributed services composition andorchestration

Composable Services Architecture

connect • communicate • collaborate

Slide_3

Composable Services Layered Model
Application Layer hosts application
related protocols
CSA primary focus on

Application Layer– Messaging Layer– Virtualisation

Virtualisation Layer
Composition & Orchestration Layer(Composition&Orchestration) Layer

Logical Abstraction Layer

Network&Transport Layer should allow
using/binding to standards
communication and security protocol

Messaging Layer

Network&Transport Layer

GN3-JRA3-T3
Discussion

Composable services are defined as“dynamically re-configuredvirtualised services” according to
OSIMM model

Composable Services Architectureconnect • communicate • collaborate

Slide_4

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)Services
Composition(&Virtualisation)

Composit&Orchestrat Layer

Logical Abstraction Layer
includes/relies oncomponent/physicalservices/resources adapters* Adaptation (sub) layer

Logical Abstraction Layer for Component Services and Resources

StorageResources

Network Infrastructure

ComputeResources

Component Services & Resources

GN3-JRA3-T3
Discussion

Composable Services Architecture

connect • communicate • collaborate

Slide_5

Composable Services Architecture –Version 0.13
Applications and User Terminals
User
ClientProxy (adaptors/containers) – Composed/Virtualised Services and Resources

Control &Management
Plane(Operation,Orchestration)

Composition
Layer/Serv

Composable Services Middleware(GEMBus)(ReservationSLA
Negotiatn)
MD SLC Registry

Logging

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

Security

Logical Abstraction Layer for Component
Services and Resources

Proxy (adaptors/containers) - Component Services and Resources

StorageResources

ComputeResources

Network Infrastructure
Component Services & Resources

GN3-JRA3-T3
Discussion

Composable Services Architecture

Control/Mngnt Links

Data Links

connect • communicate • collaborate

Slide_6

Composable Services
Lifecycle/Provisioning Workflow
Main stages/phases
Service Request/
SLA Negotiation

Composition/Reservation
Re-CompositionServiceLifecycleMetadata
Service(SL MD)

Deployment

Additional stages

Registr&Synchro
Recovery/Migration

Operation(Monitoring)

Provisiong
SessionManagnt

Re-Composition should addressincremental infrastructurechanges
Recovery/Migration can use SLMD to initiate resources resynchronisation but may require
re-composition

The whole workflow is supportedby the Service Lifecycle Metadata
Service (SL MD)

Decommissioning

GN3-JRA3-T3
Discussion

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

Composable Services Architectureconnect • communicate • collaborate

Slide_7

Composable Services Architecture –Lifecycle stages workflow
44ServUserClient43Serv

Applications and User Terminals

Serv

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

Composable Services
lifecycle/provisioning
stages13

2

Control &Management
Plane

1

Composition
Layer /Serv

Composable Services Middleware(GEMBus/GESB)(Operation,Orchestration)

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

23(ReservationSLANegotiatn)

2
MD SLC

RegistryLogging

Security

MD SLC – Service
Lifecycle Metadata3 2

Logical Abstraction Layer for Component
Services and Resources

GEMBus – GEANT
Multidomain Bus

3 244
Proxy (adaptors/containers) - Component Services and Resources

StorageResources

ComputeResources

Network Infrastructure
Component Services & Resources

GN3-JRA3-T3
Discussion

3 2

Composable Services Architecture

Control/Mngnt Links

Data Links

connect • communicate • collaborate

Slide_8

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

(3) Deployment
Control&Mngnt -> Composition/Reservation Serv -> (LogicalAbstract -> 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)

GN3-JRA3-T3
Discussion

Composable Services Architecture

connect • communicate • collaborate

Slide_9

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 Handling

Routing

Configuration

Interceptors(AspOrient)ESB

GEMBus Messaging
Infrastructure (GMI)
Composition &Orchestration

GEMBusRegistrySecurity
ServiceLogging
ServiceGEMBus Infrastructure Services

GN3-JRA3-T3
Discussion

Composable Services Architecture

GMI provides common dynamicallyconfigurable messaging infrastructure
for Composable services
communication

connect • communicate • collaborate

Slide_10

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)

Role and place for
Composition andOrchestration* Composable
services or GEMBus
infrastructure service(CSrvID,SesID)

Service 4

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

User Interface

UserClient

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

GN3-JRA3-T3
Discussion

Service 3

Service 1

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

Composable Services Architecture

CSrvID, SesID –bind component
services into theon-demand
provisioned
Composedservice NX

connect • communicate • collaborate

Slide_11

GEMBus Messaging Infrastructure – Functional
Components
Composition(Workflow)

OrchestrationComposable Service Lifecycle Metadata(Workflow)

Configurat
Manager
Adaptor

EventsHandler

Resolver
RouterReqster/
Respder

Message Processor

ReqSrv
AdaptorProvSrv
AdaptorProviderService•

LoggerConfiguratn
RequesterServiceRegistry
Service•RequesterService
ReqSrv
Adaptor•SesCtx
HandlerInterceptor
AspectOrient

ProvSrv
AdaptorProviderService••

MsgSecurity
An/Az/Policy

GN3-JRA3-T3
Discussion

MsgAC
PEP/PDP

Security
Callout

Reqster/
Respder

Ext Security
Services

GEMBus
SecServ

Reqster/
Respder

Composable Services Architecture

Message Processor
provides actual messageparsing, analysis andtransformation
Composable/Component
services are connected via
Adaptors
GEMBus services areconnected via
Requestor/Responder(RR)

LoggingService

GEMBus security
services invoked from
RR or called out

Composition&Orchestration as GEMBus services

connect • communicate • collaborate

Slide_12

Multidomain issues in CSA

Can be addressed in the properly layered infrastructure andmessage routing– CSA middleware and GEMBus Messaging Infrastructure
End-Point Reference (EPR) and use of Fully Qualified Names(FQN)
Dynamic security federation/associations and provisioning session
managementGN3-JRA3-T3
Discussion

Composable Services Architecture

connect • communicate • collaborate

Slide_13

CSA and Integration with Network
Resource Provisioning
Full convergence is possible if CSA will integrate topology based
network infrastructure provisioning– Subject of current cooperation with GEYSERS Project thedevelops infrastructure services virtualisation architecture an
don-demand provisioning
CSA should investigate Cloud middleware use, in particular,
RESERVOIR and Claudia Frameworks, future GEYSERS
infrastructure

GN3-JRA3-T3
Discussion

Composable Services Architecture

connect • communicate • collaborate

Slide_14

Additional InformationTMF SDF Lifecycle Management model
Proposed Security SLM modelWS vs REST -> UPR vs URI

Composable Services Architecture

connect • communicate • collaborate

Slide_15

TMF Service Delivery Framework (SDF)

Goal: Automation of the whole service delivery and operation process(TMF SDF, http://www.tmforum.org/ServiceDeliveryFramework/4664/home.html)
End-to-end service management in a multi-service providers environment
End-to-end service management in a composite, hosted and/orsyndicated service 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

GN3-JRA3-T3
Discussion

Composable Services Architecture

connect • communicate • collaborate

Slide_16

SDF Reference Architecture(refactored from SDF)
Design1
SDF Service Design 6
Management (ISS)

DeploySDF Service
Repository (ISS)910
SDF Service
Lifecycle Metadata
Repository (ISS)171
1
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

16
SDF Service Quality/
Problem Mngnt (MSS)12
1

SDF Service Resource
3Fulfillment (ISS)13

SDF Service Resource 4Monitor (ISS)7
SDF Service Usage
Mngnt (MSS)SDF MSS

GN3-JRA3-T3
Discussion

Composite Services
provisioned on-demand

4

1
SDF Service Resource5Usage Monitor (ISS)SDF ISS

Composable Services Architecture

8

1 – 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/ProblemManagement
7 - Service Usage Monitor
12 - Service State Monitor
13 - Service Resource Fulfillment
14 - Service Resource Monitor
15 - Resource Usage Monitor

connect • communicate • collaborate

Slide_17

GEYSSERS Service Delivery Workflow(WP2 Deliverable D2.1)

Service Request/
SLA Negotiation

Replanning

Services
Provisioning
Workflow
by VIP

Service Request/
SLA Negotiation

Geysers SDF supports
both Geysers
infrastructure development
and deployments and its
operation for on-demand
Infrastructure services
provisioning by VIO

Composition/
Reservation

Planning/Design

Re-Composition

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

Operation&Monitoring(by VIO)

Registr&Synchro
Network+ITServices
Provisioning
Workflow
by VIO

Recovery/
Migration

Operation(Monitoring)

Decommissioning
Decommissioning

GN3-JRA3-T3
Discussion

Composable Services Architecture

connect • communicate • collaborate

Slide_18

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
distribution of the security context and binding the reserved resources or services to GRI as acommon provisioning session ID.
Registration&Synchronisation stage (optional) specifically targets possible scenarios with theprovisioned services migration or failover/interruption. In a simple case, the Registration stagebinds 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 andmaintain the service access or usage session.
Decommissioning stage ensures that all sessions are terminated, data are cleaned up andsession security context is recycled.

ServiceRequest(GRI)
GN3-JRA3-T3
Discussion

ReservSession
Binding

Deployment &RsrBind

Registr
Synchro(Opt)

OperatnAccess

Composable Services Architecture

Decommisionconnect • communicate • collaborate

Slide_19

Relation between SSLM/SLM stages andsupporting general and security mechanisms
SLM
stagesRequestProcess/Activity

SLA
tiationNego

Design/Reservation
Development

Deployment

Operation

Decomission
ingService/Composition
Reservation

Composition
Configuration

Orchestration/Session
Management

LogoffAccounting

Resource

Mechanisms/Methods
SLA

V

Workflow

Metadata

V(V)

V

V

V

V

V

Dynamic
Security
Associatn

(V)

V

V

AuthZ Session
Context

V(V)V

Logging

(V)

(V)

V

GN3-JRA3-T3
Discussion

Composable Services ArchitectureV
connect • communicate • collaborate

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

SecServ
Request(GRI)

ReservSession
Binding

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

GN3-JRA3-T3
Discussion

Composable Services Architecture

connect • communicate • collaborate

Slide_21

REST vs Web Services = URI vs EPR

GEMBus uses own registered namespace branch– urn:geant:gembus
CSA requires state management and communication betweenservices– Basic functionality to be supported by WSRF and EPR– Keep EPR and URI/REST mapping
End Point Reference is a part of WS-Addressing and complements
WSDL to support the following scenarios– "Dynamic generation and customization of service endpoint
descriptions.
– Identification and description of specific service instances that arecreated as the result of stateful interactions.
– Flexible and dynamic exchange of endpoint information in tightly
coupled environments where communicating parties share a set ofcommon assumptions about specific policies or protocols that areused during the interaction."
GN3-JRA3-T3
Discussion

Composable Services Architecture

connect • communicate • collaborate

Slide_22

Example EPR and mapping to URI

EPR example with service properties and parameters<wsa:EndpointReference><wsa:Address>http://clarin.geant.net/registry</wsa:Address><wsa:ReferenceProperties><gembus:domainID>clarin.geant.net</gembus:domainID><gembus:ServiceRegistryKey>K2349456076</gembus:ServiceRegistryKey></wsa:ReferenceProperties><wsa:ReferenceParameters><gembus:sessionID>173945623490764234854</gembus:sessionID><gembus:sessionDuration>8460</gembus:sessionDuration></wsa:ReferenceParameters><wsa:PortType>gembus:RegistryPortType</wsa:PortType> ?
<wsa:ServiceName PortName="RegistryUpdate">
urn:geant:gembus:registry:update-service</wsa:ServiceName></wsa:EndpointReference>

Maping to URI string:
http://clarin.geant.net/registry/update-service/ServiceRegistryKey=
K2349456076/sessionID=173945623490764234854;sessionDuration=8460
Composable Services Architecture

connect • communicate • collaborate

Slide_23