Actions

Talk

Difference between revisions of "UMOBILE Lab"

From UMOBILE Documentation

Line 1: Line 1:
 +
The UMOBILE researchers can login and access the lab XXXX via VPN^ E CHE FANNO? prego spiegarlo.
  
OOOO
+
XXXX An option is to open the lab to foreign (non-UMOBILE) researchers, stating which is the the expected appropriate usage of the lab in a guideline or a policy statement or a similar document.
RouterOS sono solo infrastruttura
+
Sebbene non appare utile, e' possibile cambiare il routing iP
+
  
OOOO
+
At the moment the UMOBILE Lab is mainly constituted of some Raspb PI, marked as SEG in the figure "UMOBILE testbed..."; the Mikrotik devices are just used as (IP) routing infrastructure. Each SEG runs the UMOBILE software image and is NDN-connected to other SEGs, through NDN tunnels. The NDN tunnels lay over the IP layer; it is not considered an interesting option to modify the IP routing layer, in order to get modifications of the NDN layer. Instead it is possible to change the NDN topology changing the NDN routes/tunnels; the figure below represents the idea.
  
 +
XXXX figure
  
At the moment the UMOBILE Lab is mainly constituted of some Raspb PI, marked as SEG in the figure "UMOBILE testbed...". Each SEG runs the UMOBILE software image and is NDN-connected to other SEGs, through NDN tunnels (over IP).
+
There is an NDN node in the lab (the ''first node'') that is exposed over the internet with a public IP address. This node could be connected to the [https://named-data.net/ndn-testbed/ Named Data Networking Testbed], that already reaches the AFA Systems plant. Consequently every node of the UMOBILE Lab could be reached from any other node of the NDN testbed; COPELABS is connected to to the NDN testbed, too: we expect it is possible to exchange (UMOBILE) messages between devices/apps at COPELABS Research Center with devices/apps at UMOBILE Lab.
  
The NDN layer is above the IP layer.
+
== Experiments and Dashboards ==
 +
A useful and appealing lab should have clear dashboards and easy-to-configure parameters. As Paulo suggested some days ago, a good example of an on-line lab is the [https://www.iot-lab.info/tools/ FIT IoT-Lab].
  
Strictly remaining on the IP level, you can get different topology of the lab changing the routes inside devices; the figure below represents the idea.
+
Changing the parameters should change the configuration of the lab (e.g. the topology of the NDN links) in order to run different experiments. A comfortable GUI should allow to set the parameters, as well to load n-uples of parameters with just one command.
  
 +
The dashboards should allow to browse the data structure of the different nodes; e.g. the FIB. Any significant data structures should be displayed.
  
e' costituito dai RaspB (SEG, che implementa l'NDN, attraverso i tunnel)
+
The results should be collected and measured through specific dashboards.
  
Il primo nodo NDN potrebbe essere collegato al testbed pubblico.
+
For each device and UMOBILE software image there would be hooks (i.e. API) to set parameters and access the significant data structures.
  
 +
 +
 +
XXXX
 +
Rileggere email di Paulo
  
 
Quali sono gli entry-point nei SEG per parlare con i device NDN mobili (es. l'app di Paulo)
 
Quali sono gli entry-point nei SEG per parlare con i device NDN mobili (es. l'app di Paulo)
Line 24: Line 30:
  
 
Ha senso modificare i tunnel NDN?
 
Ha senso modificare i tunnel NDN?
 
Le dashboad: possiamo web-impaginare le FIB; ma che altro?
 
  
 
E' utile provare il protocollo di routing (standard) NDN? come si fa? c'e' una versione UM?
 
E' utile provare il protocollo di routing (standard) NDN? come si fa? c'e' una versione UM?
 
 
 
 
== Some ideas to improve the UMOBILE Lab ==
 
A good example of an on-line lab is the FIT IoT-Lab (https://www.iot-lab.info/tools/) (as Paulo suggested some days ago). The overall meaning of such a lab is to allow the ''configuration'' of testbeds to run experiments.
 
 
 
 
There would be GUIs and APIs to control and measure the results.
 
Currently the UMOBILE researchers can login into the lab
 
 
E CHE FANNO?
 
 
There would be also a way (and a policy) to allow foreign (non-UMOBILE) researchers to login and use the lab.
 
 
 
=== ''Configuration'' of testbeds ===
 
We may call ''testbeds'' or ''experiments'' the configuration of the devices in the lab to get a specific architecture among the possible ones.
 
 
 
 
XXXX FIG
 
 
 
 
In order to run different experiments (or trial: a campaign of "stimula" (i.e command sequences on the "user (handheld) devices") along with the generated results and collected measurements
 
 
=== Dashboards
 

Revision as of 23:18, 7 November 2017

The UMOBILE researchers can login and access the lab XXXX via VPN^ E CHE FANNO? prego spiegarlo.

XXXX An option is to open the lab to foreign (non-UMOBILE) researchers, stating which is the the expected appropriate usage of the lab in a guideline or a policy statement or a similar document.

At the moment the UMOBILE Lab is mainly constituted of some Raspb PI, marked as SEG in the figure "UMOBILE testbed..."; the Mikrotik devices are just used as (IP) routing infrastructure. Each SEG runs the UMOBILE software image and is NDN-connected to other SEGs, through NDN tunnels. The NDN tunnels lay over the IP layer; it is not considered an interesting option to modify the IP routing layer, in order to get modifications of the NDN layer. Instead it is possible to change the NDN topology changing the NDN routes/tunnels; the figure below represents the idea.

XXXX figure

There is an NDN node in the lab (the first node) that is exposed over the internet with a public IP address. This node could be connected to the Named Data Networking Testbed, that already reaches the AFA Systems plant. Consequently every node of the UMOBILE Lab could be reached from any other node of the NDN testbed; COPELABS is connected to to the NDN testbed, too: we expect it is possible to exchange (UMOBILE) messages between devices/apps at COPELABS Research Center with devices/apps at UMOBILE Lab.

Experiments and Dashboards

A useful and appealing lab should have clear dashboards and easy-to-configure parameters. As Paulo suggested some days ago, a good example of an on-line lab is the FIT IoT-Lab.

Changing the parameters should change the configuration of the lab (e.g. the topology of the NDN links) in order to run different experiments. A comfortable GUI should allow to set the parameters, as well to load n-uples of parameters with just one command.

The dashboards should allow to browse the data structure of the different nodes; e.g. the FIB. Any significant data structures should be displayed.

The results should be collected and measured through specific dashboards.

For each device and UMOBILE software image there would be hooks (i.e. API) to set parameters and access the significant data structures.


XXXX Rileggere email di Paulo

Quali sono gli entry-point nei SEG per parlare con i device NDN mobili (es. l'app di Paulo)

Come fa l'applicazione di Paulo a parlare con il lab?

Ha senso modificare i tunnel NDN?

E' utile provare il protocollo di routing (standard) NDN? come si fa? c'e' una versione UM?