Guide for Extensions

3 Testbed Provider Services (Testbed to FIESTA-IoT)

3.4 Testbed Configuration management

In this section, we are going to introduce the User Interface that is provided by FIESTA-IoT in order to facilitate the testbed provider manage the testbed behaviour with the FIESTA-IoT platform. FIESTA-IoT offers a TPI configuration UI that enables the testbed provider to discover the semantically registered resources of his/her testbed, by utilizing the IoT-Registry services. Moreover, it manages the data retrieval process, by utilizing the TPI DMS services.

The TPI Configurator UI can be found at the FIESTA-IoT portal under the Testbed Provider Menu (see 1st Figure below) by clicking the “TPI Configurator”.

As soon as the tool opens it identifies the user and automatically searches for Testbeds bound with the logged-in User ID. The available testbeds are listed at the Testbed dropdown list of the tool’s Discovery tab (see 2nd Figure below).

When a testbed is chosen the registered resources appear at the resource list where the user can select in order to proceed with their data retrieval scheduling (see 2nd Figure above and 3rd Figure below) by hitting next.

The Testbed provider can now define a specific schedule to retrieve their measurements. This is achieved by defining it in the “Schedule” tab as shown in 4th Figure below. In the schedule tab the user can specify the properties of the schedule to be defined and these are:

  • a name for the schedule,
  • to choose the Testbed ‘s exposed service (TPS) (see 4th Figure below) that has already been defined in the Testbed registration process. This Testbed URI will expose one of the TPS services (i.e. get observation, push observation etc.),

  • Select the Security Key (see 5th Figure below), identified in the Testbed registration process, in order to access the Testbed URI above and

  • To specify a timeschedule (if the get methodology for TPS has been implemented) for the daretrieval (get) to be executed from the DMS to TPS component. This is achieved by identifying:
    • The start time (optional): which defines a historical date in order to adittionally retrieve historical measurements for a resource (i.e. to retrieve the data from last month set the start time date 30 days in the past). Note that this feature is not curently implemented.
    • The frequency and the time unit of it which defines the periodicity frequency of the measurements retrieval (get) from the Testbed’s TPS.

After completing the required flow and the definition of the requested properties, the testbed provider needs to hit the schedule button (see 6th Figure below) to initiate both the equivalent service of the TPI DMS and the process of pushing data to FIESTA-IoT platform or retrieving data from the Testbed (depending on the TPS service implemented from the Testbed TPS).

This step will take the Testbed Provider to the status tab (see 7th Figure below) where an overview of all the scheduled jobs can be found. In case the Experimenter needs to stop a job the job should be picked from the Status list and the stop button should be clicked (see 7th Figure below). This stops the schedule for the specific job of retrieving measurements from TPS (in case the get method has been implemented) or instructs TPS to stop pushing measurements to DMS (in case the push methodology was chosen).