controller API gateway

[cdupont]

The role of the controller is to expose the external API and forward the requests to internal services.
Currently the controller is implemented as a Python program doing the translation.
However it would be simpler and more modular/future proof to implement it with an HTTP proxy like nginx or Apache tomcat.

Some links on the API gateway pattern and implementation:
http://microservices.io/patterns/apigateway.html
https://www.nginx.com/blog/building-microservices-using-an-api-gateway/

Currently the controller is also enforcing the IoT-lite format on the API, before translating the data to Orion.
This function should be moved to a separate wrapper located in the "broker" pod.

[cdupont]

This pattern also would make the identification/security easier: #13
New services can be exposed in the gateway: #18

[cdupont]

I created the proxy. Some quick instructions here: https://github.com/Waziup/Platform/tree/master/orchestrator/kube-system

[cdupont]

Mapping proposed:

• www.waziup.io -> platform website
• api.waziup.io -> controller API (regroup all APIs)
• broker.waziup.io -> orion API
• sms.waziup.io -> sms API

See https://github.com/Waziup/Platform/tree/master/orchestrator/README.md

[cdupont]

Done, see: https://github.com/Waziup/Platform/tree/master/controller