1 - OneLab - AsiaFi– November 17, 2009 – Bangkok Thailand OneLab Asia Future Internet Workshop...

1 - OneLab - AsiaFi– November 17, 2009 – Bangkok Thailand

Asia Future Internet Workshop

OneLabOneLabCan we build a test-bed to

explore the “future” Internet?

Serge Fdida

Université Pierre & Marie Curie, LIP6Paris, France

An Open Federated Laboratory Supporting Network Research for the Future Internet


Outline

● Vision Starting from the Customer end A Facility - what is it?

● The Federation concept When and how to federate? Current federation activities

● From vision to Implementation: Offering PlanetLab Europe Operation Onelab contributions


Questions?

● What is the vision? What is broken and need to be fixed?

● What is the right approach? Is the clean slate approach appropriate? Any transition methodology?

● How difficult do you expect that a new architecture would be adopted? We have a few examples on how difficult it is to change

the current architecture: multicast, mobile IP, Intserv/Diffserv, and IPv6.

Any enabling factor?


Some possible scenario ….


Clean slate vs evolutionary?


Vision – The « Facility » framework


Vision

● Explore the possible Future(s) of the Internet Innovative research, multidisciplinary, demonstration

• The future Internet might be Polymorphic• Multiple Federated Internets will co-exist build with different design

criteria• Including the current one

• Content, Wireless, DTN, Things, …

● What is the foundation of this future?

● How to assess the assumptions explored by candidate future internet solutions?

Network Science Experimentation facility


The Polymorphic Internet : Some Internet Future(s)

• The Network is a Database

• The (Access) Network is The (Access) Network is WirelessWireless

• The Network is the People

• The Network is a global Virtualized resource

• They’re all Federated (Inter-domain)

Enabling continuous deployement of New architectures

Virtualized substrate

IP world

Policies

Monitoring

Security

Federation

First applied to Test-beds federation


Experimentally driven research

● Why? Research driven by Intuition & Experimentation +

validation A Playground for enabling new architectures

● Enforce a Federation effort on building a large-scale facility for network research On the importance of testing Diversity and scale Lower the entry cost for experimentation


The federation vision

http://www.onelab.eu/http://www.planet-lab.eu//


Federate your testbed


The EU FIRE Framework

14 - OneLab - AsiaFi– November 17, 2009 – Bangkok Thailand ••• 14

“creating a research environment for investigating and experimentally validating highly innovative and

revolutionary ideas“

To investigate, test and compare, at large scale, new paradigms and future internet architectures, and their socio-economic impact

requirements

validation

long-termresearch

large scaleexperiment. Testbed

Testbed

Testbed

Testbed

Testbed

Testbed


Next?: Expanding the concept & building the facility

• enable socio-economic impact assessment

• broaden involvement of large user communities

• support sustainability• develop the facility in

close cooperation with FIRE research projects

• Join forces in Europeand collaborateinternationally

FP6: Early design & prototyping

TESTBED PROJ ECTS

FP7 – WP 2007/08: Prototyping the conceptof federating testbeds

• supporting academia and industry• proof-of-concept → pre-commercial tbs• understanding the socio-economic dim.

FIREWorks

PARADISO

FIRE-Research:New paradigms

Network ofthe Future

FIRE Facility

Other ProjectsFP7, MSs, …

ON

EL

AB

2

VIT

AL

++

WIS

EB

ED

PII

FE

DE

RIC

A


European Union Framework

● ICT FP7 Framework Program (2007/2014) ICT: Information and Communication Technologies € 9.1 billion for funding ICT over the duration of FP7

● ICT Challenge 1 Internet related projects from technology to services Strong emphasis on the future Internet Most are industry driven projects Some innovative projects

● Experimentally-driven research European Experimental Facility Fireworks FP7 SA coordinating FIRE projects

17 - OneLab - AsiaFi– November 17, 2009 – Bangkok Thailand ••• 17

PII

OL2

Vital++

WISEB

PERIM

NaDa

Resum

Self

ECOD OPN

N4C

SMART


PII Architecture

•18



•19


1 Gbps Ethernet

GARRIT

DFNDE

CESNETCZ

SWITCHCH

Red.esES GRNET

ICCS GR

HungarnetHU

PSNCPL

HEAnetIE

i2CATES

KTHSE

NORDUNET

SUNET

FCCNPT

Each core PoP is equipped with a switch/router (Juniper) and two or more V-Nodes

FEDERICA Infrastructure

•20

A rough comparison of the FIRE Facility prototypes

• Virtual slices composed of networking and computing resources• Isolation of experiments in slices• Operational environment• Reproducibility & monitoring

•Shared Resources•Real World Environment

•Applications enduring over time

•Partial Control•Variability

•Converging network, service platform and application infrastructures•Complete Control over Dedicated Resources•Reproducibility

Focus

Gigabit transmission equipment and computing nodes both capable of virtualization

PlanetLab – both public and private versionsOwn evolution with Federation

SOA(e.g. to federate IMS based testbeds among themselves and with others)

Platform

• Networking Research• Network technology agnostic environment• GÉANT, NRENs

•Distributed system•IP networking•Research focus

• Converged Telecom/ Internet Service & Network Environments• Industry focus

Context

NSF/FIRE workshop, December 8, 2008, Madrid21


The Federation Concept!


A Customer View on Experimentation● What do I want to achieve?

Test a proposition, e.g.,■ Technology

■ New service

■ End user acceptance

■ A new business hypothesis (e.g., business model)

■ A new regulatory approach

with given objectives Openness of results

Exclusive IPR

Scale of experiment

Diversity of environment, e.g., locality, technologies, …

Integration into larger facilities (for increased testing purposes)


Where does the Facility Come In?

A means to the (customers') ends!● Is A Facility…

…A collection of test beds (each individually governed)?

…A collection of test bed federations?

…A single test bed federation?

● Or is it a toolkit to support the customers' needs with the ability to

Build a federation that match the objectives at hand

Build on working test beds but also allow to integrate its own

Apply technologies proven to work (to a certain extent)

Rely on a community of researchers and practitioners dealing with similar (testing and research) problems?


The Onelab Vision

Provide a facility to the consumer that constitutes a toolkit of methods and abilities by

● Building on a proven basis PLanetLab Europe (PLE) is a working federation of test beds

PlanetLab (PL) provides a proven and evolving platform basis for experimentation

PL has gathered a large community of experimental researchers worldwide to rely on

● Building (and federating) actual test beds PLE is the public version under a particular governance

Wireless and other (DTN) extensions under work (see later)

● Building a toolkit that helps customers in experiments Work on benchmarking, measurements, … useful beyond the test beds

Dissemination activities to potential customers


Main questions?

● Building a Facility, which affordable long-term vision can we develop? No dogmatism! Usage/Cost Trade-off.

● What is a reasonable starting point? Users of the Facility from the origin

● What are the purposes to be served? Long-term / Short-term Research / Industry Public good / Commercial

● What are the facility-specific research & industrial challenges?

● The Semantic of Federation!


Why to federate?

● Many benefits Diversity, realism (geography, technology) Scale (number of nodes, resources) Multiplexing (more efficient resource usage) Creation of a global research community

● But also challenges Complexity Legal and trust issues Policies


When and how to federate?● Different objectives: Scale, realism, reproducibility,

heterogeneity

● Different constraints: Security, privacy, allocation policies

● When (not)? (which types of facilities) Commercial vs. open testbeds Reproducibility vs. realism Heterogeneity/scale vs. capacity per node/simplicity

● How? (under which policies) Fairness vs. efficiency Sophisticated incentive mechanisms vs. accounting Independence vs. simplicity


Can we achieve this?


Or this, eg FEDERATION


Distributed facilities

● PlanetLab

Sites contribute nodes

Researchers belonging to a site create slices that consume resources

An Internet overlay

Public good approach

● Slice-based Facility Architecture (MyPLC)

Private vs. Public

MyPLC

Give:Get:

Provision:Depends on sites(number, quality)

Allocation:Short-term fairness


Network infrastructure providers

● Geographic initiatives

FEDERICA (Europe)

VINI (US)

SINET3 (Japan)

● Low-level network virtualization tools

● Main issue: resource allocation

Provision:Fixed

Allocation:Fair + Constrains (time, bandwidth)Payments?


Stand-alone testbeds

● Testbeds managed by a single authority

Geographically limited

With affiliated users or not

● Different technologies

Wireless, emulation, sensors, …

E.g., ORBIT, Emulab, Haggle/ANA, WISENET

● Again, resource allocation is critical

Scarce resources or need for users?

In many cases virtualization is hard

Provision:Fixed

Allocation:Various reservationmodels


Federation (dictionary definition!)

A federation is a union comprising a number of partially self-governing regions united by a central ("federal") government under a common set of objectives.


The federation vision


Federation: main entities

Researchers

Resources

Facility A

Slice Management

Administrative borderAuthority A Authority B

Slice Management

Facility B


Federation (1)

Facility A

Slice Management Slice Management

Facility B1. Share user credentials


Federation (2,3)

Facility A


Facility B1. Share user credentials

2. Share resource descriptions

3. Allow experiments to run across facilities


Federation: more than resource integration

Facility A


Facility B

Policies

Monitoring

Security


Slice Management Interface (SMI)

● Different possible scenario Only user credentials are exchanged and users can

access other facilitie’s resources through their own SMI Each facility can offer its own interface to the all available

federated resources Facilities could agree on a common interface to provide

access to the federated resources

● Running an experiment across facilities None (an experiment per facility) A gateway to bridge facilitie’s nodes Synchronization functionality (reservation!)


PLE-PLC federation policy


Future Plans


Need for hierarchical federation


Other types of federation policies (PLE-Federica)


PLE-Private PlanetLabs (Glab, EverLab, Emanics)


From Vision to Implementation


Onelab History

Oct’03

ENEXT NoE

Testbeds

March’04

PlanetLab Europe Initiative

May’04

PlanetLab meeting in Cambridge

Sept’06

Onelab funded as IST project (Strep), 2 years -1.9/2.9M€

Sept’05

OneLab submitted as IST STREP

Sept’08

OneLab2 accepted as IST project (IP), 2 years6.3/8.9M€

March’07PLE

PLC/PLE Federation

http://www.onelab.eu/

…PLC/PLEPLJ Federation


OneLab ingredients

● Currently funded for 2009-10 Drawing on FP6 activities: Onelab, SAC, Evergrow

● Three Pillars: Platform, Tools and Customers

● 26 partners Industry: Alcatel, Ericsson, Thales, Thomson Operators: BT, Telekomunikacja Polska Research Labs: INRIA, Fraunhofer, Nicta Universities in France, Germany, Italy, Israel, Spain, Portugal,

Sweden, Switzerland, Hungary, Japan

● External: PlanetLab, CoreLab, WINLab (ORBIT), VINI, CAIDA, …


OneLab2 Organisation

WP0 Management

Pillar 1 - Platform

WP5 Packet

Tracking

WP4 Topology

Information

WP3 Dissemination

Pillar 2 - Tools

WP8 SAC

WP9 Benchmarking

WP7 Content

WP6 Wireless

Pillar 3 - Customers

WP1 Integration Contributes code

WP2 Operations

Provides monitoring tools

Provides

PlanetLab Europe

Delivers the OneLab Build


Contribute code


What Does OneLab Do?




Activities & Contributions (Operation)

● Operate PLE, Welcome new sites

● Document the system for users and administrators

● Deploy new federation technology: SFA Interface Allow three-way top-level federation: PLE-PLC-PLJ- … Allow “hierarchical” federation: PLE-EverLab, PLE-G-Lab, … Allow PL/OMF (Wireless)

● Develop MySlice advanced slice management tool Integration of TopHat, Etomic, Dimes Virtual Observatory Visualization tools

52


Activities & Contributions (Integration)

● Co-development between Princeton and Onelab

● Unique codebase at svn.planet-lab.org

● Notion of a “distribution” that allows to build variants

● Features and objectives Flexible, extensible data model (v4.3) Reworked web UI (v4.3) GENIwrapper / SFA (v5.0) More recent linux kernel (v5.1)

● Federation and new components integration Emulation, Wireless, …

53


Activities & Contributions (Monitoring)● Topology Discovery (WP4) based on TopHat, DIMES, ETOMIC

Specialized flexible measurement hardware High precision measurements Integration and extension of TopHat, DIMES, ETOMIC Visualization tools

● Packet Tracking (WP5) based on CoMo Provide standardized interfaces and formats (IPFIX, PSAMP) Allow distributed multipoint measurements Provide data selection techniques Provide resource management for measurement tasks Impact Standardization with own contributions

54


Objectives● To Integrate wireless technologies into a global large-scale

research infrastructure

● To define a common framework for conducting experiments in all the various OneLab wireless test beds.

Activities towards the following lines:

● Provisioning of new test bed resources, in order to properly support experimentation activities

● Development of management tools to configure and monitor those wireless networks / support the experimenter

● Development of a common test methodology that developers can follow to validate their applications or protocols

Activities & Contributions (Wireless)


SAC, Content● Explore the issues raised by the inclusion of such

environments

● The SAC Gateway concept: Environments alike ANA, Haggle, DTN

● The PubSub & CDN approaches

Benchmarking

● A methodology for running and comparing experiments

● “Controlled” environments

Activities & Contributions (Customers)


Concluding remarks● Building a facility is a major challenge

Complex process, High risk, non technical issues (IPR, Legal,)

● Onelab is about: Supporting two complementary dimensions (NS & Exp) Enabling different federations – not one size fits all Basing on an existing ecosystem with an international community

● Onelab has delivered PlanetLab_Europe (PLE): Up and running! Independent and Federated Highly visible worldwide, seen as a peer wrt other testbeds Cooperation with « Pilot » projects (PSIRP, ANA, Haggle, 4Ward,

FEDERICA) – looking for new partnerships. Aggregate tools of disperse communities


Test-Beds “As close as possible to real life!”

Join and experiment with us!


Questions


Tutorial Site

The tutorial (pdf slides) are available at:

http://www.ict-fireworks.eu

The tutorial system is available at:

http://tutorial.onelab.eu

60


Backup


The OneLab2 projectRationale and Objectives

(detailed, not to be presented)!

Serge Fdida, UPMC



From Vision to Implementation


Onelab2

● Follow on of Onelab Onelab2: IP project, 2 years, 6.3/8.9M Euro

● Responsible for Planetlab Europe Already federated with PLC http://www.planet-lab.eu/join_us

● + various stand-alone testbeds Wireless testbeds (WiMax, WiFi, Multi-link, Multi-radio) SAC testbeds (ANA/DTN)

● Specific focus on measurements tools

● Currently 46 (35 operational) sites, 77 (65 available) nodes, growing…


Onelab 1● Onelab_1 was a concrete path towards Experimental Facilities

Based on Planetlab

● OneLab will help us better understand federation, which will be key to Experimental Facility success

● OneLab will also make considerable progress in

● Extend Extend PlanetLab into new environments, beyond the traditional wired internet.

● Deepen Deepen PlanetLab’s monitoring capabilities.

● Federate Provide a European administration for PlanetLab nodes in Europe. Federate with other facilities ….


Developing the Vision

● OneLab should be developed as a multi-year facility

● Based on three pillars Platform (development, operations) Tools (monitoring) Customers (users and research targets)

● Liaison with “pilot” projects Haggle & ANA (SAC), PSIRP (Content), 4WARD (Future Internet)

● PlanetLab Europe (PLE) will grow over the years Tools found mature are integrated from OneLab2 into PLE

● Peer with PLC/GENI, PlanetLab Japan, Glab, Federica, ORBIT/OMF, …


OneLab2 Organisation

WP0 Management

Pillar 1 - Platform

WP5 Packet

Tracking

WP4 Topology

Information

WP3 Dissemination

Pillar 2 - Tools

WP8 SAC

WP9 Benchmarking

WP7 Content

WP6 Wireless

Pillar 3 - Customers

WP1 Integration Contributes code

WP2 Operations


Provides

PlanetLab Europe

Delivers the OneLab Build


Contribute code


Operations

Timur Friedman, UPMC



Our key platform is European PlanetLab● Covered by a legal framework:

Membership Agreement PlanetLab Europe has a legal status

● with Special terms for EU enterprises Private PlanetLabs possible

● Federated with Princeton and Japanese efforts MoU with PLC Aki Nakao (Univ. Tokyo) joining Onelab2 project On going discussions with Tsinghua University

● Increase the “Value” of PlanetLab_EU New users, industrial involvment PlanetLab has proved itself already, even as a production deployment

environment (Telecom Poland example)

70 - OneLab - AsiaFi– November 17, 2009 – Bangkok Thailand70

What we manage

Main operations centre EverLab opsPLC ops

Nodes


Growth of PlanetLab Europe


Nodes

Addition ofwireless(new)


Growth of PlanetLab Europe


Nodes

Addition ofemulation(new)


Future plans

● Next six months Deploy new federation technology: SFA Interface

■ Allow three-way top-level federation: PLE-PLC-PLJ- …

■ Allow “hierarchical” federation: PLE-EverLab, PLE-G-Lab, …

■ Allow PL/OMF (Wireless) Upgrade PLE, EverLab from v4.2 to v4.3 (done!)

● Ongoing Welcome new sites Document the system for users and administrators Develop MySlice advanced slice management tool

73


Integration

Thierry Parmentelat, INRIA



Integration

● Co-development between Princeton and Onelab

● Unique codebase at svn.planet-lab.org

● Notion of a “distribution” that allows to build variants

● Features and objectives Flexible, extensible data model (v4.3) Reworked web UI (v4.3) GENIwrapper / SFA (v5.0) More recent linux kernel (v5.1)


Dissemination WP3

Scott Kirkpatrick, HUJI

UPMC, HUJI, with participation from all partners



Dissemination Activities

● Two websites www.planet-lab.eu

■ Basic resource for PlanetLab Europe, its tools and associated facilities

www.onelab.eu

■ Project website, news, archive, wiki, and scheduler

□ News stories posted here with RSS feed. Newsletter in future.

□ All presentations and deliverables available to public


Education and Outreach● We have to prove the “Value” of PlanetLab to:

IST projects Industry

● Tutorials First focus on getting over the initial hurdles:

■ Registration, setup, slices, slivers, launching tests

■ Building on experience with EverLab, OneLab users

□ Strong correlation between completing tutorial and subsequent usage.

■ Tutorial addresses several classes of user, docs now separate the roles clearly for reference use

Next build demo/tutorials for advanced users


International cooperation● Participation in global federation effort

PLE – PLC

■ Already exploiting foreground technology from 2007-8 collaboration

■ Federation works in both directions today

□ Client app (e.g. Dimes client) can launch slivers on PLC from PLE or the reverse.

□ Access to private planet-labs (delegated testbeds) is next

□ A scalable federation model

■ PLE/PLC MoU signed

Planet-lab Japan and other Far Eastern groups

■ PL_Japan (Aki Nakao), Progress with China, Korea

PLE and PLC collaborate on the SFA architecture


Monitoring Tools (WP4/WP5)

Tanja Zseby, Fraunhofer FOKUS

Javier Aracil, Universidad Autonoma de Madrid (UAM)



PlanetFlow

Web GUI

CoMon

Web API,Text Files

Monitor

Web GUI

EverStats

Monitoring Agents

InformationCollection

InformationAccess

E.g.: PlanetLab monitoring

Traffic(for security)

CPU, memory, bandwidth

Reliability

Web GUI


OneLab2 Activities● Topology Discovery (WP4) based on TopHat, DIMES, ETOMIC

Specialized flexible measurement hardware High precision measurements Integration and extension of TopHat, DIMES, ETOMIC Visualization tools

● Packet Tracking (WP5) based on CoMo Provide standardized interfaces and formats (IPFIX, PSAMP) Allow distributed multipoint measurements Provide data selection techniques Provide resource management for measurement tasks Impact Standardization with own contributions


SERVERAPE

Switch

Internet

NICNIC

COMO

Span portEtomic/COMO control

ARGOS

Nanosec

GPS

Etomic control

PlanetLab boxes

Blackfin

ANME Advanced Network Monitoring Equipment

Joint Specification of WP4/5 in D 4.2: ‘Specification for advanced monitoring boxes’


From nanoseconds (ARGOS) to microseconds

● ARGOS provides a measurement resolution of tens of nanoseconds with GPS timestamping.

● PREMON Driver provides a measurement resolution of microseconds with GPS timestamping.

● We can use combinations: some equipments with PREMON and some with ARGOS.


PREMON installed on a SOM-PC

SOM-PC cost (Mini-ITX): 300 Euro.


ARGOS card (NetFPGA)

Price for university: 500 USD


Wireless WP Overview

Leandros Tassiulas, CERTH



Objectives● To Integrate wireless technologies into a global large-scale

research infrastructure

● To define a common framework for conducting experiments in all the various OneLab wireless test beds.

Activities towards the following lines:

● Provisioning of new test bed resources, in order to properly support experimentation activities

● Development of management tools to configure and monitor those wireless networks / support the experimenter

● Development of a common test methodology that developers can follow to validate their applications or protocols


Wireless-Testbeds● An IEEE 802.11 (Wi-Fi) test-bed (CERTH)

Linux platform Commercial WiFi cards (Atheros, Intel, Intersil) with open source drivers

(MadWiFi, Intel, HostAP) Focuses on MAC and network layer implementation

● An IEEE 802.16 (WiMAX) test bed (ALF, ALI) Two Base Stations, a number of mobile clients Focuses on WiMAX node configuration, evaluation of the behavior of

WiMAX in a mobile environment, handover scenarios

● A multi-link test bed (ETH) Based on PC nodes and different radio access technology devices

(HSDPA, WLAN, Bluetooth, ZigBee, 3GPP-LTE-like) Focuses on the modeling of the characteristics of cellular mobile

systems (bandwidth limitation, propagation delay, handover between routers of different technology)


Current StatusWe have developed the three testbeds:

● WiFi testbed (CERTH)

● WiMAX testbed (AL-F, AL-I)

● Multi-link test bed (WiFi link, LTE link, HSPA link)

We are working on the remote access of the testbeds.

We are developing a control and management framework based on OMF as a federation tool on the top of the testbeds.

We are developing an interface that runs between the user and the driver (currently in the WiFi testbed) that:

● Monitors the communication (channel condition, power, rates, etc)

● Controls the communication (sets the rate, power, etc)

We are conducting research in order to investigate limitations on the implementation of research ideas on the test beds

We are developing documentation and tutorials


Current StatusWe are developing a control and management framework based on

OMF as a federation tool on the top of the testbeds.

● a slicing scheme based on OMF that gives access to a remote user.

■ Reserve resources of a particular testbed

□ Particular nodes setup a slice Functioning in specific channels Using a specific max power

■ Reserve resources of different testbeds and run experiments in a unified way

□ Some nodes of one testbed (e.g. WiMAX)

□ Some nodes on another (e.g. WiFi)

□ The testbeds communicate though the wired network


Next Steps● Federation of the different testbeds though OMF

● Define a common framework for Remote reservation

Control

Management

● Develop the wireless toolkit Low cost WiFi based nodes

OMF based control framework

● Implementation of interconnection scenarios

● Testing of the developed framework

● Documentation - tutorials


Documentation

● http://omf.mytestbed.net/ (NICTA)

● http://nitlab.inf.uth.gr (CERTH)

Date post:	28-Jan-2016
Category:	Documents
Upload:	kathlyn-james
View:	218 times
Download:	0 times

1 - OneLab - AsiaFi– November 17, 2009 – Bangkok Thailand OneLab Asia Future Internet Workshop...

Documents