Embed Size (px)
Citation preview
Federation for Future Internet Research and
Experimentation August 21th 2013, Daejeon, Korea
Piet Demeester
2
Fed4FIRE – general info � Federation for FIRE � FP7 IP project � 10/2012 - 9/2016
Project partners
§ project coordinated by iMinds § Total budget: 7.75 MEUR
3
Fed4FIRE – general info � Federation for FIRE � FP7 IP project � 10/2012 - 9/2016
Project partners
§ project coordinated by iMinds § Total budget: 7.75 MEUR
Individual TESTBEDs
Integrated FIRE CLOUD FACILITY
Individual TESTBEDs
Integrated FIRE CLOUD FACILITY
FEDERATED FIRE FACILITY
7
Basic Approach
Facilities / Testbeds
Common Federation Tools
Experimenter
8
Basic Approach
9
Basic Approach
10
Detailed Approach: Common Federation Tools Resource discovery
• Show me all resources available in the Fed4FIRE federation
Resource requirements
• Limit to wireless camera’s, network emulation, server and cloud nodes
Resource reservation
• Reserve 3 wireless nodes on testbed X and one on testbed Y and … Friday
Resource provisioning
• Friday: deploy them and use Ubuntu 12.04 LTS
• Start wireless, after 10 s, start video streams from cameras over wireless network, after 50 s start introducing packet loss on the route from camera to server, etc. Experiment control
• Facility monitoring: crucial servers up and running? à testbed up and running • Infrastructure monitoring: CPU load, wireless spectrum interference • Experiment measurement: measure actual throughput, delay and jitter.
Monitoring
• Store measurements on the storage server of testbed X for later analysis Permanent storage
• I’m done with them at 15h already, release my resources so they can be used by other experimenters. Resource release
11
Fed4FIRE facilities
PlanetLab Europe
UNIVBRIS OFELIA island
FuSeCo playground
i2CAT OFELIA island
Smart Santander facility
NETMODE wireless testbed
NITOS wireless testbed
Grid’5000
EPCC BonFIRE testbed
iLab.t Virtual Wall
Sydney: NORBIT testbed
Korea: KOREN testbed
iLab.t Wireless lab
Outside EU
Outside EU
ARCHITECTURE
13
Design Principles
� Distributed architecture ◦ User tools can interact directly with the testbeds ◦ Centralized components are introduced for
convenience. They are not strictly needed to operate the federation
� Based on open APIs ◦ Testbeds keep their own management software ◦ But Fed4FIRE defines the APIs that they should
support on top of that (SFA, FRCP, OML, …) Influenced by sustainability considerations
14
Split up of architecture figures Figure 1
• Resource discovery
• Resource requirements
• Resource reservation
• Resource provisioning
• Resource release
• Authentication & authorization
Figure 2
• Experiment control
Figure 3
• Facility monitoring
• Infrastructure monitoring
• Experiment measuring
15
Exp
erim
ente
r Te
stbe
d Te
stbe
d m
anag
emen
t
Testbed A Testbed B Federation facilitator
Bro
kers
[Figure 1]
16
Exp
erim
ente
r Te
stbe
d Te
stbe
d m
anag
emen
t
Testbed A Testbed B Federation facilitator
Bro
kers
Testbed directory
Identity provider
Certificate directory Tool directory
Identity provider
[Figure 1]
Portal (portal.fed4fire.eu)
17
Exp
erim
ente
r Te
stbe
d Te
stbe
d m
anag
emen
t
Testbed A Testbed B
Rules-based authorization
Grant access?
Rules-based authorization
Grant access?
Federation facilitator
Bro
kers
Discovery, reservation, provisioning, release
Discovery, reservation, provisioning, release
Testbed directory
Identity provider
Tool directory
Identity provider
[Figure 1]
Certificate directory
Portal (portal.fed4fire.eu)
18
Exp
erim
ente
r Te
stbe
d Te
stbe
d m
anag
emen
t
Testbed A Testbed B
Discovery, reservation, provisioning, release
Discovery, reservation, provisioning, release
Testbed directory
Identity provider
Rules-based authorization
Rules-based authorization
Identity provider
Federation facilitator
Portal (portal.fed4fire.eu)
Bro
kers
Certificate directory
Tool directory
Define scenario
Experiment control server
Define scenario
Experiment control server
[Figure 2]
19
Exp
erim
ente
r Te
stbe
d Te
stbe
d m
anag
emen
t
Testbed A Testbed B
Discovery, reservation, provisioning, release
Discovery, reservation, provisioning, release
Testbed directory
Identity provider
Rules-based authorization
Rules-based authorization
Identity provider
Federation facilitator
Central facility monitoring (first level support)
Bro
kers
Certificate directory
Tool directory
Measurement Measurement
Get monitor data
Infrastructure monitoring
Facility monitoring
Facility monitoring
[Figure 3]
IMPLEMENTATION, TESTING and INTEGRATION
21
Exp
erim
ente
r Te
stbe
d R
esou
rce
Test
bed
man
agem
ent
Discovery, reservation, provisioning
OML Filter
OML store
in SQL
OML visua-liser
Measurements & monitoring
OML stream
Nagios server
RRDTool (collectd)
Zabbix server
OML stream
ML
OML stream
MA
MA stream
AM: Aggregate Manager EC: Experiment controller RC: Resource controller
ML: Measurement Library MA: Monitoring Agent
SFA
AM
SFA
F4F Portal MySlice
Flack
Omni SFI jFED
RC
FRCP
OMF6 EC
NEPI
SSH client
Experiment control
FRCP SSH
OMF6 EC
XMPP server
SSH
SSH
FRCP
22
Testing and integration steps Detailed functional description
Development
Manual testing per testbed with jFed
Automatic nightly testing of testbeds with jFed
Cross and integration testing between tools and testbeds
23
Manual testing with jFed Supported APIs
Supported functions per API
Testbed under test
Detailed call analysis
24
Automatic testing with jFed
Testbed under test
Test scenarios
Results
25
Detailed jFed test reports
26
Detailed jFed test reports (incl. failures)
27
jFed for FLS monitoring - screenshot
Test connectivity to testbed (1min)
Test for aggregate manager (15min)
Available resources on testbed (15 min) What the testbed
internal monitoring says at the testbed premises (5 min)
29
Acknowledgement � This work was carried out with the support of the
Fed4FIRE-project (“Federation for FIRE"), an Integrated project funded by the European Commission through the 7th ICT-Framework Programme. (318389)
� I also would like to thank all my colleagues in the Fed4FIRE project
