Ability to have different Rabbit connections for Sink

Bug #1688621 reported by Adrien Cunin
This bug affects 3 people
Affects Status Importance Assigned to Milestone

Bug Description

It'd be nice to be able to configure Designate Sink to connect to a different RabbitMQ server/vhost than the global Designate RabbitMQ server/vhost.

Example use case: you have one vhost per OpenStack service (one for Nova, one for Neutron, one for Designate, etc.), and you want Designate Sink to listen to the notifications emitted by Nova and Neutron... which are in their own vhost.

Revision history for this message
Tim Simmons (timsim) wrote :

This is more of a feature request. I agree it could be useful, if you'd like to push forward with this, file a blueprint, and write up a quick spec! It would be very helpful.

Changed in designate:
status: New → Invalid
Revision history for this message
Dmitriy Rabotyagov (noonedeadpunk) wrote :

So I found https://blueprints.launchpad.net/designate/+spec/rabbit-connections-sink as a blueprint but not sure there were some actions regarding it

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers