make AMQP support when develop_mode=false

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
Merge "make AMQP support when develop_mode=false"
Update spec_helper to include 'chefspec/berkshelf'

This minor change allows you to run rspec outside of strainer while
still having cookbook dependencies automatically handled by berkshelf
(which also means you can run individual chefspec tests).

Note that this change does marginally increase the time it takes to run
a strainer test.

A similar change was recently accepted in the openstack-compute
cookbook.

Change-Id: I4ac5ec08dc3a09dd3b434203f83ef5e54d964505
Filling out initial rubocop support for metadata.rb and the Gemfile.

Removing tailor, cleaning up metadata and Gemfile and adding TESTING.md

Addresses: blueprint rubocop-for-ops-messaging
Change-Id: I4734194aa52973dbaeb299e5970802a38b326dc5
Move to use "get_password" instead of "{user,service,db}_password"

The user_password, service_password and db_password functions are redundant
since they simply call "secret". Creates a get_password function that will
accept a "type" of db, service or user.

All instances of these calls have been changed to call get_password

Change-Id: Ic73c99034638ec092192d11e37671edbba0e48ef
Partial-Bug: #1195915
Merge "Move to use "get_password" instead of "{user,service,db}_password""
Update recipes to be rubocop compliant

- Add rubocop.yml in recipes/
- Add recipes rubocop tests in Strainerfile
- Update recipes to comply with rubocop

Change-Id: I258b2ed24a6b2f1221ec8b5e188bd4567bc63f99
Addresses: blueprint rubocop-for-ops-messaging
Update spec to be rubocop compliant

- Add rubocop.yml in spec/
- Add spec rubocop tests in Strainerfile
- Update spec files to comply with rubocop

Change-Id: Ia1aabed7ab1ed21913e4783eec711c09777c9754
Addresses: blueprint rubocop-for-ops-messaging
Merge "Update spec to be rubocop compliant"
Single .rubocop.yml file for all Ruby files, attributes cleanup.

Also changed email & company name.

Addresses: blueprint rubocop-for-ops-messaging
Change-Id: I1bb991184f813bc574e1c6a4f5de3030b82c0b49
Remove Berksfile.lock from dev branches

blueprint remove-berksfile-lock-from-dev-branches

Change-Id: I730a7b8876a9610236f8afc5ef544abf2972dea2
Clean up cookbook for bp/clean-up-attr-for-mq-and-db

This change removes the attributes we'll be moving to openstack-common
and changes reference of those attributes to reflect new (more
consistent) namespace.

Change-Id: I1602d2e6241a62b188d64fa760786fb95a734404
Implements: blueprint clean-up-attr-for-mq-and-db
Upgrade/Update rubocop

Now that almost all of the rubocop blueprints have been completed, make
one final pass through all of the cookbooks ensuring they're all in
sync with each other.

- Upgrade rubocop to 0.18.1
- Fix violations caused by 0.18.1 upgrade
- Move Excludes for non-existent folders to Includes so they
  automatically cover future additions

Change-Id: I9473903e19f075cff520a2fa7602ad779e7f13db
Implements: blueprint lint-and-unit-testing-for-havana
Adding ChefSpec::Coverage to spec_helper.rb

Change-Id: Ia40b7be0c24afd4220550e043833304a25e88e93
Addresses: blueprint lint-and-unit-testing-for-havana
Disable the NumericLiterals cop for rubocop

- Disable the NumericLiterals cop in the .rubocop.yml file - this cop enforces
  an underscore '_' every 3 characters of an integer. This doesn't make much
  sense in our use case and reduces readability. Especially for port numbers.

Change-Id: I4e7f7c03efc501857afb4c5ecd7af1bba107a8c7
Addresses: blueprint rubocop-integer
Install rabbitmq-server from rabbit site for CentOS/RHEL

Fixes: bug 1282041
Implements: blueprint centos-rhel-for-ops-messaging

On CentOS/RHEL, the OS base repos don't have a package for
rabbitmq-server.  The rabbitmq cookbook by default expects to be able to
install the latest rabbitmq-server rpm from the rabbitmq site
(use_distro_version = false).  However, in our cookbooks we are overriding
'use_distro_version' to true, which works for ubuntu as it has a
rabbitmq-server package in it's base repo

This commit basically leaves the use_distro_version flag as false unless
ubuntu/suse is the platform_family, so that CentOS/RHEL can grab the rpm
from the rabbitmq site

Change-Id: I4e31cbb4957f0e696a1528fa3f7c6c80695989ac
Refactoring chefspec tests

Change-Id: Ifb11af44da87fec7a8d0018a7db36bbd8b1989de
Addresses: blueprint refactor-spec-files
Adding tests for untouched resources

Change-Id: I0aae1d2336f96d35e64191da2dcb5c58ab47896b
Addresses: blueprint lint-and-unit-testing-for-havana
update gitignore

Change-Id: I1afceae710c0f6d6719b6b124f671ef44fb7ed18
Merge "update gitignore"