Designate

Designate cannot listen for notifications in different RabbitMQ vhosts

Bug #1578199 reported by György Szombathelyi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Designate
Opinion
Undecided
Unassigned

Bug Description

Designate can not receive notifications, when neutron and nova are configured into different RabbitMQ vhosts.
IMHO it would be nice to copy the notifications configuration from ceilometer, when one can specify one ore more URL where the notification exhange is.
e.g.

[handler:nova_fixed]
messaging_urls = rabbit://nova:pass@rabbit_cluster_host1:5672/nova
messaging_urls = rabbit://nova:pass@rabbit_cluster_host2:5672/nova
messaging_urls = rabbit://nova:pass@rabbit_cluster_host3:5672/nova

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

This is more of a feature request than a bug, it would require at least a designate-sink change, and likely an oslo.messaging change as well. If you'd like, you can file a blueprint for this :)

Changed in designate:
status: New → Opinion
Revision history for this message
György Szombathelyi (gyurco) wrote :

I thought about creating a blueprint, but the new neutron external DNS integration makes the sink somewhat obsolete.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.