A single sdx-controller instance alone is not very helpful during development (against the sdx-controller's REST APIs, for instance.) It seems to me that development can be a little simpler if we are able to publish the topologies on the message queue which sdx-controller can consume.
A single sdx-controller instance alone is not very helpful during development (against the sdx-controller's REST APIs, for instance.) It seems to me that development can be a little simpler if we are able to publish the topologies on the message queue which sdx-controller can consume.
Perhaps the scripts in https://www.rabbitmq.com/tutorials/tutorial-five-python.html can help, or maybe
amqp-publishfrom amqp-tools.