Notifications are emitted per-cell instead of globally

[Sylvain Bauza]

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 [1], but we certainly need to be more gentle in Devstack or depending jobs (like for Vitrage) could fail.

[1] https://docs.openstack.org/developer/oslo.messaging/opts.html#oslo_messaging_notifications.transport_url

devstack version: pike

[Matt Riedemann (mriedem)]

We are going to need to document this in the nova cells devref as something to consider when doing multi-cell deployment.

[Matt Riedemann (mriedem)]

This does global MQ for notifications in devstack: https://review.openstack.org/#/c/477556/

[Sean Dague (sdague)]

No version was found in the description, which is required, marking as Incomplete. Please update the bug description to include 'devstack version: ... '.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/477556
Committed: https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=f3d533157267a1568eeb36a349aee637195e9c8a
Submitter: Jenkins
Branch: master

commit f3d533157267a1568eeb36a349aee637195e9c8a
Author: Dan Smith <email address hidden>
Date: Thu Jun 8 08:22:38 2017 -0400

    Fleetify nova conductor for N cells

    This makes us start two levels of nova-conductor processes, and one per cell.

    Note that this also sets the notification transport_url to the top-level mq
    so that we continue to get a unified stream of notifications.

    Related-Bug: #1700496
    Change-Id: I08d7da843d18b426dda8a8a231039d950a4c0ce5
    Depends-On: I64b600b30f6e54db0ec9083c6c176e895c6d0cc2
    Depends-On: If59453f1899e99040c554bcb9ad54c8a506adc56

[Sean Dague (sdague)]

There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments.

[Balazs Gibizer (balazs-gibizer)]

Based on Matt's comment from ML[1] the nova side of this bug has already been fixed by [2]

[1]http://lists.openstack.org/pipermail/openstack-dev/2017-August/121571.html
[2]https://review.openstack.org/#/c/487183/

[Dr. Jens Harbott (j-harbott)]

It looks like this issue was fixed via a patch to nova, please update if there is still an issue with devstack.

[Dr. Jens Harbott (j-harbott)]

[Closing for devstack because there has been no activity for 60 days.]