InterCloud Architecture Framework (ICAF)
forInteroperability and Integration

Yuri Demchenko
SNE Group, University of Amsterdam
Hong Kong Polytechnic University
30 November 2012, Hong Kong

Outline••••

Cloud Computing Architecture research at SNE group (UvA)
General use cases for Intercloud Architecture
Related standardisation initiatives: NIST, OGF, IETF
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

HK PolyU, 30 Nov 2012

InterCloud Architecture Framework

Slide_2

System and Network Engineering Groupat the University of Amsterdam••

SNE group is primarily a research group but also supports SNE master education
Main research areas– High speed optical networks• Recent testbed achieved sub-40Gbps at Amsterdam-CERN link
• Information modeling for network description– Security and generic AAA Authorisation framework (GAAA-AuthZ)•

Evolving from client/security model to dynamically provisioned services for Cloud and Grids– Cloud and Intercloud Architecture, Cloud Security, Cloud Services Provisioning•

New research area on Big Data Infrastructure services and adoption of Cloudbased/powered provisioning technologies and models– Defining corresponding security models and infrastructure•••Long term research cooperation with SURFnet and GigaPort program in NL
Re-building own testbed for optical network technologies, Intercloudinfrastructures and AAA/Security
Recent and current projects participation – DataGrid, NextGrid, EGEE,
Phosphorus, GEYSERS, GEANT3, NOVI, ENVRI

27-28 Nov 2012, HK PolyU

Cloud Architectures and Services
Provisioning3

Yuri Demchenko – Professional Summary••••

Graduated from National Technical University of Ukraine “Kiev Polytechnic
Institute” (KPI) in Instrumentation and Measurement (aka Industry Automation)
Candidate of Science (Tech) – Dissertation on System Oriented Precision
Generators (1989)
Teaching at KPI 1989-1998 – Computer Networking, Internet Technologies,
Security
Professional work in Internet technologies since 1993
– First publications on Internet technologies and security – 1994•

Work at TERENA (Trans-European R&E Networking Association) – 1998-2002–•

Wide contacts among European and international NREN and research community

Work at UvA with SNE group – since 2003
– Main research areas: Cloud Computing, Big Data Infrastructures, Application andInfrastructure Security, Generic AAA&Authorisation, Grid and collaborative systems– EU Projects: GEYSERS, GEANT3, Phosphorus, EGEEI-II, Collaboratory.nl– Standardisation activity – IETF (1 I-Draft pending, 3 RFC’s published), Open Grid
Forum (OGF) – ISOD-RG chairing, NIST Cloud Architecture Collaboration

HK PolyU, 30 Nov 2012

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

– Enterprise/campus cloud infrastructure evolution and migration/mobility– Infrastructure disaster recovery (e.g., Vodafone NL Datacenter Incident –April 2012, Orange multiple DC failures – summer 2012)• Data require supporting infrastructure– Educational Lab setup in cloud• Easy to suspend and deploy when necessary• ICAF intends to open Cloud market to more players and rise so-called“cloud curtain”
HK PolyU, 30 Nov 2012

InterCloud Architecture Framework5InterCloud: Related standardisation activities• NIST Cloud definition (NIST SP 800-145), and Cloud Computing
Reference Architecture (CCRA), v1.0 (NIST SP 500-292)• 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• 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• OGF ISOD-RG– BCP on existing on-demand network and cloud infrastructure resources
provisioning systems (including GEYSERS)• 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
HK PolyU, 30 Nov 2012

InterCloud Architecture Framework

6

NIST Cloud definition – SP 800-145
Draft SP 800-145 A NIST Definition of Cloud Computing (published Nov 2011)
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 cloud

HK PolyU, 30 Nov 2012

InterCloud Architecture Framework

7

NIST Cloud Computing Reference Architecture(CCRA) 2.0 - Main Roles• Cloud Carrier as a role to accommodate telco’s
interests
HK PolyU, 30 Nov 2012

InterCloud Architecture Framework

8

NIST Cloud Computing Reference Architecture(CCRA) 2.0 – Consolidated View

• txt

HK PolyU, 30 Nov 2012

InterCloud Architecture Framework

9Work on I-Draft “Cloud Reference Framework”(Version 0.3)
http://tools.ietf.org/html/draft-khasnabish-cloud-reference-framework03.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

HK PolyU, 30 Nov 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 – December 2012
Version 0.5 – Summer 2013
(To be considered)10Intercloud Architecture - Requirements
Intercloud Architecture (ICA) should address interoperability and integrationof different cloud service platforms provided by multiple cloud providers,
including integration with legacy 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• Support/provide Intercloud Control and Management Plane functionality
for performance critical cloud services and network integration• Support intra- and inter-cloud network infrastructure provisioning with
controlled performance and QoS (as NaaS service model)• Support existing Cloud Provider operational and business models andprovide a basis for new forms of services provisioning and operation– Support provider side federation (for resources sharing) and customer/broker sidefederation for multi-provider infrastructure integration
HK PolyU, 30 Nov 2012

InterCloud Architecture Framework

11

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
HK PolyU, 30 Nov 2012

InterCloud Architecture Framework

12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

VR7
VR4

VR1

VR5

Resource/
Service
ProviderImplementing
Resource/
Enterprise/Scientific
Service
Providerworkflow or
supporting a business modelis an ultimate goal of any
infrastructure
HK PolyU, 30 Nov 2012

User
Group B

VR3

Enterprise/Project basedIntercloud Infrastructure

Cloud 1 IaaS

CN

CN
CN

CN
CN

CN

Cloud PaaS Provider

CN
CN

CN

CN
CN

Cloud IaaS Provider

InterCloud Architecture Framework

13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

VR7
VR4

VR1

VR5

Resource/
Service
ProviderEnterprise/Scientificworkflow
Is mapped
to heterogeneous cloudinfrastructure containing
IaaS, PaaS components
HK PolyU, 30 Nov 2012

User
Group B

VR3

Enterprise/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 Framework

14

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

VR7
VR4

VR1

VR5

Resource/
Service
ProviderDistributed
Resource/
heterogeneous cloud
Service
Providerinfrastructure requires
separately provisioned
network infrastructure that
Can outsourced to Cloud Carrier
HK PolyU, 30 Nov 2012

User
Group B

VR3

Enterprise/Project basedIntercloud Infrastructure

Cloud 1 IaaS

CN

CN
CN

CN
CN

CN

Cloud PaaS Provider

CN
CN

CN

CN
CN

Cloud IaaS Provider

InterCloud Architecture Framework

15

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

… or to regular
Network Service Provider
HK PolyU, 30 Nov 2012

Cloud PaaS Provider

CN
CN

CN

CN
CN

Cloud IaaS Provider

InterCloud Architecture Framework

16

Intercloud Applications Interaction (1) - ICCMP
IaaS Domain

Cloud Layers
Layer 7 - Applications

User
definedPlatform
andSW&Apps

InterCloud Control andManagement Plane(ICCMP)

PaaS Domain

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

Visualisation

Providerdefined
Virt&OS
Platform

ICCMP – InterCloud Control
and management Plane

User
defined
SW&Apps

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

VR7
VR4

VR1

VR5

Resource/
Service
ProviderConsistent and tight
Resource/
management ofService
Providerthe heterogeneouscloud infrastructure requires
Intercloud Control andManagement Plane (ICCMP)HK PolyU, 30 Nov 2012

User
Group B

VR3

Enterprise/Project basedIntercloud Infrastructure

Cloud 1 IaaS

CN

CN
CN

CN
CN

CN

Cloud PaaS Provider

CN
CN

CN

CN
CN

Cloud IaaS Provider

InterCloud Architecture Framework17

Intercloud Applications Interaction (2) - ICFFIntercloud Federation
Infrastructure

IaaS Domain

PaaS Domain
Registry

Discovery

User
SW&Apps

Layer C3-IaaS

BrokerBrokerGW

GW
ProviderVirt&OS
Platform

IdP
Trust
BrokerAttribs

Visualisation

ICFF – InterCloud
Federation Framework

LayerC4-PaaS

Trust
Broker

ProviderVirt&OS
PlatformCampus A

User
SW&AppsVisualisation

Trust

CE

User
Group A

Campus B

CE

User
User
User

User
User
User
VR6

Cloud 2 PaaS

VR2

VR7
VR4

VR1

VR5

Resource/
Service
ProviderIndependently
managed cloud domains Resource/
Service
Providermay use federated
model for resources andprocesses integration andinteroperation
HK PolyU, 30 Nov 2012

User
Group B

VR3

Enterprise/Project basedIntercloud Infrastructure

Cloud 1 IaaS

CN

CN
CN

CN
CN

CN

Cloud PaaS Provider

CN
CN

CN

CN
CN

Cloud IaaS Provider

InterCloud Architecture Framework

18

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• Mobility?

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

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

Visualisation

Trust

Layer 2 - Virtualisation

Campus B

Visualisation

ProviderdefinedInfrastr.
andVirt&OS
Platform

Layer 3 – Composition
Providerdefined
Virt&OS
Platform

Trust
BrokerPaaS Domain

Layer 4 - PaaS

Layer 4 - IaaS
Cloud Infrastructure

Layer 3 - IaaS

CE

CE

Layer 1 - Physical
HW Platform/Network

User
User
User

User
User
User
VR6

Cloud 2 PaaS

VR2

VR7

VR5

Resource/
Service
ProviderHK PolyU, 30 Nov 2012

User
Group B

VR4

VR1

Resource/
Operational andService
Providerbusiness issues are
typically addressedby Operations services anda framework

Provider Virt&OS
Platform

Userdefined
SW&Apps

Layer 7 - Applications

User
definedPlatform
andSW&AppsUser
Group A

GW

IdP
Attribs

IaaS Domain Cloud Layers

Campus A

User
SW&Apps

VR3

Enterprise/Project basedIntercloud Infrastructure

Cloud 1 IaaS

ICOF – InterCloudOperations Framework
CN

CN
CN

CN
CN

CN

Cloud PaaS Provider

CN
CN

CN

CN
CN

Cloud IaaS Provider

InterCloud Architecture Framework

19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
HK PolyU, 30 Nov 2012

InterCloud Architecture Framework

20

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

HK PolyU, 30 Nov 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_21

Multilayer Cloud Services Model (CSM) – In development
Compose into one Cloud Services layerand define intra-model
User Applications

Access layer

CSM layers
Layer C7
User
Client/ Application

1
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

HK PolyU, 30 Nov 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

22

Intercloud Control and Management (1)• 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 project

HK PolyU, 30 Nov 2012

InterCloud Architecture Framework

23

Intercloud Control and Management (2)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

HK PolyU, 30 Nov 2012

InterCloud Architecture Framework24Intercloud Control and Management (3)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

HK PolyU, 30 Nov 2012

Non-standard/proprietary Interface

InterCloud Architecture Framework

25

Intercloud Control and Management (4)• 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– Message routing– Signaling– Control– Management– Monitoring– Location
HK PolyU, 30 Nov 2012

InterCloud Architecture Framework

26

InterCloud Federation Framework (1)•••HK PolyU, 30 Nov 2012

All inter-services interactions involve 3rd party actor: Registry, Broker
and gateways
Requires previously established relations/contracts and trust
relations – direct or via trusted broker
Dynamic trust establishing mechanisms required for dynamic intercloud federation
InterCloud Architecture Framework

27

InterCloud Federation Framework (2)• 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

HK PolyU, 30 Nov 2012

InterCloud Architecture Framework28

InterCloud Operations Framework (1)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• Mobility?

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

HK PolyU, 30 Nov 2012

InterCloud Architecture Framework

29InterCloud Operations Framework (2)• Defines the main roles and actors– RORA model: Resource, Ownership, Role, Action• Defined in the GEYSERS project to address infrastructure services virtualisation• 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
HK PolyU, 30 Nov 2012

InterCloud Architecture Framework30

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

HK PolyU, 30 Nov 2012

InterCloud Architecture Framework31

Implementation: GEYSERS Project 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/

HK PolyU, 30 Nov 2012

InterCloud Architecture Framework

32

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

HK PolyU, 30 Nov 2012

InterCloud Architecture Framework

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

33

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

HK PolyU, 30 Nov 2012

InterCloud Architecture Framework

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

34

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

HK PolyU, 30 Nov 2012

InterCloud Architecture Framework

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

35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

HK PolyU, 30 Nov 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

36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)

HK PolyU, 30 Nov 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_37

Summary and Future works• The proposed ICAF is based on existing standards andproposes their integration and extension– Includes 4 components: CSM, ICCMP, ICFF, ICOF
• Addresses cloud services/infrastructure lifecycle management• Future research and development primarily focused on interlayer and inter-cloud interfaces definition– Re-factor GEYSERS Infrastructure virtualisation interfaces– Testbeds: IaaS (GEYSERS) and PaaS (GEANT3)• Standardisation activity at IETF, OGF, TMF– Partnership with industry (GEYSERS partners: Telefonica R&D,
Interoute, SAP, Polish Telecom, ADVA; also Cisco, Huawei)

HK PolyU, 30 Nov 2012

InterCloud Architecture Framework38Questions and Discussion

HK PolyU, 30 Nov 2012

InterCloud Architecture Framework39