The configuration is done via the oslo::messaging::rabbit resource
from puppet-oslo. We should be checking for the resource that we're
using instead of the underlying configuration file.
Change-Id: Ic078c7f036ce93fc91bd496884e4423b9653b1c8
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
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
This change updates the glance tests to use rspec-puppet-facts to test
multiple operating systems.
Change-Id: I75fd8970ba8335cb4ffa09a7d600415056e9f889
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
This change adds possibility to use the os_service_default
fact for configuration options that default to '<SERVICE DEFAULT>'.
this change is done by analogy with cinder
commit 667e6c0850672dbbf99381eb92468f95e5591913
Change-Id: Ie5c8909bcc1c9a6a7a9ab1b59eec4637751ffd74
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 d302170d260f4e6585fedc1b4709c953d0491c56.
We can unrevert this change once we are ready for kilo specific
changes.
Change-Id: I3079727c8333de3e9b4382a68fca3ef293ce2d48
This reverts commit e6e8f6a56231409028ff1e7cdcd44781ca37d5b0.
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
This patch aim to update our specs test in order to work with the rspec-puppet release
2.0.0, in the mean time, we update rspec syntax in order to be prepared
for rspec 3.x move.
In details:
* Use shared_examples "a Puppet::Error" for puppet::error tests
* Convert 'should' keyword to 'is_expected.to' (prepare rspec 3.x)
* Fix spec tests for rspec-puppet 2.0.0
* Upgrade and pin rspec-puppet from 1.0.1 to 2.0.0
* Clean Gemfile (remove over-specificication of runtime deps of puppetlabs_spec_helper)
Change-Id: Ibd0333dc3c0959e846edfbad51fb48e8dfb8fbe9
Card: https://trello.com/c/eHXc1Ryd/4-investigate-the-necessary-change-to-be-rspec-puppet-2-0-0-compliant
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 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
using RI's version of the concat module.
It introduces a custom fact concat_basedir that can determine
where the vardir is for a particular agent.
This commits adds that fact to unit tests that are validating
the resuling fragment files.
I had previously checked in some broken tests that
resulted from the updating the concat fragments names
to ensure uniqueness between services (eg, choosing
fragment names like HEADER were causing
duplicate resource errors, these have been prefixed
with the service name glance-api to ensure uniqueness)
This commit updates the tests so that they work for
this previous commit (oops!)
This commit resolves failing tests from
glance::api and glance::registry related to recent
refactors.
It also adds tests for all of the new api fragment
classes/defines.