Inter cloud computing: Use cases and requirements for Sociallab.iisec.ac.jp/~goto_lab/publication/2012/20120224_CloudScape.pdf · 2/24/2012 · Inter‐cloud computing: Use cases

Inter‐cloud computing:Use cases and requirementsfor Social Infrastructures

Feb 24, 2012Global Inter‐Cloud Technology Forum (GICTF)

Institute of Information Security (IISEC)Atsuhiro Goto

Feb 24, 2012 GICTF & IISEC 1

Secure cloud computing is needed


Small and medium‐sized enterprises/municipalities

Individuals

Public cloudPublic cloud(for Internet use)

Private cloud

Consumers Enterprise / Organizations

Home ICT

Limited Use in Enterprise / Organizations

Utility operation systemsMission-critical tasks

High

LowCurrent Cloud areas

Social infra-structures

QualityReliability

Safety

e-Government

EntertainmentBlogs, SNS

Tele-work

Large enterprises/governments

Medical, Finance

Agenda

• Highly Reliable Inter‐Cloud Systems R&D project, a national project in Japan

• Global Inter‐Cloud Technology Forum (GICTF)

• Inter‐Cloud for secure “Lifeline Services”– Lessons learned from the East Japan Earthquake


Highly Reliable Inter‐Cloud Systems R&D project funded by Japanese government


Physical World

SensorNode

SensorNode

Network

Cloud SystemA

Cloud SystemB

Server

Storage

Open FlowOpen Flow

AP AP APApplication

Cloud Resource Federation and Reconfiguration

Cloud Resource Provisioning

Real-time Sensor Node

Dynamically Reconfigurable NW based on Open Flow

<2009 ‐ 2012: total 43M$>

Global Standardization of “Inter‐Cloud”

Global Inter‐Cloud Technology Forum (GICTF)Main activities:

• Identify technical needs for secure “inter‐cloud technology” • Raise awareness of users both in industry, government and communities

Membership (as of December 2011)• 80 enterprises, National laboratories, and academia• Observer: MIC, METI


Global Inter‐Cloud Technology Forum


Major DeliverablesI. “Use case and functional requirements for Inter‐Cloud

Computing” E/Aug 2010II. “Inter‐Cloud interface specification on protocols” J/Dec

2011, E/Mar 2012III. “Inter‐Cloud interface specification on resources data model

for network control” J/Dec 2011, E/Mar 2012IV. “Network and technical requirements in support of Inter‐

Cloud” J/Dec 2011 E/Aprl 2012

Promote international standardization of “inter‐cloud” interface through cooperation with standards bodies

Cloud Functional Architecture First Cloud ICT architecture

7

User Layer

Access Layer

Resources & Network Layer

Cross‐LayerFunctions

ServicesLayer

End‐User Function Partner Function Administrator

Function

Inter Cloud Function

Endpoint Function

SaaS / CaaS

PaaS

IaaS

NaaS

Service Orchestration

PhysicalResources

Pooling & Virtualization

Resource Orchestration

Cloud PerformanceFu

nction

VN VS VMSoftware & Platform

AssetsVirtual Path Virtual Circuit

Intra Cloud Network Storage Computing Core Transport

NetworkInter Cloud Network

Security & Privacy Function

Operational Management Function

Feb 24, 2012 GICTF & IISEC

Inter‐cloud Computing


Medical

Network

Server

Storage

Application

Cloud A

CDNCDN

E‐Gov

Cloud B

FinanceMedical

E‐Gov

Finance

On‐demand reassignment of cloud resourcesacross “autonomous” clouds

SLA assurance

SLA assurance

interworking

Lessons learned : The East Japan Earthquake


Serious damage on ICT facilities in the disaster area

Serious power shortage / rolling blackout in wide area of East Japan

Flexibly reassigning resources among cloud providers and network providers on a global scale

Secure Inter‐Cloud for “Lifeline Services”

GICTF & IISEC 10

AP

Home network

Sensor network

Cloud ProvidorAP

Internet

Other cloud providers

Disaster

Case1: Migrate lifeline services by accommodating cloud resources among cloud/network providers when disaster or massive breakdown occurs

Lifeline Services(administrative,

financial, medical care, etc.)

Amusement

Case2: Cloud providers re‐assign their cloud resources in line with social importance, e.g. from amusement services to lifeline services, when necessary

Lifeline Services

Feb 24, 2012

Wrap‐ups

• The future social infrastructures based on cloud computing and networking systems must be based on appropriate global standards.

• GICTF has been and will be contributing to inter‐cloud technologies development and standardization.

• Now, technology evaluation efforts are very important– By global collaboration projects with EU and other regions

– By encouraging users to join the evaluation via GICTF Application TF and JCC.


BACKUPS


JGN‐X Tohoku‐1

JGN‐X Tokyo‐1

Base(1)Tokyo

Base(2)Tohoku

JGN‐X Kyushu‐4

Exclusive Line100M

JGN‐X Kyushu‐1

• Inter‐cloud technology evaluation will start in 2012 on the national‐scale test bed where three cloud data centers in Tokyo , Tohoku, and Kyushuwill be connected with each other via JGN‐X.

Inter‐cloud test bed planned in 2012

Base(3)Kyushu

Cloud C

Cloud A

Cloud B


PaaS APISaaS API

IaaS API

Implementation

BSS/OSS

Security

Open Cloud Manifesto

CSA

ENISA

DMTF

OASIS

ETSI

Inter-Cloud

Other Cloud

TM forum

ISO/IEC JTC1

ITU-T IEEE

DMTF

ITU-T

OCC

Taxonomy, Use cases, SLA, Requirements

NIST

NIST

Architecture ITU-T NIST

SDO coordination OMG IEEE

ITU-T

OCC

SIENA OGC CBA

KCSA CCF

GICTF

JapanAsiaEUUSAGlobal

GICTF

Cloud

OGF

SNIA

DMTF

ATIS CSF

OpenStack

Users/Operators

Cloud MngAPI

ISO/IECJTC1

Cloud Standardization Status


GICTF Organization

15

General Assembly

Board of Directors

1. Exchange and share informationwith relevant standards bodies, academia and communities

2. Identify technical needs related to secure inter-cloud technology applicable to e-Government, etc.

3. Develop a standard set of specifications applicable to e-Government, etc. and propose it to relevant standards bodies

1. Identify technical needsrelated to secure inter-cloud technology

2. Promote widespread use of inter-cloud computing technology

Application Task ForceTechnology Task Force

GICTF & IISEC

Chair: Tomonori AoyamaV.Chair: Atsuhiro Goto

Feb 24, 2012

Four white papers produced by GICTF1. Use cases and functional requirements for inter‐

cloud computing, Aug 2010.• Six use cases and requirements

2. Network and technical requirements in support of inter‐cloud, Apr. 2012.• Detailed study on required network functionalities in three

timeframes3. Inter‐cloud interface specification on protocols, Mar.

2012.• Information flows between two cloud operators

4. Inter‐cloud interface specification on resources data model for network control, Mar. 2012.• Data semantics between two cloud operators


Framework of Inter‐cloud Interface Specification

• The interface between two cloud systems administered by different operators

• Three layer modeling– Lower layer protocols assumed as some XML message exchange,

e.g., REST or SOAP– Inter‐cloud protocol: Information flows, message semantics with

associated parameters specified– Data models for network resources specified– Data models for computing and storage referenced to other SDO’s

specifications

Inter‐Cloud Protocol

Lower Layer Protocols (e.g., REST or SOAP)

Data Center ResourceData Model

(Computing and Storage)

Network ResourceData Model(Network)

Inte

r-C

loud

IFCloud System

Data CenterResource

NetworkResource

Cloud System

Data CenterResource

NetworkResource

Inter‐Cloud Protocol


Examples of information flow and data model

• Information flows– Definition of three resource states. i.e., unused, reserved, and

used– Information flows between cloud providers

• Notification of system activation and being ready• Resource discovery, reservation, usage monitoring, activation,

and release• Data synchronization between cloud providers and delegation

of the control– Messages to be exchanged with their parameters

• Resource data model– Three‐type network resources: network, provider, and user

– Definition of classes and example descriptions in XML

Resource Reservation Request

Server Resource Reservation Request

Resource ReservationNW Resource Reservation ResponseServer Resource Reservation Response

Resource Reservation Response

Cloud System A

Cloud System B

NetworkResource

Data CenterResource Network

‐Network ID‐Number of end points‐Physical bandwidth‐Cost‐‐‐‐‐‐‐‐‐‐‐

Network usage status‐Measuring point‐Measurement values‐‐‐‐‐‐‐‐‐‐

Network group‐Network group ID‐Network ID list‐redundancy‐‐‐‐‐‐‐‐‐‐‐

User‐Name‐Address‐Network address‐‐‐‐‐‐‐‐‐‐‐

Provider‐Provider ID‐Access point ID list‐‐‐‐‐‐‐‐‐‐‐

Access point‐Access point ID‐Network address‐‐‐‐‐‐‐‐‐‐‐‐

QoS‐Guarantee bandwidth‐Maximum bandwidth‐‐‐‐‐‐‐‐‐‐‐

Resource reservation

Parameters‐Request ID‐Cloud system A attributes

System name, URL, Provider ID, System configuration‐Cloud system B attributes‐Information for resources to be reserved‐ . . .

Messages

Network

User Network Provider

NW Resource Reservation Request


Results of ITU‐T FG cloud computing• Seven deliverables produced by two‐year activities and eight meetings• Potential drafts for Recommendations provided: Ecosystems, Reference

Architecture, Infrastructure, and Security• Identification of study items in the final FG‐Cloud report including Inter‐

Cloud stating that “Procedures and interfaces are required for…”• Nomination of SG13 as the lead Study Group in ITU‐T cloud computing• Joint Coordination Activity (JCA) to be established, which should coordinate

cloud computing studies with SDOs beyond ITU‐T

Deliverable Target SG Contents

aIntroduction to the cloud ecosystem: definitions, taxonomies, use cases, and high level requirements

SG13Definitions, actors and roles、use cases, and-high level requirementsNOTE: Intercloud aspect has been incorporated in use cases, high-level requirements, and scenarios

b Functional Requirements and Reference Architecture SG13 Layers and their functions.

NOTE: Access layer contains Inter-Cloud function.

c Requirements and framework architecture of cloud infrastructure SG13

Lower network parts NOTE: Functional requirements includes functional requirements for the inter-cloud network

d Cloud Resource Management Gap Analysis SG13 Gap analysis on resource management

e Cloud Security SG17 Security considerations and current practices


Comparison between four GICTF white papers and four FG Cloud deliverables

DefinitionConcept overview

Use cases

Requirements

Functions

Architecture and IF

Signaling

Information data elements

Protocol

Profiling

Interoperability

1Use Cases and Functional

Requirements

2Network andTechnical

Requirements

1

3Inter‐Cloud Protocol

4Resource Data

Model

aEco

system

bReferenceArchitecture

cInfra‐

structure dResource

management

GICTF 4 White Papers FG Cloud Main 4 Deliverables


NICT IPA JDCC GICTF

Secretarial Board(a secretariat consisting of Nippon Keidanren and

several other enterprises/organizations)

General meeting (About twice a year)

Ｊapan Cloud Consortium

Related organiza-

tions

The private organization of a “Japan Cloud Consortium” is established to promote the dissemination/development of cloud services in Japan in an industry‐academia‐government collaboration of various industries, organizations, and businesses.

ASPIC GIPC ＯＳＳ－Ｃ

●MembersTotal 378

（including Enterprises 307,Organizations,59,Experts １２）（Dec, 2011）

WGWGWGWG

Ｊapan Cloud Consortium


Communication facilities were the worst affected


• Transmission lines: 90 routes were cut off

• 18 buildings were fully destroyed, and 23 buildings were flooded

• 65000 telephone poles were destroyed by the flood

Inter cloud computing: Use cases and requirements for Sociallab.iisec.ac.jp/~goto_lab/publication/2012/20120224_CloudScape.pdf · 2/24/2012 · Inter‐cloud computing: Use cases

Documents