Depends-On: https://review.opendev.org/756168 Change-Id: I37569390af252c1270d7e98aa03c062519a46992 Signed-off-by: Lance Albertson <firstname.lastname@example.org>
|3 months ago|
|.delivery||10 months ago|
|attributes||3 months ago|
|recipes||3 months ago|
|spec||3 months ago|
|.gitignore||5 years ago|
|.gitreview||1 year ago|
|.zuul.yaml||2 years ago|
|Berksfile||1 year ago|
|CONTRIBUTING.md||6 years ago|
|LICENSE||3 years ago|
|README.rst||5 months ago|
|Rakefile||1 year ago|
|TESTING.md||5 years ago|
|metadata.rb||5 months ago|
This cookbook provides shared message queue configuration for the OpenStack deployment provided by Chef for OpenStack. The OpenStack chef-repo contains documentation for using this cookbook in the context of a full OpenStack deployment. It currently supports RabbitMQ and will soon other queues.
The following cookbooks are dependencies:
The usage of this cookbook is optional, you may choose to set up your own messaging service without using this cookbook. If you choose to do so, you will need to provide all of the attributes listed under the Attributes.
openstack["mq"]["cluster"]- whether or not to cluster rabbit, defaults to
The following attributes are defined in
attributes/messaging.rb of the common cookbook, but are documented here due to their relevance:
openstack["endpoints"]["mq"]["host"]- The IP address to bind the rabbit service to
openstack["endpoints"]["mq"]["port"]- The port to bind the rabbit service to
openstack["endpoints"]["mq"]["bind_interface"]- The interface name to bind the rabbit service to
openstack["mq"]["rabbitmq"]["use_ssl"]- Enables/disables SSL for RabbitMQ, the default is false.
If the value of the
bind_interface attribute is non-nil, then the rabbit service will be bound to the first IP address on that interface. If the value of the
bind_interface attribute is nil, then the rabbit service will be bound to the IP address specified in the host attribute.
Please refer to the TESTING.md for instructions for testing the cookbook.
Berks will resolve version requirements and dependencies on first run and store these in
Berksfile.lock. If new cookbooks become available you can run
berks update to update the references in
Berksfile.lock will be included in stable branches to provide a known good set of dependencies.
Berksfile.lock will not be included in development branches to encourage development against the latest cookbooks.
|Author||John Dewey (email@example.com)|
|Author||Matt Ray (firstname.lastname@example.org)|
|Author||Craig Tracey (email@example.com)|
|Author||Ionut Artarisi (firstname.lastname@example.org)|
|Author||JieHua Jin (email@example.com)|
|Author||Mark Vanderwiel (firstname.lastname@example.org)|
|Author||Jan Klare (email@example.com)|
|Author||Lance Albertson (firstname.lastname@example.org)|
|Copyright||Copyright (c) 2013, Opscode, Inc.|
|Copyright||Copyright (c) 2013, Craig Tracey|
|Copyright||Copyright (c) 2013, AT&T Services, Inc.|
|Copyright||Copyright (c) 2013, SUSE Linux GmbH.|
|Copyright||Copyright (c) 2013-2014, IBM Corp.|
|Copyright||Copyright (c) 2019-2020, Oregon State University|
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.