IOTMODULES.md

IoT Platform allows to enable or disable some IoT Modules for each register Service.

IoT Modules are optional features, like persistence services or GPS location service.

Orchestrator allows enable or disable these IoT Modules per service (aka keystone domain) or subservice (aka keystone project). There are an API and a command to handle IoT Modules through Orchestrator.

Enable or disable an IoT Module implies subscribe or unsubscribe IoTModule in Orion Context Broker for all entities.

IoT Module endpoints are just used as reference in Orion Context Broker subscriptions, but are never invoked by Orchestrator directly. An IoT Module is going to be a Context Application subscribed in Orion Context Broker, so an IoT Module is going to be notified by Orion Context Broker. By default notify path will be /notify, but can be overwrite in each IoT module endpoint configuration, by defining "notifypath".

IoT Modules are defined in Orchestrator configuration files, typically a file like that in this sense:

There is a list of possible IoT Modules:

IOTMODULES = [ "STH", "CYGNUS", "PERSEO" ]

For each IoT Module there is an object to define fully related endpoint. This object has IoT Module name, like aboe names:

STH = {
    "host": "localhost",
    "port": "8666",
    "protocol":"http",
    "notifypath":"/notify"
}

This way to add a new IoT Module into Orchestrator you should add something like this to [conf]((https://github.com/telefonicaid/orchestrator/blob/master/src/settings/dev.py) file

IOTMODULES = [ "STH", "CYGNUS", "PERSEO", "MYNEWMOD" ]

MYNEWMOD = {
    "host": "localhost",
    "port": "7777",
    "protocol":"http",
    "notifypath":"/mynotify"    
}