← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1361963] [NEW] No default control_exchange configuration prompt in glance-api.conf

 

Public bug reported:

In current default glance-api.conf, messaging configurations as below,
but actually 'rabbit_notification_exchange = glance' and
'qpid_notification_exchange = glance' do not impact topic consumer_queue
creation. because Oslo .messaging uses 'control_exchange' as queue name,
default value is 'openstack'.  other component such as cinder has
written ''control_exchange=cinder'' into cinder conf.  glance should do
same change as well.

# Messaging driver used for 'messaging' notifications driver
# rpc_backend = 'rabbit'

# Configuration options if sending notifications via rabbitmq (these are
# the defaults)
rabbit_host = localhost
rabbit_port = 5672
rabbit_use_ssl = false
rabbit_userid = guest
rabbit_password = guest
rabbit_virtual_host = /
rabbit_notification_exchange = glance
rabbit_notification_topic = notifications
rabbit_durable_queues = False

# Configuration options if sending notifications via Qpid (these are
# the defaults)
qpid_notification_exchange = glance
qpid_notification_topic = notifications
qpid_hostname = localhost
qpid_port = 5672
qpid_username =
qpid_password =
qpid_sasl_mechanisms =
qpid_reconnect_timeout = 0
qpid_reconnect_limit = 0
qpid_reconnect_interval_min = 0
qpid_reconnect_interval_max = 0
qpid_reconnect_interval = 0

** 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/1361963

Title:
  No default control_exchange configuration prompt in glance-api.conf

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  In current default glance-api.conf, messaging configurations as below,
  but actually 'rabbit_notification_exchange = glance' and
  'qpid_notification_exchange = glance' do not impact topic
  consumer_queue creation. because Oslo .messaging uses
  'control_exchange' as queue name, default value is 'openstack'.  other
  component such as cinder has written ''control_exchange=cinder'' into
  cinder conf.  glance should do same change as well.

  # Messaging driver used for 'messaging' notifications driver
  # rpc_backend = 'rabbit'

  # Configuration options if sending notifications via rabbitmq (these are
  # the defaults)
  rabbit_host = localhost
  rabbit_port = 5672
  rabbit_use_ssl = false
  rabbit_userid = guest
  rabbit_password = guest
  rabbit_virtual_host = /
  rabbit_notification_exchange = glance
  rabbit_notification_topic = notifications
  rabbit_durable_queues = False

  # Configuration options if sending notifications via Qpid (these are
  # the defaults)
  qpid_notification_exchange = glance
  qpid_notification_topic = notifications
  qpid_hostname = localhost
  qpid_port = 5672
  qpid_username =
  qpid_password =
  qpid_sasl_mechanisms =
  qpid_reconnect_timeout = 0
  qpid_reconnect_limit = 0
  qpid_reconnect_interval_min = 0
  qpid_reconnect_interval_max = 0
  qpid_reconnect_interval = 0

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


Follow ups

References