yahoo-eng-team team mailing list archive

[Sylvain Bauza <sbauza@xxxxxxx>]

Public bug reported:

With https://review.openstack.org/#/c/436094/ we began using different transport URLs for Nova internal services.
That said, as notifications emit on a different topic but use the same transport URL than the component, it leads to our consumers missing notifications as they only subscribe to the original MQ.

While Nova can use multiple MQs, we should still offer the possibility
to have global notifications for Nova so a consumer wouldn't require to
modify their configs every time a new cell is issued.

That can be an oslo.messaging config option, but we certainly need to be
more gentle in Devstack or depending jobs (like for Vitrage) could fail.

** Affects: nova
     Importance: Undecided
         Status: Confirmed

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1700496

Title:
  Notifications are emitted per-cell instead of globally

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  With https://review.openstack.org/#/c/436094/ we began using different transport URLs for Nova internal services.
  That said, as notifications emit on a different topic but use the same transport URL than the component, it leads to our consumers missing notifications as they only subscribe to the original MQ.

  While Nova can use multiple MQs, we should still offer the possibility
  to have global notifications for Nova so a consumer wouldn't require
  to modify their configs every time a new cell is issued.

  That can be an oslo.messaging config option, but we certainly need to
  be more gentle in Devstack or depending jobs (like for Vitrage) could
  fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1700496/+subscriptions