W/o this change we cannot drop a RabbitMQ service (cluster)
installation and configuration from Cinder module.
We want Cinder module to has an option to configure only users,
rights, vhosts but not the AMQP cluster itself (this part
should be moved to some other modules).
The solution is:
* add a False value for the rabbitmq_class parameter and skip
all of the related configuration steps, if the False value
was specified.
* Deprecate rabbitmq_class parameter.
Reviewed: https:/ /review. openstack. org/147420 /git.openstack. org/cgit/ stackforge/ puppet- cinder/ commit/ ?id=583e7c39c42 f5d28bcc2e9eb94 120917d248d40d
Committed: https:/
Submitter: Jenkins
Branch: master
commit 583e7c39c42f5d2 8bcc2e9eb941209 17d248d40d
Author: Bogdan Dobrelya <email address hidden>
Date: Thu Jan 15 09:33:54 2015 +0100
Add an option to not configure RabbitMQ service.
W/o this change we cannot drop a RabbitMQ service (cluster)
installation and configuration from Cinder module.
We want Cinder module to has an option to configure only users,
rights, vhosts but not the AMQP cluster itself (this part
should be moved to some other modules).
The solution is:
* add a False value for the rabbitmq_class parameter and skip
all of the related configuration steps, if the False value
was specified.
* Deprecate rabbitmq_class parameter.
Closes-bug: #1407077
Change-Id: Ie13123f01fc4a2 079dd7ef6622675 b7e8c7f417e
Signed-off-by: Bogdan Dobrelya <email address hidden>