Defining InterCloud Architecture
Framework (ICAF)
forInteroperability and Integration
Yuri Demchenko
SNE Group, University of Amsterdam
CloudComputing2012
22--23 July 2012, Nice, France

InterCloud Architecture 2012

InterCloud Architecture Framework1Outline• Cloud Computing Architecture research at SNE group (Univ Amsterdam)• General use cases for Intercloud Architecture• Related standardisation initiatives– NIST Cloud Computing Reference Architecture (CCRA) and extension for network
aware cloud resources provisioning– IEEE Intercloud Working Group– ITU-T Cloud Interest Group final report– OGF ISOD-RG infrastructure services definition– IETF Internet-Draft on Cloud Architecture Framework• Intercloud Architectural Framework (ICA/ICAF) components––––

Multi-layer/Layered Cloud Services Model (CSM)
Intercloud Control and Management Plane (ICCMP)
Intercloud Federation Framework (ICFF)Intercloud Operations Framework (ICAF)• Abstract Model for Cloud IaaS Provisioning• Further research and standardisation contribution

InterCloud Architecture 2012

InterCloud Architecture Framework

Slide_2

SNE Cloud Architecture ResearchIntercloud Architecture for Interoperability and Integration, Release 1, Draft
Version 0.4. SNE Technical Report 2012-03-02, 19 June 2012
http://staff.science.uva.nl/~demch/worksinprogress/sne2012-techreport-12-05-intercloud-architecturedraft04.pdf

Main contributing research:(1) Generic Cloud IaaS Architecture, Release 1, 15 April 2011
Published as http://staff.science.uva.nl/~demch/worksinprogress/sne2011-techreport-2011-03-clouds-iaasarchitecture-release1.pdf

•
•
•
•

Virtual Infrastructure Composition and Management (VICM) layer
Infrastructure Services Modeling Framework (ISMF)
Composable Services Architecture (CSA)
Service Delivery Framework (SDF)(2) InterCloud OS/Middleware (low level Intercloud integration)• Targeting for Intercloud BGP-like protocol(3) Security Infrastructure for Cloud (dynamically provisioned)•••

Dynamic Access Control Infrastructure (DACI)Contributing to cloud standardisation by OGF, NIST, IEEE, IETF
Implementation – EU projects GEYSERS, GEANT3– Telco and NREN driven – core network and last mile

InterCloud Architecture 2012

InterCloud Architecture Framework3General use cases for Intercloud Architecture• Clouds are evolving as a common way of provisioning
infrastructure services on-demand– In this way, clouds add a new type of services, in addition and on the topof currently existing network based and distributed services• Intercloud Architecture Framework (ICAF) provides a framework to
support provisioning of cloud based project oriented infrastructures
on-demand and distributed virtualised applications mobility– Hybrid Cloud/Grid e-Science collaborative environment• Scientific Data Infrastructure for Big Data

– Enterprise/campus cloud infrastructure evolution andmigration/mobility– Infrastructure disaster recovery (Vodafone NL Datacenter Incident)• Data require supporting infrastructure– Educational Lab deployment in clouds• ICAF intends to open Cloud market to more players and rise socalled “cloud curtain”
InterCloud Architecture 2012

InterCloud Architecture Framework4InterCloud: Related standardisation activities• OGF ISOD-RG– BCP on existing on-demand network and cloud infrastructure resources
provisioning systems (including GEYSERS)• NIST Cloud definition (NIST SP 800-145), and Cloud Computing
Reference Architecture (CCRA), v1.0 (NIST SP 500-292)• IEEE - WGs on InterCloud issues and Cloud Profiles– IEEE ICWG/2302 WG - Intercloud WG (ICWG) Working Group
http://standards.ieee.org/develop/wg/ICWG-2302_WG.html• ITU-T Focus Group on Cloud: Technical Report (Part 1 to 7)
http://www.itu.int/en/ITU-T/focusgroups/cloud/Documents/FG-coud-technical-report.zip• IETF Internet Drafts– Cloud Reference Framework. Internet Draft, by B. Khasnabish, J. Chu, S. Ma, Y.
Meng, N. So, P. Unbehagen, M. Morrow, M. Hasan, Y. Demchenko
http://tools.ietf.org/html/draft-khasnabish-cloud-reference-framework-03.txt– Cloud Service Broker, Internet Draft by Shao Weixiang, Hu Jie, Bhumip
Khasnabish.
http://tools.ietf.org/html/draft-shao-opsawg-cloud-service-broker-03.txt

InterCloud Architecture 2012

InterCloud Architecture Framework5Work on I-Draft “Cloud Reference Framework”(Version 0.3)
http://tools.ietf.org/html/draft-khasnabish-cloud-reference-framework-03.txt
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Cloud Services Reference Model . . . . . . . . . . . . . . . 6
3.1. HORIZONTAL LAYERS . . . . . . . . . . . . . . . . . . . . 7
3.1.1. Application/Service Layer . . . . . . . . . . . . . . 7
3.1.2. Resources Control Layer . . . . . . . . . . . . . . . 8
3.1.3. Resources Abstraction and Virtualization Layer . . . . 9
3.1.4. Physical Resources Layer . . . . . . . . . . . . . . . 10
3.2. VERTICAL LAYERS (planes?) . . . . . . . . . . . . . . . . 10
3.2.1. Cloud Management Layer . . . . . . . . . . . . . . . . 10
4. Inter-Cloud Framework . . . . . . . . . . . . . . . . . . . . 17
4.1. Inter-Cloud Requirements . . . . . . . . . . . . . . . . . 17
4.2. Intercloud Framework Components
4.3. Intercloud Control and Management Plane (ICCMP)
4.4. Intercloud Federation Framework (ICFF)
4.5. Intercloud Operation Framework (ICOF)
5. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.1. Virtual Network Management . . . . . . . . . . . . . . . . 19
5.2. Telecom Network Virtualization . . . . . . . . . . . . . . 19
5.3. Virtual Data Center . . . . . . . . . . . . . . . . . . . 21
5.4. Security infrastructure for on-demand provisioned
cloud-based services/infrastructures
6. Security Framework for Clouds . . . . . . . . . . . . . . . . 22
7. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . 24
8. Security Considerations . . . . . . . . . . . . . . . . . . . 25
9. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 26
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
12. Normative references . . . . . . . . . . . . . . . . . . . . . 28

InterCloud Architecture 2012

InterCloud Architecture Framework

B. Khasnabish(ZTE USA)
J. ChuS. Ma
Y. Meng(ZTE)
N. So(Verizon)P. Unbehagen
Avaya
M. Morrow(Cisco Systems
Switzerland)
M. Hasan(Cisco Systems)
Y.Demchenko
University of
Amsterdam

Version 0.3 – 29 June 2012
Version 0.4 – End July 2012
Version 0.5 – October 2012
(To be considered)6Intercloud Architecture - Requirements
Intercloud Architecture (ICA) should address interoperability and integrationof different cloud service platforms and multi-cloud integration, including withlegacy campus/enterprise infrastructure• Be compatible and provide multi-layer integration of existing cloudservice models – IaaS, PaaS, SaaS and Apps clouds• Facilitate interoperable and measurable intra-provider infrastructures• Provide a framework for heterogeneous inter-cloud federation• Common Intercloud Control Plane and signalling for better cloud services
and network integration• Explicit/Guaranteed intra- and inter-cloud network infrastructure
provisioning and performance (as NaaS service model)• Support existing Cloud Provider operational and business models andprovide a basis for new forms of services provisioning and operation

InterCloud Architecture 2012

InterCloud Architecture Framework

7

General use case for infrastructure provisioning:
Workflow => Logical (Cloud) Infrastructure (1)Enterprise/Scientific workflow
Storage
Data

SpecialProc 1
Data
Filtering

Input
Data

VisualPresent
SpecialProc 2

Instrum.
Data

Campus A

Data
Archive

Visualisation

Visualisation

CE

User
Group A

Campus B

CE

User
User
User

User
User
User
VR6

Cloud 2 PaaS

VR2

User
Group B

VR7
VR4

VR1

VR5

Resource/
Service
ProviderVR3Enterprise/Project basedIntercloud Infrastructure

Cloud 1 IaaS

Resource/
Service
Provider
CN

CN
CN

CN
CN

CN

Cloud PaaS Provider

CN
CN

CN

CN
CN

Cloud IaaS Provider

InterCloud Architecture 2012

InterCloud Architecture Framework

8General use case for infrastructure provisioning:
Workflow => Logical (Cloud) Infrastructure (2)Enterprise/Scientific workflow
Storage
Data

SpecialProc 1
Data
Filtering

Input
Data

VisualPresent
SpecialProc 2

Instrum.
Data

Campus A

Data
Archive

Visualisation

Visualisation

CE

User
Group A

Campus B

CE

User
User
User

User
User
User
VR6

Cloud 2 PaaS

VR2

User
Group B

VR7
VR4

VR1

VR5

Resource/
Service
ProviderVR3Enterprise/Project basedIntercloud Infrastructure

Cloud 1 IaaS

Resource/
Service
Provider
CN

CN
CN

CN
CN

CN

Cloud PaaS Provider

CN
CN

CN

CN
CN

Cloud IaaS Provider

InterCloud Architecture 2012

InterCloud Architecture Framework

9General use case for infrastructure provisioning:
Logical Infrastructure => Network Infrastructure (1)Resource and Cloud Provider Domains
Cloud 1 IaaS
VR3

VR1

Cloud 2 PaaS

VR5

VR7

Campus A
Infrastructure

Campus B
Infrastructure

VR2

Campus A

VR4

VR6

Cloud Carrier Network Infrastructure

Visualisation

Visualisation

CE

User
Group A

Campus B

CE

User
User
User

User
User
User
VR6

Cloud 2 PaaS

VR2

User
Group B

VR7
VR4

VR1

VR5

Resource/
Service
ProviderVR3Enterprise/Project basedIntercloud Infrastructure

Cloud 1 IaaS

Resource/
Service
Provider
CN

CN
CN

CN
CN

CN

Cloud PaaS Provider

CN
CN

CN

CN
CN

Cloud IaaS Provider

InterCloud Architecture 2012

InterCloud Architecture Framework

10General use case for infrastructure provisioning:
Logical Infrastructure => Network Infrastructure (2)Resource and Cloud Provider Domains
VR3

VR1

VR5

VR7

Campus A
Infrastructure

Campus B
Infrastructure

VR2

VR4

VR6

Network Provider 1

Campus A

Visualisation

Network Provider 2

Visualisation

CE

User
Group A

Campus B

CE

User
User
User

User
User
User
VR6

Cloud 2 PaaS

VR2

User
Group B

VR7
VR4

VR1

VR5

Resource/
Service
ProviderVR3Enterprise/Project basedIntercloud Infrastructure

Cloud 1 IaaS

Resource/
Service
Provider
CN

CN
CN

CN
CN

CN

Cloud PaaS Provider

CN
CN

CN

CN
CN

Cloud IaaS Provider

InterCloud Architecture 2012

InterCloud Architecture Framework

11

Intercloud Applications Interaction (1) - ICCMP
IaaS Domain

Cloud Layers
Layer 7 - Applications

User
definedPlatform
andSW&Apps

InterCloud Control andManagement Plane(ICCMP)

PaaS Domain
Userdefined
SW&Apps

Layer 6 – SaaS/Apps
Layer 5 - PaaS
Cloud based Platform

Layer 4 - PaaS

Layer 4 - IaaS
Cloud Infrastructure

Layer 3 - IaaS

ProviderdefinedInfrastr.
andVirt&OS
Platform

Layer 3 – Composition

Campus A

Providerdefined
Virt&OS
Platform

Visualisation

Layer 2 - Virtualisation

Visualisation

Layer 1 - Physical
HW Platform/Network

CE

User
Group A

Campus B

CE

User
User
User

User
User
User
VR6

Cloud 2 PaaS

VR2

User
Group B

VR7
VR4

VR1

VR5

Resource/
Service
ProviderVR3Enterprise/Project basedIntercloud Infrastructure

Cloud 1 IaaS

Resource/
Service
Provider
CN

CN
CN

CN
CN

CN

Cloud PaaS Provider

CN
CN

CN

CN
CN

Cloud IaaS Provider

InterCloud Architecture 2012

InterCloud Architecture Framework

12

Intercloud Applications Interaction (2) - ICFFIntercloud Federation
Infrastructure

IaaS Domain

PaaS Domain
Registry
Discovery

User
SW&Apps

Layer C3-IaaS

BrokerBrokerGW

LayerC4-PaaS

Trust
Broker

ProviderVirt&OS
PlatformCampus A

User
SW&Apps

GW
ProviderVirt&OS
Platform

IdP
Trust
BrokerAttribs

Visualisation

Visualisation

Trust

CE

User
Group A

Campus B

CE

User
User
User

User
User
User
VR6

Cloud 2 PaaS

VR2

User
Group B

VR7
VR4

VR1

VR5

Resource/
Service
ProviderVR3Enterprise/Project basedIntercloud Infrastructure

Cloud 1 IaaS

Resource/
Service
Provider
CN

CN
CN

CN
CN

CN

Cloud PaaS Provider

CN
CN

CN

CN
CN

Cloud IaaS Provider

InterCloud Architecture 2012

InterCloud Architecture Framework

13

Intercloud Applications Integration (3) - ICOF

Storage
Data

SpecialProc 1

Data
Archive

Data
Filtering

Input
Data

Business Processes Management and Services
Operation Support• SLA Management• Business roles and Actors• Business level Service Registry and Broker

Intercloud Federation
Infrastructure
Registry
User
SW&AppsVisualPresent

Layer C3-IaaS

Disco-very

BrokerBrokerGW

LayerC4-PaaS

Trust
Broker

Provider Virt&OS
Platform

SpecialProc 2

Instrum.
Data

Provider Virt&OS
Platform

Layer 6 – SaaS/Apps
Layer 5 - PaaS
Cloud based Platform

Visualisation

Visualisation

ProviderdefinedInfrastr.
andVirt&OS
Platform

Layer 3 – Composition
Providerdefined
Virt&OS
Platform

CE

Trust

Layer 4 - PaaS

Layer 4 - IaaS
Cloud Infrastructure

Layer 3 - IaaS

Trust
BrokerPaaS Domain
Userdefined
SW&Apps

Layer 7 - Applications

User
definedPlatform
andSW&Apps

Layer 2 - Virtualisation

User
User
User

User
User
User
VR6

Campus B

CE

Layer 1 - Physical
HW Platform/Network

User
Group A

GW

IdP
Attribs

IaaS Domain Cloud Layers

Campus A

User
SW&AppsCloud 2 PaaS

VR2

User
Group B

VR7
VR4

VR1

VR5

Resource/
Service
ProviderVR3Enterprise/Project basedIntercloud Infrastructure

Cloud 1 IaaS

Resource/
Service
Provider
CN

CN
CN

CN
CN

CN

Cloud PaaS Provider

CN
CN

CN

CN
CN

Cloud IaaS Provider

InterCloud Architecture 2012

InterCloud Architecture Framework

14

InterCloud Architecture components• Multi-layer Cloud Services Model (CSM)– Combines IaaS, PaaS, SaaS into multi-layer model with inter-layer interfaces– Including interfaces definition between cloud service layers and virtualisation
platform• InterCloud Control and Management Plane (ICCMP)– Allows signaling, monitoring, dynamic configuration and synchronisation of the
distributed heterogeneous clouds– Including management interface from applications to network infrastructure andvirtualisation platform• InterCloud Federation Framework (ICFF)– Defines set of protocols and mechanisms to ensure heterogeneous clouds
integration at service and business level– Addresses Identity Federation, federated network access, etc.

• InterCloud Operations Framework (ICOF)– RORA model: Resource, Ownership, Role, Action•

RORA model provides basis for business processes definition, SLA and access control– Broker and federation operation
InterCloud Architecture 2012

InterCloud Architecture Framework

15

Multilayer Cloud Services Model (CSM)
CSM layers
Layer C7
User
Client/ Application

User Applications

Security InfrastructureManagement

IaaS

Layer C6
Cloud Applications(SaaS)SaaS

PaaS

SaaS-PaaS IF
Layer C5
Cloud Platform(PaaS)

PaaS-IaaS Interface
IaaS – Virtualisation Platform Interface

Cloud Management
Software(Functional Definition Proposed)

Virtualisation Platform

Cloud Management Software/Platforms
OpenNebula

OpenSta
ck

KVM

VM

VM

VPN

Other
CMS

XEN

VMWareNetwork
Virt

Proxy (adaptors/containers) - Component Services and Resources
StorageResources

ComputeResources

Network
Infrastructure
Hardware/Physical Resources

InterCloud Architecture 2012

InterCloud Architecture Framework

Layer C4
Cloud
Infrastructure(IaaS)
Layer C3
Virtual Resources
Composition andControl(Orchestration)(C7) User Client/Application(C6) Cloud Application(SaaS)(C5) Cloud Platform (PaaS)(C4) Cloud Infrastructure(IaaS)(C3) Virtual Resources
Composition andOrchestration(C2) Virtualisation Layer(C1) Hardware platform anddedicated network
infrastructure

Layer C2
Virtualisation

Layer C1
PhysicalHardwarePlatform andNetwork

Control/
Mngnt Links

Data Links

Slide_16

InterCloud Control and Management Plane(ICCMP)• Supports messages delivery/routing, signaling, monitoring,
dynamic configuration and synchronisation between the distributed
heterogeneous cloud instances• Includes management interfaces from upper layers andapplications to network infrastructure and virtualisation platform(virtualised resources)• Layer 1 - Layer 4 interfaces are being developed and prototyped
in the framework of the GEYSERS projectInterCloud Architecture 2012

InterCloud Architecture Framework17

Intercloud Control and Management (1)IaaS Domain

Cloud Layers
Layer 7 - Applications

User
definedPlatform
andSW&Apps

InterCloud Control andManagement Plane(ICCMP)

PaaS Domain
Userdefined
SW&Apps

Layer 6 – SaaS/Apps
Layer 5 - PaaS
Cloud based Platform

Layer 4 - PaaS

Layer 4 - IaaS
Cloud Infrastructure

Layer 3 - IaaS

ProviderdefinedInfrastr.
andVirt&OS
Platform

Layer 3 – Composition

Campus A

Providerdefined
Virt&OS
Platform

Visualisation

Layer 2 - Virtualisation

Visualisation

Layer 1 - Physical
HW Platform/Network

CE

User
Group A

Campus B

CE

User
User
User

User
User
User
VR6

Cloud 2 PaaS

VR2

User
Group B

VR7
VR4

VR1

VR5

Resource/
Service
ProviderVR3Enterprise/Project basedIntercloud Infrastructure

Cloud 1 IaaS

Resource/
Service
Provider
CN

CN
CN

CN
CN

CN

Cloud PaaS Provider

CN
CN

CN

CN
CN

Cloud IaaS Provider

InterCloud Architecture 2012

InterCloud Architecture Framework

18

Intercloud Control and Management (2)IaaS Domain

Cloud Layers

PaaS Domain

Layer 7 – Applications
User defined Applications

User defined
Platform
andSW&Apps

Layer 6 – SaaS/Apps
Cloud based Apps/Software
Layer 5 - PaaS
Cloud based Platform

Layer 4 - IaaS

Layer 4 - IaaS
Cloud Infrastructure

IaaS Mware
ProviderdefinedOS&VirtPlatform

Layer 3 - Composition
Virtual Resources Composition
Layer 2 - Virtualisation
Resources Abstraction andVirtualisation

User defined
SW&Apps

Layer 5 - PaaS
PaaS Mware

ProviderdefinedInfrastructure
andOS&VirtPlatform

Layer 1 - Physical
HW Platform/Network

InterCloud Control and Management Plane (ICCMP)
Standard Interface

InterCloud Architecture 2012

Non-standard/proprietary Interface

InterCloud Architecture Framework

19InterCloud Control and Management Plane(ICCMP)• Allows signaling, monitoring, dynamic configuration andsynchronisation of the distributed heterogeneous clouds• Including management interface from applications to network
infrastructure and virtualisation platform• Main functional components include– Cloud Resource Manager– Network Infrastructure Manager• Possible ICCMP Interfaces include– Signaling– Control– Monitoring– Management– Location– Message routing
InterCloud Architecture 2012

InterCloud Architecture Framework

20

InterCloud Federation Framework (ICFF)• Defines set of protocols and mechanisms to ensure heterogeneousclouds integration at service and business level• Addresses Identity Federation, federated network access, etc.
• Main functional components include– Service and Trust brokers– Intercloud gateway including attribute/namespace translator
•

–
–
–
–

Attribute/namespace resolver

Service Registry
Service discovery service
Identity provider
Trust manager/router• Possible ICFF Interfaces
–
–
–
–
–

Naming, Addressing and Translation (if/as needed)
Publishing
Discovery
Attributes management
Trust/key management

InterCloud Architecture 2012

InterCloud Architecture Framework21

InterCloud Operations Framework (ICOF)• Defines the main roles and actors– RORA model: Resource, Ownership, Role, Action• Provides basis for business processes definition, SLA management and access control policy
definition• Broker and Federation operation• Main functional components include– Cloud Service Provider, Cloud Operator, Cloud (physical) Resource provider,
Cloud Carrier– Service Registry– Service Broker• Possible ICOF Interfaces– Provisioning, Deployment, Decommissioning/Termination– SLA management and negotiation– Services Lifecycle management– Services deployment
InterCloud Architecture 2012

InterCloud Architecture Framework22Main Actors in Cloud/InterCloud Architecture
•
•
•
•
•
•
•
•
•

Cloud Service Provider
Intercloud (Cloud Service) Operator
Cloud Customer
Cloud User
Cloud Carrier
Cloud Broker
Cloud Auditor
Cloud Resource Provider
Physical Resource Provider

Ownership/Management modelneeds to be applied to these actors
using extended RORA model– Can also be a “fixed” resources provider

InterCloud Architecture 2012

InterCloud Architecture Framework

23Implementation: Architectural Framework for
Cloud IaaS
• Abstracted from the GEYSERS LICL (Logical Infrastructure Composition
Layer) architecture• Includes Composable Services Architecture (CSA) being developed in
GEANT3 JRA3
• Incorporates RDF based Network and Infrastructure Description
Languages (NDL, NML, INDL) research at SNE/UvA• Includes the following main components– Infrastructure Services Modeling Framework (ISMF)– Composable Services Architecture (CSA)– Service Delivery Framework (SDF)• Additional components (orthogonal)– Cloud Security Infrastructure– Control and Management Plane
Published as SNE Technical Report (2011)
http://staff.science.uva.nl/~demch/worksinprogress/sne2011-techreport-2011-03-clouds-iaasarchitecture-release1.pdf

InterCloud Architecture 2012

InterCloud Architecture Framework

24

GEYSERS Layered Architecture – CSM and ICCMPService Consumer

Service Middleware Layer (SML)
Virtual IT Management (VITM)

Inter-layer
communication

Virtual Infrastructure
Virtual IT nodecontroller

Virtual Resource Pool

Virtual Network nodecontroller
Virtual IT resource

Logical Infrastructure
Composition Layer (LICL)

IT-aware Network Control Plane (NCP+)

Physical IT
resource

Virtual Network resource
Physical Network
resource

Physical Infrastructure•

Developed and implemented in the GEYSERS project http://www.geysers.eu/

InterCloud Architecture 2012

InterCloud Architecture Framework

25

Abstract (Cloud) IaaS Provisioning Model
Virtual Infrastructure (VI) (operated by VIO1)
VRI2
Application/Service Layer
Service Middleware Layer (SML)

User/
Applic A

VRI5
VRI4

VRI1

VRI6

User/
Applic B

VRI3
VI Comp & Mngnt (Upper LICL)

SLC
Metadada

Logical Abstraction Layer

PR Virtualis & Mngnt (Lower LICL)
Pi/PR Adaptation Layer
Resource
ConfigSLA/
SLMSecurity
Context

VR1
IT infrastructure virtualisation

Composition
Logical Rsr

Ctrl & Mngnt(Orchestratn)

AAI/Policy
Security

VI Operator
Layer

VIO1

VI/VR Adaptation Layer

VR2

VR3

VIProvider1

PIP1

PIP2

ND-PIP1

ND-PIP2

VR4

VR5

VIProvider2

PIP3

PIP4

Pi/PR Layer

Network Infrastructure Provisioning

UserND-A

ND-PIP3-PIP4

VR6

VI Provider
Layer

PI Provider
Layer

UserND-B

Network Control Plane
Resource
ConfigSLA/
SLMSecurity
Context

ND-VIP1

ND-VIP2

Network Domain ND-VIO1
Network Infrastructure virtualisation and instantiation

InterCloud Architecture 2012

InterCloud Architecture Framework

LegendND* - Network Domain
VIR* - VI Resource (deployed)
VR – Virtual Resource
LR – Logical Resource
PR – Physical Resource

26

Abstract (Cloud) IaaS Provisioning Model
Virtual Infrastructure (VI) (operated by VIO1)
VRI2
Application/Service Layer
Service Middleware Layer (SML)

User/
Applic A

VRI5
VRI4

VRI1

VRI6

User/
Applic B

VRI3
VI Composition & Management Layer

SLC
Metadada

Logical Abstraction Layer

PR Virtualis & Mngnt (Lower LICL)
Pi/PR Adaptation Layer
Resource
ConfigSLA/
SLMSecurity
Context

VR1
IT infrastructure virtualisation

Composition
Logical Rsr

Ctrl & Mngnt(Orchestratn)

AAI/Policy
Security

VI Operator
Layer

VIO1

VI/VR Adaptation Layer

VR2

VR3

VIProvider1

PIP1

PIP2

ND-PIP1

ND-PIP2

VR4

VR5

VIProvider2

PIP3

PIP4

Pi/PR Layer

Network Infrastructure Provisioning

UserND-A

ND-PIP3-PIP4

VR6

VI Provider
Layer

PI Provider
Layer

UserND-B

Network Control Plane
Resource
ConfigSLA/
SLMSecurity
Context

ND-VIP1

ND-VIP2

Network Domain ND-VIO1
Network Infrastructure virtualisation and instantiation

InterCloud Architecture 2012

InterCloud Architecture Framework

LegendND* - Network Domain
VIR* - VI Resource (deployed)
VR – Virtual Resource
LR – Logical Resource
PR – Physical Resource

27

Abstract (Cloud) IaaS Provisioning Model
Virtual Infrastructure (VI) (operated by VIO1)
VRI2
Application/Service Layer
Service Middleware Layer (SML)

User/
Applic A

VRI5
VRI4

VRI1

VRI6

User/
Applic B

VRI3
VI Comp & Mngnt (Upper LICL)

SLC
Metadada

Logical Abstraction Layer

PR Virtualisation & Management

en

Pi/PR Adaptation Layer
Resource
ConfigSLA/
SLMSecurity
Context

VR1
IT infrastructure virtualisation

Composition
Logical Rsr

Ctrl & Mngnt(Orchestratn)

AAI/Policy
Security

VI Operator
Layer

VIO1

VI/VR Adaptation Layer

VR2

VR3

VIProvider1

PIP1

PIP2

ND-PIP1

ND-PIP2

VR4

VR5

VIProvider2

PIP3

PIP4

Pi/PR Layer

Network Infrastructure Provisioning

UserND-A

ND-PIP3-PIP4

VR6

VI Provider
Layer

PI Provider
Layer

UserND-B

Network Control Plane
Resource
ConfigSLA/
SLMSecurity
Context

ND-VIP1

ND-VIP2

Network Domain ND-VIO1
Network Infrastructure virtualisation and instantiation

InterCloud Architecture 2012

InterCloud Architecture Framework

LegendND* - Network Domain
VIR* - VI Resource (deployed)
VR – Virtual Resource
LR – Logical Resource
PR – Physical Resource

28

Abstract (Cloud) IaaS Provisioning Model
Virtual Infrastructure (VI) (operated by VIO1)
VRI2
Application/Service Layer
Service Middleware Layer (SML)

User/
Applic A

VRI5
VRI4

VRI1

VRI6

User/
Applic B

VRI3
VI Comp & Mngnt (Upper LICL)

Composition
Logical Rsr

SLC
Metadada

VR1
IT infrastructure virtualisation

Ctrl & Mngnt(Orchestratn)

AAI/Policy
Security

Logical Abstraction Layer

PR Virtualis & Mngnt (Lower LICL)
Pi/PR Adaptation Layer
Resource
ConfigSLA/
SLM

VI Operator
Layer

VIO1

VI/VR Adaptation Layer

Security
Context

VR2

VR3

VIProvider1

PIP1

PIP2

ND-PIP1

ND-PIP2

VR4

VR5

VIProvider2

PIP3

PIP4

Pi/PR Layer

Network Infrastructure Provisioning
Network Control Plane
Resource
ConfigSLA/
SLMSecurity
Context

UserND-A

ND-PIP3-PIP4

ND-VIP1

ND-VIP2

Network Domain ND-VIO1
Network Infrastructure virtualisation and instantiation

InterCloud Architecture 2012

InterCloud Architecture Framework

VR6

VI Provider
Layer

PI Provider
Layer

UserND-B
LegendND* - Network Domain
VIR* - VI Resource (deployed)
VR – Virtual Resource
LR – Logical Resource
PR – Physical Resource

29Virtual Infrastructure Composition and Management• Main actors involved into provisioning process– Physical Infrastructure Provider (PIP)– Virtual Infrastructure Provider (VIP)– Virtual Infrastructure Operator (VIO)• Virtual Infrastructure Composition and Management (VICM) layer
includes– VICM middleware - defined as CSA– Logical Abstraction Layer and the VI/VR Adaptation Layer facing
correspondingly lower PIP and upper Application layer.

• The infrastructure provisioning process is defined by the Service Delivery
Framework (SDF)– Defines services lifecycle• VICM redefines Logical Infrastructure Composition Layer (LICL)
proposed by GEYSERS project– Basic functionality is implemented as GEMBus/ESB/CSA
InterCloud Architecture 2012

InterCloud Architecture Framework

30

Services Lifecycle/Provisioning Workflow•

Main stages/phases–

Service Request/(SLA Negotiation)––
Composition/
Reservation(SLA enforcement)
Re-Planning/
Re-Composition

Service
Lifecycle
Metadata
Service(SL MD)––•

Deployment

Additional stages–

Registr&Synchro(Security Bootstrap)
Recovery/
Migration

Operation(Monitoring)(SLA enforcement)–

Provisiong
SessionManagnt••

Decommissioning(Security Recycling)

InterCloud Architecture 2012

InterCloud Architecture Framework

Service Request (including SLA
negotiation)
Composition/Reservation (akadesign)Deployment, including
Reqistration/Synchronisation
Operation (including Monitoringand SLA enforcement)
Decommissioning (including
Dynamic Security Associations
destroying/recycling)
Re-Planning/Re-Composition
should address incremental
infrastructure changes
Recovery/Migration can use SLMD to initiate resources resynchronisation but may require recomposition

The whole workflow is supported by
the Service Lifecycle Metadata
Service (SL MD)
Provisioning session provides aframework for services context andsecurity context management

Slide_31

Summary and Future works• The proposed ICAF is based on existing standards
and proposes their integration and extension– Includes 4 components: CSM, ICCMP, ICFF, ICOF
• Addresses cloud services/infrastructure lifecycle management• Future research and development primarily focusedon inter-layer and inter-cloud interfaces definition– Re-factor GEYSERS Infrastructure virtualisationinterfaces– Testbeds: IaaS (GEYSERS) and PaaS (GEANT3)• Standardisation activity in IETF, OGF, TMF– Partnership with industry
InterCloud Architecture 2012

InterCloud Architecture Framework32

Questions and Discussion

InterCloud Architecture 2012

InterCloud Architecture Framework33

Additional Information• NIST Cloud definition and standardisation activity• Useful links on Cloud standardisation and practiceInterCloud Architecture 2012

InterCloud Architecture Framework

34

ISMF – Virtual Resource Lifecycle
Network Segment
Network Segment

VRs{LR0} -> LR2
Planning
Composition
Reservation

Composed

LRs

Registered.

PRs

Physical Resource

PR-LR1
Config&
InstantiationLR0
Re-usable(Published)
PRs
PIP1

InterCloud Architecture 2012

Virtual Infrastructure

Deployed

Logical Resource

LR2 -> VR
VI Deployment

Virtual Resource

Network Segment

Topology Pool

PIP2InterCloud Architecture Framework

35

ISMF - Relation between PR-LR-VR-VI••

Virtual Resource lifecycle – defines relations between different resource
presentations along the provisioning process
Physical Resource information is published by PIP to the Registry service serving
VICM and VIP
–

•

•
•
•

Logical Resource representing PR includes also properties that define possible (topological)
operations on the PR, such as e.g. partitioning or aggregation.

Published LR information presented in the commonly adopted form (using
common data or semantic model) is then used by VICM/VIP composition service
to create requested infrastructure as combination of (instantiated) Virtual
Resources and interconnecting them with the available network infrastructure
Network infrastructure can be composed of a few network segments (from the
network topology pool) run by different network providers.
Composed LRs are deployed as VRI/VI to VIP/VIO and as virtualised/instantiated
PR-LR to PIPResource/service description format considered––

NDL/NML (Network Description Language / Network Markup Language at OGF)
Compatibility with VXDL infrastructure service request format by INRIAInterCloud Architecture 2012

InterCloud Architecture Framework

36

NIST Publications on Cloud Computing
•
•

•

•
•

•

[NIST CC] NIST SP 800-145, “A NIST definition of cloud computing”, [online] Available:
http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf[NIST CCRA] NIST SP 500-292, Cloud Computing Reference Architecture, v1.0. [Online]
http://collaborate.nist.gov/twiki-cloudcomputing/pub/CloudComputing/ReferenceArchitectureTaxonomy/NIST_SP_500-292__090611.pdf[NIST Synopsis] DRAFT NIST SP 800-146, Cloud Computing Synopsis andRecommendations. [online] Available: http://csrc.nist.gov/publications/drafts/800-146/DraftNIST-SP800-146.pdf
Draft SP 800-144 Guidelines on Security and Privacy in Public Cloud Computing. [online]
Available: http://csrc.nist.gov/publications/nistpubs/800-144/SP800-144.pdf[NIST CC Roadmap] DRAFT NIST SP 800-293, US Government Cloud Computing
Technology Roadmap, Volume I, Release 1.0. [online]
http://www.nist.gov/itl/cloud/upload/SP_500_293_volumeI-2.pdf
NIST SP500-291 NIST Cloud Computing Standards Roadmap. [online] Available:
http://collaborate.nist.gov/twiki-cloudcomputing/pub/CloudComputing/StandardsRoadmap/NIST_SP_500-291_Jul5A.pdf

InterCloud Architecture 2012

InterCloud Architecture Framework

37

NIST Cloud definition – Draft SP 800-145 (1)• NIST Definition of Cloud – missing network provisioning, just “limited
control over network”
Cloud computing is a model for enabling ubiquitous, convenient, on-demand network accessto 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. This cloud model promotes availability andis composed of five essential characteristics, three service models, and four deployment
models.

Cloud Infrastructure as a Service (IaaS). The capability provided to the consumer is toprovision processing, storage, networks, and other fundamental computing resources
where the consumer is able to deploy and run arbitrary software, which can include
operating systems and applications. The consumer does not manage or control theunderlying cloud infrastructure but has control over operating systems, storage,
deployed applications, and possibly limited control of select networking components(e.g., host firewalls).

InterCloud Architecture 2012

InterCloud Architecture Framework

38

NIST Cloud definition – Draft SP 800-145 (2)Draft SP 800-145 A NIST Definition of Cloud Computing (published)
http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf• Five essential clouds characteristics
–
–
–
–
–

On-demand self-service
Broad network accessResource poolingRapid elasticity
Measured Service• 3 service/provisioning models– Software as a Service (SaaS)– Platform as a Service (PaaS)– Infrastructure as a Service (IaaS)• 4 deployment models––––

Public cloudPrivate cloud
Community cloudHybrid cloudInterCloud Architecture 2012

InterCloud Architecture Framework

39

NIST Cloud Computing Reference Architecture(CCRA) 2.0 - Main Roles (1)• Cloud Carrier as a role to accommodate telco’s
interests
InterCloud Architecture 2012

InterCloud Architecture Framework

40

NIST Cloud Computing Reference Architecture(CCRA) 2.0 - Provider Functions (2)Add:Service Delivery(Framework)• Request&SLA• Reservation/
Composition• Deployment• Operation• Decommissioning

Provider functions• Defined ambiguously• Need clear separation between Delivery
process, Operation and Control&Mngnt
functions• Service Orchestration is a Control function
InterCloud Architecture 2012

InterCloud Architecture Framework

41

NIST Cloud Computing Reference Architecture(CCRA) 2.0 – Consolidated View (3)• txtInterCloud Architecture 2012

InterCloud Architecture Framework42Dedicated Network Provisioning in Clouds• This issue is not addressed in details in any of currently
proposed CC architectures• It can not be consistent infrastructure QoS without(dedicated) network provisioning– Specifically for Optical networks• Telco, network providers and telecom equipment vendors areworking in this direction– GEYSERS project is an example of network+IT infrastructure
virtualisation•

InterCloud Architecture 2012

InterCloud Architecture Framework43Extending NIST Cloud IaaS definition to support NaaS(in the context of Network Infrastructure provisioning)
The suggested extensions to the Cloud IaaS model to meet requirements ofthe critical enterprise services:• Define layered cloud services model that should be suitable for defining
main inter-layer and inter-service (functional) interfaces• Add topology aware infrastructure view• Define resources and services virtualisation as one of generic cloudfeatures (TBD)• Include improved network services definition capable of provisioning
required QoS and allowing control from user run applications• At the business/operational level, the CCRA should be extended toaddress the following features:– Improved definition of the Cloud Carrier role, operational model and interaction
with other key actors– Extended set of basic roles to reflect typical for telecom operators/providers
business relations:• Cloud/infrastructure Operator, Customer, and User (in place of the currently used consumerrole)• Other cloud service models PaaS and SaaS should also allow
management of QoS and other network related parameters
InterCloud Architecture 2012

InterCloud Architecture Framework44