yahoo-eng-team team mailing list archive

[Juan Antonio Osorio Robles <jaosorior@xxxxxxxxxx>]

Public bug reported:

This applies mostly for code-correctness. configuring notifications
using the standard options in the default group is meant to be
deprecated in favor of options in the group
oslo_messaging_notifications[1]. So basically what this enables is to be
able to use that group to configure the notifications. As a fallback,
the default group will still work though.

Usually this is useful to be able to configure a separate vhost and user
for notifications and for RPCs; But glance doesn't really have this
problem as it's using oslo.messaging only for notifications.

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

** Affects: glance
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1567231

Title:
  glance using get_transport and not the correct
  get_notifications_transport for oslo.messaging configuration

Status in Glance:
  New

Bug description:
  This applies mostly for code-correctness. configuring notifications
  using the standard options in the default group is meant to be
  deprecated in favor of options in the group
  oslo_messaging_notifications[1]. So basically what this enables is to
  be able to use that group to configure the notifications. As a
  fallback, the default group will still work though.

  Usually this is useful to be able to configure a separate vhost and
  user for notifications and for RPCs; But glance doesn't really have
  this problem as it's using oslo.messaging only for notifications.

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

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