No default control_exchange configuration prompt in glance-api.conf

[Jin Liu]

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

[Jin Liu (liujinbj)]

https://review.openstack.org/#/c/117115/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/104476
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=819f28a0b8863bd18f8a14491b5966c8b2723432
Submitter: Jenkins
Branch: master

commit 819f28a0b8863bd18f8a14491b5966c8b2723432
Author: Zhi Yan Liu <email address hidden>
Date: Thu Mar 27 17:39:14 2014 +0800

    Enabling separated sample config file generation

    As a common approach most projects used now and Oslo preferred, this
    change enabled sample configuration file generation mechanism for
    each Glance services.

    This change, as an enhancement, allows generating separated sample
    configuration files for each Glance major services, e.g.:

        etc/glance-api.conf.sample
        etc/glance-cache.conf.sample
        etc/glance-manage.conf.sample
        etc/glance-registry.conf.sample
        etc/glance-scrubber.conf.sample

    It is different than I94d486d6686815c45705a7a9b00fb26062e1eb63
    which only supports generating an unified sample configuration
    file to including all Glance available options.

    This mechanism not only can help auditing by packager, milestone
    maintainer or developer as a function (testenv) of tox, but also
    those separated configuration files could make deployment be easy.
    And it helps keeping sample configuration files be update with
    code change.

    The change added "genconfigs" function as a tox testenv (-egenconfigs),
    and it dependes on oslo-config-generator function of oslo.config.

    The change doesn't introduce those sample files Glance repo, so
    next step is to investigate if we can generate them in gate
    automatically when a change was merged.

    Related-Change-Id: I15686708fc9460948a58cfea3d18dae40ba1fda9
    Related-Change-Id: Iae31856d5886ee78786972d80c7c103c3460a2b3
    Related-Change-Id: I76043b08e2872867e5af2a5ac902e4d092fda5c8
    Closes-Bug: #1300546
    Closes-Bug: #1361963

    Change-Id: Ibe03a3fe80b96ca32acb1a6bea7e38e6075951bb
    Signed-off-by: Zhi Yan Liu <email address hidden>