Modifications for the agent:
"Control resources plane" on the event bus features for the agent:
-
heartbeat (so resource repo knows if its alive or not) -
add doc on how the topics and queues are used, also how the data plane messages should be routed -
a vhost needs to be created for these interactions (this happens outside of the session execution), something similar to /common-sevices? -
availability information should be sent through this channel too (so RR knows if the resource is available or not) -
agent logs in into session now using usr/pass which exist only during the execution of the session, do we need another set of credentials for when the agent is only heartbeating? -
how does the agent checks if the resource which is attached to is available or not? is this info manually input by the user into the agent?
issue discussed in Paris meeting 09/03/17 @fsismondi @sieben @DeviceGatewayIntern @EunahKim