This parameter was deprecated during Yoga cycle[1] because it has been
invalid.
[1] 8bb784d524
Related-Bug: #1955510
Change-Id: I412625e9c741a20c3661f6a2ae17b6e16788b60a
The [oslo_messaging_rabbit] default_notification_exchange does not
exist and the parameter belongs to the oslo_messaging_amqp section
instead from the beginning[1].
This change deprecates that invalid support directly, instead of fixing
it, because it has never worked as expected.
[1] https://review.opendev.org/c/openstack/oslo.messaging/+/333531
Closes-Bug: #1955510
Change-Id: Ic01da52434b5791da3e34fb5bfa8ff1d704e52fa
This patch removes support for glance-registry service, because it has
been removed from glance [1].
[1] https://review.opendev.org/#/c/738671/
Change-Id: Id05f736dbbddaff2cb90aa6678c777b9a0318e40
oslo.messaging RabbitMQ driver have now a new option that allow user to
run the RabbitMQ heartbeat over a native python thread.
These change allow user to use this new option.
Change-Id: I5a322d3bbcd08443a3f5b9cf5f8e93a7435c0224
Closes-Bug: #1840868
Adds the kombu_failover_strategy option for configuring
oslo.messaging.rabbit. This will determines how the next RabbitMQ node
is chosen in case the one we are currently connected to becomes
unavailable.
Change-Id: Id360da722f4bacab3835ab8b48d4de95df700736
Closes-Bug: #1748353
Add control_exchange to configure an exchange name for message.
Add rpc_response_timeout to configure seconds time for waiting
for a response from a call.
Change-Id: I255c4ceda252f0f39eecc823cef2820c9e7b1e48
The rabbitmq connection parameters have been deprecated in favor of the
transport_url setting.
Change-Id: I891570dde75dc58f45e5ad6386be9e522b2706eb
Related-Bug: #1625198
This adds defined anchor points for external modules to hook into the
software install, config and service dependency chain. This allows
external modules to manage software installation (virtualenv,
containers, etc) and service management (pacemaker) without needing rely
on resources that may change or be renamed.
Change-Id: If683fbd098e701a3c4da91941cf818b18b41b209
Additonal changes:
* switch messaging related parameters to $::os_service_default
as they are used in oslo::messaging_rabbit define
* update unit tests
* update docs for notify::rabbitmq class
* drop deprecated rabbit_durable_queues parameter
* fix notification parameters according to mitaka config file
Change-Id: Ib20c13f136a299c958d9ac064e8ad93ceb0ebd40
There are two ways for setting up RabbitMQ HA:
1. Configure $rabbit_hosts to multi rabbit hosts.
2. Setting up a loadbalancer in front of RabbitMQ cluster,
provide a unique address in $rabbit_host
In current, rabbit_ha_queues option is controled by rabbit_hosts
if conditional statement. When users try the second method:
changing rabbit_ha_queues to true. If they don't set rabbit_hosts,
then current logic will not work.
This patch is aim to add an rabbit_ha_queues option, set it to undef
by default for forward compatbility.
Change-Id: I9f61c113b41cb00f7f95e80e2cabe1641aed74e7
Close-Bug: #1485287
Qpid messaging driver is removed from Oslo.messaging [1]
Therefore, we cannot support it anymore.
[1] I4a9cba314c4a2f24307504fa7b5427424268b114
Change-Id: I5a702aacf77956a6c616fd98d2f942654548f00d
Kilo oslo.messaging added heartbeating support for RabbitMQ
connections. This patch adds support for this in Puppet modules
by managing the oslo_messaging_rabbit/heartbeat_timeout_threshold
and oslo_messaging_rabbit/heartbeat_rate settings.
Closes-bug: 1467667
Change-Id: I3aef101e3a099bcbd96ee32efa7c5f849e6000cf
This reverts commit d302170d26.
We can unrevert this change once we are ready for kilo specific
changes.
Change-Id: I3079727c8333de3e9b4382a68fca3ef293ce2d48
This reverts commit e6e8f6a562.
Kilo deprecates these settings, but they still work. We should wait to
merge this until upstream distro packages are ready so that master is
not broken.
Change-Id: Ib05943e89969eb810527943426c566cf4a77e7ad
Kilo oslo-messaging deprecates rabbit/kombu settings in the
DEFAULT section.
Move these settings to proper oslo_messaging_rabbit section.
Change-Id: Ica8cd70ece41f55b827f74d3f14cbc35f37ae13d
It makes possible to control the value of notification_driver setting and defaults
to 'messaging' to maintain backwards compatibility.
Change-Id: I3f2c29adbfb605ef288962f72ba81c11811cb357
Add puppet parameters lint (with puppet-lint-param-docs gem) and fix
missing documentations, this commit also fix metadata.json file (SPDX
license, and open dependencies).
Change-Id: I0d590b930a8d0263c3a74d861b9786770be7d183
The kombu_ssl_* parameters should not be required when rabbit_use_ssl => true
Rather, rabbit_use_ssl must be set to true if the kombu_ssl_* parameters are
used.
Change-Id: I1b2cbb15a7778c3d072409c43b39d1f41b7b48b6
Closes-Bug: 1356083
Rabbitmq won't talk to us anymore if we try to use SSLv3 as it disabled
support for SSLv3. Openstack components use python's openssl
implementation which does not support TLSv1.1 and TLSv1.2 yet so we
just switch to TLSv1. Support for newer TLS should come with python
2.7.9+
Closes-Bug: #1409667
Change-Id: I6dd2dcf7d047d8cee028c3f890221194b0179b8a
Currently secrets like rabbit_password or admin_password are displayed in
puppet logs when changed. This commit changes glance_*_config and
glance_*_ini types adding a new parameter that triggers obfuscation of
the values in puppet logs.
Change-Id: I31f974a9afadef42939ee092ecba3b8f4333bb8b
Closes-Bug: #1328448
This commit causes the run to fail is rabbit_use_ssl parameter is set
to true but the ssl related parameters remains undef.
Change-Id: I12a8a87dde45a06d35c6d3e90ef2637085fdba86
* Use new oslo.messaging conf options for rabbit_hosts and
rabbit_ha_queues for glance::notify::rabbitmq class
* Warn on deprecated rabbit_durable_queues and use amqp_* instead
* Fix/add rspecs
* Fix a mess with wrong notification_driver usage
* Update README with usage example
DocImpact
Closes-bug: #1259193
Closes-bug: #1312054
Closes-bug: #1312658
Closes-bug: #1313553
Change-Id: I16b8e71db20602986a7afe8d24e7faba91a0997f
Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
This adds the following parameters:
* kombu_ssl_ca_certs
* kombu_ssl_certfile
* kombu_ssl_keyfile
* kombu_ssl_version
these are necessary to establish a secure ssl
connection to rabbitmq.
Change-Id: Ia9ea7cf44664f71a4fb5cc76e3474aa54a9bb30d
The configuration option 'notifier_strategy' has been deprecated
in favor of 'notification_driver'.
Change-Id: Ia51aa6772df8736c57f0fb2223b6a680e3dfb11d
This patch replaces `qpid_host` with `qpid_hostname` in both the
qpid manifest and the spec file class. `qpid_host` has been shipped
as the parameter to specify qpid's hostname, although the correct one is
`qpid_hostname`.
Closes-bug 1242715
Change-Id: I92b8da5a204180316f8117634a45154023551abd
This patch is aim to update rabbitmq options in notify::rabbitmq
class to keep consistent with glance-api.conf. And fix description
error in comment.
Fixes bug #1221008
Change-Id: I441a61bb683552e1696f779c733db561cca03b64
- Add native types to manage all existing ini files
- remove all unused templates
- convert all concat with ini_setting resources
- remove all concat code
This commit splits the api.conf template into
fragments to better allow for logical separation
for configuration sections.
The main motivation for this change is to allow
differrent implementations of services in glance to
be split up into seperate configuration interfaces.
The primary examples of this are the notifier and
the storage backend. Each of these services have
multiple potential implementations. This allows
those implementations to be implemented as separate
class interfaces and saves us from having to have
all of the possible config parameters to be specified
as parameters of the api class.
It creates a define: glance::api::config that can
used to configure file fragments for
/etc/glance/glance-api.conf
It also creates configuration interfaces for
configuring the following config sections of api:
backend::swift, backend::file, notify::qpid,
notify::rabbitmq.
Takashi Kajinami