IoT M2M DaaS

This page contains the necessary steps for deploying the IoT part of the M2M, possibly on different cloud than the M2M DaaS.

This part of the M2M DaaS can be deployed either as a whole (sensors+processing+queue together) or separately, firstly deploying the processing infrastructure which is part of the M2M DaaS, and then deploying the sensors which are producing the workload. The sensors which we have here are simulating actual sensors from smart cities, sending location data in this case.

For the first version, we provide a TOSCA description to be used for Salsa automatic deployment. In this case, the artifacts are located on the Salsa server (e.g., http://128.130.172.215/salsa/), under upload/files/DaasService/IoT/. Here we also have the .sh instantiation scripts, which are downloading appropriate artifacts from the Salsa server and installing the needed software. In this case, please use the artifacts from DaaSForSalsa branch (available here)

For the case we don't want to use Salsa, we have the following three steps for the three components that need to be deployed:

• for the MQTT queue, run run_mqtt_broker.sh, in the same folder as the mqtt chef solo cookbook (here).
• for the local processing component, run install-local-analysis-service.sh in the same folder as the local processing artifact (here).
• for the sensor, run run_sensor.sh in the same folder as the sensor chef solo cookbook (chef-sensor).