- Replace git.openstack.org with opendev.org
- Update some documentation
- Move README.md to README.rst for better rendering
- Drop obsolete bootstrap.sh script
Change-Id: I21ccc2b022c9123e6449dd8d8639e0405b848711
- deprecated Gemfile
- updated TESTING and README
- updated Rakefile to use chef exec instead of bundle exec
- replaced Runner by SoloRunner in specs
Change-Id: I5300850921f0af06ba65d3a0f7cf681f609e5868
* Consistent email across cookbooks
* Add Contributor.md to help out new folks
* Fix broken link in Testing.md
* Readme tweaks
Change-Id: Ifb0019ec4d1c6427b23f41f59fa3e5cf835fa105
Partial-Bug: #1342735
In current logic, rabbitmq port will be set to ssl-listening port,
this will make rabbitmq fail to start.
This submit will configure rabbitmq port for both ssl and non-ssl cases.
Closes-Bug: #1353884
Change-Id: I37dc9b656c553554b9bc636fe35c69744debe92a
The problem that this change addresses is that the address_for method
will not work correctly if there are multiple IP address associated
with the specified interface.
The approach to solving this problem and moving towards the overall
goal of having one place where service networking information is
stored is to convert address_for calls into endpoints, and add a
address() method to the endpoints interface for IP address resolution.
The address() method has the following behavior: if the
bind_interface of an endpoint is set, then the IP is looked up on
the interface. Otherwise, the IP specified in the host attribute is
returned. This allows the caller to choose either method of
determining what IP a service will be bound to.
This initial change switches both the openstack-ops-database and
openstack-ops-messaging cookbooks over to use endpoints instead of
address_for. The other cookbooks will be switched over time.
blueprint increase-ip-binding-flexibility
Change-Id: I4a610409b9542a4c802f94b557299bb97dd0781b
Removing tailor, cleaning up metadata and Gemfile and adding TESTING.md
Addresses: blueprint rubocop-for-ops-messaging
Change-Id: I4734194aa52973dbaeb299e5970802a38b326dc5
When develop_mode=false, the password of mq user "guest"
in the databag user_passwords is required. But the current
code doesn't support. I made it work, and add the test cases.
Closes-Bug: #1257554
Change-Id: I0d01bd73eaec9cc90304e67484fec15fad061504
Since this breaks people using rabbit in the standard way, I
rather revert this change, and fork my own ops-messaging cookbook
since this is intended as an example cookbook (granted others
may use it directly). This code would be better off in my
own fork, where i do not impact others, with a non-merged upstream
rabbitmq feature.
This reverts commit 3b35ac204d.
Change-Id: I53da70583c50ae985d3842c3d709eb81f565d63d
This change integrates against a rabbitmq cookbook feature which
is not yet merged upstream. However, given the default code path
does not change, felt okay to get this out there. Especially b/c
we are dependant on it. This feature allows one to run rabbit
and clustering across a specific address. For more details, see:
http://tickets.opscode.com/browse/COOK-3320
Change-Id: I2a10c551cb2176dadaee8842eeadfdfc8cb93e44
These attributes are specified in openstack-common.
Don't see why we should document them inside the wrapper,
should only document attributes the wrapper is setting
Change-Id: Ic4be7505348e0a2d52442f64bcf388f2244e11e6
Clustering is set to false by default. When enabled, will setup
rabbitmq disk node clustering. Also, added opscode to attribution,
somehow had removed them in the previous rebase.
Change-Id: Idd249d0d950f5f4eb44cd7c10566ece254ed7f45
We had two reviews which added an ops-messaging cookbook. Updating
this cookbook with patterns we estabished from the database cookbook.
Craig already did most of the work, however, updated the tests to
use the chefspec find_provider, added clustering support, and attempted
to follow the service_type attribute patterns used in database cookbook.
Since these cookbooks are not complete, added a larger commit than
would have.
Change-Id: I0edfc996df413c6e41a31d53f964d7f5fc9e0aeb
This initial commit provides support for an openstack-ops-messaging
cookbook. In this initial release, we provide the capability to install
and configure RabbitMQ. This cookbook is modeled after the
openstack-ops-database cookbook in the way in which it can be utilized.
Included are tests for all recipes and this release supports Ubuntu
only.
Change-Id: I4d799fa46e67e0f2eca2ac8b205f51c07e0df01e
Lance Albertson