devstack

Use get_notification_url when configuring oslo.messaging notifications

Bug #1708754 reported by Ken Giusti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
devstack
Fix Released
Undecided
Ken Giusti

Bug Description

oslo.messaging allows deployments to use two separate messaging backends - one dedicated for RPC and another for Notifications. For example this allows a deployment to configure a rabbitmq server to write all notifications to persistent store (slow), while RPC can be deployed over a lightweight point to point system like ZeroMQ

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to devstack (master)

Fix proposed to branch: master
Review: https://review.openstack.org/491103

Changed in devstack:
assignee: nobody → Ken Giusti (kgiusti)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to devstack (master)

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

commit b645904d4aae46a8be5cee3a23710565b211f458
Author: Kenneth Giusti <email address hidden>
Date: Fri Aug 4 18:08:37 2017 -0400

    Use get_notification_url when configuring notifications

    If a project manually configures the oslo.messaging transport url for
    notifications it should use 'get_notification_url', not
    'get_transport_url'. get_transport_url should only be used to obtain
    the RPC transport address.

    Change-Id: I77772dfa9f30a3db2db6d0387260dfe3452a26ef
    Closes-Bug: #1708754

Changed in devstack:
status: In Progress → Fix Released
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.