AGILE 2nd F2F MEETING, 14-15 April 2016, Athens, GR

1. Pilot – Testbed
LEADER: INRIA
INVOLVED PARTNERS: CREATE-NET, INRIA
AGILE MEETING, 14-15 April 2016, Athens

2. Testbed Overview: IoT-LAB
§ HW and SW Infrastructure already in place for remote, bare-metal
access to 2700+ IoT-devices.
§ Online tools for IoT node firmware upload, experiment configuration,
experiment results download.
AGILE MEETING, 14-15 April 2016, Athens

3. From the user perspective
Like a Raspberry Pi + an associated programmable “mote” (with
802.15.4 radio)
Except you can have 100s of them
And you connect through ssh (tunnel through IoT-LAB server)

4. From admin perspective
… plus backend management system
Management
(Linux + mote
802.15.4, sniffer…)Open A8
+ M3 mote

5. IoT-LAB @Inria-Saclay
~200 A8 nodes
~100 WSN 430

6. IoT-LAB @Inria-Saclay

7. IoT-LAB @Inria-Saclay

8. Planned Testbed Extension
Many variations, but main objective:
connect indirectly to the
Agile gateway through the
Open A8.
Management
(Linux + mote
802.15.4, sniffer…)
Open A8
+ M3 mote
Agile Gateway

9. Planned Testbed Extension
USB plugged-in AGILE gateway hardware on IoT-LAB host A8-M3 nodes
AGILE MEETING, 14-15 April 2016, Athens
Blue: userland
Yellow: admin
Green: userland extension

10. Requirements
§ SW: the testbed offers bare-metal access to IoT devices, so there is no SW
requirements on IoT devices. No specific req. on AGILE gateway SW either
(except: must be able to run on AGILE hardware e.g. RasPi)
§ HW: IoT devices are currently IEEE 802.15.4 only on the targeted IoT-LAB
site => AGILE gateway should have a IEEE 802.15.4 communication module
(which may be a USB-connected board running RIOT).
§ Security requirements:
§ ssh tunnel to AGILE gateway, where AGILE interfaces can be used (and
corresponding security considerations apply).
§ Bare-metal access to IoT-devices: e.g. RIOT firmware running on IoT-LAB M3
nodes, with IPv6/6LoWPAN/RPL/UDP stack (and corresponding security
considerations apply).
§ Data management, post-processing and visualization: up to the testbed
users. Out of scope for the testbed tools. Pre-processing possible on the IoT-
devices (programmable in the firmware uploaded on IoT devices e.g. RIOT)
AGILE MEETING, 14-15 April 2016, Athens

11. Open Issues
§Industrial gateway vs Maker gateway (and how many ?)
§Framework to avoid user-initiated file-system « bricking » on the gateway
§ Based on NFS boot?
§Final decision between several possible levels of integration:
§ Level 1: adding new IoT devices to IoT-LAB (connecting them through USB to
one of the A8-M3 nodes)
§ Level 2: adding new gateways to IoT-LAB (e.g. AGILE gateway)
◦ connecting via an existing Open A8 - maybe USB-Ethernet
◦ connecting to the private Ethernet of IoT-LAB local server
◦ alternative: connect via an additional private server, with an admin VM dedicated to AGILE.
§ Level 3: modifying SW (currently a customized OpenEmbedded - Yocto Daisy) on
IoT-Lab A8 nodes so that they become an AGILE Gateway, e.g. using Snappy
AGILE MEETING, 14-15 April 2016, Athens

12. Next Steps
§Level 1: ongoing, planned for different IoT device hardware (see annex)
§Level 2 : described in the document “Agile IoT Testbed”:
§ discussion in Annex
§ decision which way to go
§ Plug in AGILE gateway hardware (maker version)
AGILE MEETING, 14-15 April 2016, Athens

13. Integration of IoT device
FIT A8 node
Arduino node