-
Notifications
You must be signed in to change notification settings - Fork 0
Thoughts on deployment
I just want to jot down some thoughts/ideas on how I would like to deploy this system.
The sensor processor is something that needs to be connected with the sensors. If any changes need to be made to this component or any changes to the sensor config then it will have to be scpd directly on to it. In the event you have multiple sensor processors, then Chef and Puppet could be of assistance.
This needs to be somewhere accessible to both the sensor and notification processors. Currently, everything can be hosted locally and it would all work fine since the notification processor is the only thing that needs the internet.
The notification processor needs to be able to connect to the MQTT broker and the internet since it uses services like Twilio to send the notifications out.
If the notification processor could run as an app on a PaaS like Cloud Foundry, it would work in terms of scale. I could deploy multiple notification processors although some more work needs to be done in terms of tracking notifications sent for issue #15.
Also it needs to contact a MQTT broker via a service. Currently, such a service doesn't exist.
I would like to investigate how hard it is to hook up a cloudfoundry app to a service like CloudMQTT to automatically provision me an account so I can start using it with my notification processor.
The only issue will be trying to share the creds/url of the online mqtt broker to the sensor processor so it can relay sensor values.