TF4: Cloud Federation New elements comparing to the separated Cloud : CF network Resources in many...

8
TF4: Cloud Federation New elements comparing to the separated Cloud : CF network Resources in many Clouds Potentiality of Cloud Federations vs. Separated Clouds: Better resource utilization More offered services Problem: More complicated traffic management Exemplary Cloud Federation with 5 Clouds 1

Transcript of TF4: Cloud Federation New elements comparing to the separated Cloud : CF network Resources in many...

Page 1: TF4: Cloud Federation New elements comparing to the separated Cloud : CF network Resources in many Clouds Potentiality of Cloud Federations vs. Separated.

1

TF4: Cloud Federation

New elements comparing to the separated Cloud :

• CF network• Resources in many Clouds

Potentiality of Cloud Federations vs. Separated Clouds:

• Better resource utilization• More offered services

Problem:• More complicated traffic

management

Exemplary Cloud Federation with 5 Clouds

Page 2: TF4: Cloud Federation New elements comparing to the separated Cloud : CF network Resources in many Clouds Potentiality of Cloud Federations vs. Separated.

• University of Szeged and MTA SZTAKI, Hungary– Attila Kertesz

• University of Antwerp-iMINDS, Belgium– Steven Latre

• University of Zurich, Switzerland– Patrick Gwydion Poullie , Patric Taddei

• Deutsche Telekom AG– Gerhard Hasslinger

• Warsaw University of Technology, Poland– Wojciech Burakowski, Maciej Sosnowski, Andrzej Beben

1

Partners:

TF4: Cloud Federations

Page 3: TF4: Cloud Federation New elements comparing to the separated Cloud : CF network Resources in many Clouds Potentiality of Cloud Federations vs. Separated.

Content 1. Introduction 22. Reference architecture for Cloud Federation 32.1. Architectural views 32.2. Standardization on clouds and CDNs 52.3. The role of ISPs in cloud federation 63. Modelling Cloud Federation 73.1 Cloud Federation system 71.2 Multi-level model of traffic management 81.2.1 Level5: Strategies for handling requests in Cloud Federations 103.2.2 Level4: Cloud Federation set-up 113.2.3 Level3: Service provision and Level2: Service execution 133.2.4 Level1: Task service in cloud resources 164. Capabilities for performing experiments 175. Conclusions 19Bibliography 20

1

Task Force 4: Cloud Federations (white paper)

TF4: Cloud Federations

Page 4: TF4: Cloud Federation New elements comparing to the separated Cloud : CF network Resources in many Clouds Potentiality of Cloud Federations vs. Separated.

4

Multi-level traffic model for Cloud Federation

OFF-LINE

OFF-LINE

OFF-LINE

ON-LINE

Level 4Cloud Federation Setting

· Resources in Cloud Federation · types of resources· number of resources

· Network connecting Clouds· network topology· network provision

Level 3Service of IS requests

· Service specification - specification of task sequence

· Service provision -alocating resources to execute particular task

Installing Service (IS) Requests

Level 2Service of ES requests

· Service of appropriate task sequence· Allocating tasks to the resources (if more than one

resource can serve the task) Execution Service (ES)

Requests

Level 5Strategies for handing demands

· Distribution of demands between Clouds

Level 1Task service in cloud resources

· Task scheduling · Fairness ON-LINE

Page 5: TF4: Cloud Federation New elements comparing to the separated Cloud : CF network Resources in many Clouds Potentiality of Cloud Federations vs. Separated.

1

Example – Level 1 Fair Multi-resource Allocation in CloudsInvestigated research topics

TF4: Cloud Federations

1. How do CPU, RAM, Disk I/O, and network accessinterdependent, when consumed by VM

– i.e., when one resource gets scarce, how changes theconsumption of the other resources?

2. How to define fairness between cloud customers?– Customers may have different VMs with different utilization

3. How to reallocate resources to enforce fairness?– Oblivious to jobs, i.e., low level fairness

Page 6: TF4: Cloud Federation New elements comparing to the separated Cloud : CF network Resources in many Clouds Potentiality of Cloud Federations vs. Separated.

1

Short-term plans

TF4: Cloud Federations

• To specify the multi-level CF traffic management model– To specify algorithms for each level• Eg. next document: „Algorithms for the multi-level CF

traffic management model”

– To understand the dependences between particular levels

Page 7: TF4: Cloud Federation New elements comparing to the separated Cloud : CF network Resources in many Clouds Potentiality of Cloud Federations vs. Separated.

1

Long-term plans

TF4: Cloud Federations

– To develop software tool to evaluate the model– To check the CF traffic management in a testbed,

e.g. in PL-LAB2020

Gdańsk

Warszawa

Poznań

Wrocław

Gliwice

WarsawUniversity of Technology

6 SDN switches15 Servers

Poznań Supercomputingand Networking Center

16 SDN switches19 servers

GÉANT, FED4FIRE, XIFI, FIWARE

Wrocław University of Technology

2 SDN switches25 servers

Gdańsk University of Technology6 servers

National Institute of Telecommunications

18 SDN switches24 servers

Silesian University of Technology

6 SDN switches4 servers

Page 8: TF4: Cloud Federation New elements comparing to the separated Cloud : CF network Resources in many Clouds Potentiality of Cloud Federations vs. Separated.

1

Publication plans

TF4: Cloud Federations

– To edit special issue e.g. in Computer Communications

– Other publications