Static agent which resides on external system\machine

Registered by Georgy Okrokvertskhov on 2015-04-16

In order to enable an integration with 3rd party systems which are external to OpenStack Murano needs a way to send command to such system. It is possible to do if we enhance agent capabilities to manage tasks and results queue in a way that they are configured independently from environment deployment process.

For example, imagine a baremetal MySQL node which is deployed outside of OpenStack. If there is an agent which uses preconfigured task queue for receiving incoming tasks, then Murano can send tasks during different environment deployments if tasks queue is known to Murano. In order to respond to proper environment deployment agent should be able to know to which result queue it should put a response.
In this blueprint it is proposed to add additional header to the message like message.reply_to and provide a results queue name dynamically.

Blueprint information

Status:
Not started
Approver:
Ekaterina Chernova
Priority:
Medium
Drafter:
Georgy Okrokvertskhov
Direction:
Approved
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/static-agent,n,z

Addressed by: https://review.openstack.org/174175
    Add dynamic result message routing

Addressed by: https://review.openstack.org/235913
    Add dynamic result message routing

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.