Guide for Extensions

7 Testbed Configuration management

7.2 Scheduling and Status

In this section, we are going to introduce the User Interface that is provided by Fiesta−IoT in order to facilitate the testbed provider to 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) by clicking the “TPI Configurator”.

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 the 2nd Figure. 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 2nd Figure) that has already been defined in the Testbed registration process. This Testbed URI will expose one of the TPS services (i.e. getLastObservations, pushLastObservations, etc.),

  • In order for Fiesta−IoT DMS to access the Testbed URI above, if your testbed is protected with API Key, select the Security Key (see 3rd Figure), as you reported it in the Testbed registration process. If your testbed does not use an API Key for authorizing requests on your TPS, leave it blank.

  • To specify a timeschedule (if the get methodology for TPS has been implemented) for the data-retrieval (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.
    • If push-based TPS method is selected (i.e. pushLastObservations), the Time Schedule options are not visible.

After completing the required flow and the definition of the requested properties, the testbed provider needs to hit the schedule button (see Figure above) 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 where an overview of all the scheduled jobs can be found. In case the Testbed Provider needs to stop a job, the job should be picked from the Status list and the stop button should be clicked . 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).