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: I3cb98dd54675d9ff2bff340425378b34b021d9da
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-database
Change-Id: Ia2e02864b3c157b44cf0cf483801c6bb19f83054
Merge "Filling out initial rubocop support for metadata.rb and the Gemfile."
Add supoort for heat

Pending on review: https://review.openstack.org/#/c/59292/
1) Add dependency for openstack orchestration cookbook
2) Create heat database
3) Add testcase for heat database creation
Implements: blueprint heat-support

Change-Id: I99caa16f62945b8063f142d3897db8509248a0e8
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: I8e1e25e73eb01cbea30435fe7c6c53cab7a15c04
Partial-Bug: #1195915
Update attributes to be rubocop compliant

- Update rubocop config to handle entire repo in one file
- Update Strainerfile to run rubocop only once
- Update attributes to comply with rubocop

Change-Id: I299c2775a5a124b0af74f2e3d844cbd91f93380f
Addresses: blueprint rubocop-for-ops-database
Fix bug on get_password for "heat"

- Add appropriate variables for "get_password" call for heat db.
- Fix stub in spec test to catch this in future.

Change-Id: Ic653dde525bbe7c56e8cf1a6694a06885a1e3c88
Remove Berksfile.lock from dev branches

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

Change-Id: I16763286632d468f3dbea28750b9ecfee75533cf
Merge "Remove Berksfile.lock from dev branches"
Merge "Update attributes to be rubocop compliant"
Update spec files to be rubocop compliant

- Update .rubocop.yml to include spec/**
- Update metadata.rb to be rubocop compliant
- Update spec files to be rubocop compliant

Change-Id: If059f01f46102282ffeed9323f6e06fa78f8597c
Addresses: blueprint rubocop-for-ops-database
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: I5f324ed2494a643d27bb2922361e21f4a1ce2a1f
Implements: blueprint clean-up-attr-for-mq-and-db
Update recipes to be rubocop compliant

- Update .rubocop.yml to include recipes/**
- Update recipes to be rubocop compliant

Change-Id: Ibb2113e266427b1d9b509d1e66389462e1ff0189
Addresses: blueprint rubocop-for-ops-database
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: I08e8822a7ad7a5330881c14ffb07db3842bd5d9c
Implements: blueprint lint-and-unit-testing-for-havana
Fix issue with mysql not restarting on new bind_ip

Addresses: bug #1277041

By default mysql binds to 127.0.0.1. Setting the bind_ip attribute to
something else, as we do in the ops-database cookbook before calling the
mysql::server recipe, causes the my.cnf to be populated with the correct IP.

However, because of this bug in the upstream mysql cookbook:
https://tickets.opscode.com/browse/COOK-4161
mysql does not get restarted (it only gets reloaded)
and so the new bind_ip does not take effect.

This commit adds a workaround until the upstream bug is fixed. The
workaround directly modifies the template resource from the resource
collection to add a 'restart mysql' notification.

Change-Id: I4f59e9f7fecb5040532948d0bb07d49385280a48
Fix issue with mysql not restarting on new bind_ip - RHEL/CENTOS

Addresses: bug #1277041
Implements: blueprint centos-rhel-for-ops-database

By default mysql binds to 127.0.0.1. Setting the bind_ip attribute to
something else, as we do in the ops-database cookbook before calling the
mysql::server recipe, causes the my.cnf to be populated with the correct IP.

However, because of this bug in the upstream mysql cookbook:
https://tickets.opscode.com/browse/COOK-4161
mysql does not get restarted (it only gets reloaded)
and so the new bind_ip does not take effect.

This commit adds a workaround until the upstream bug is fixed. The
workaround directly modifies the template resource from the resource
collection to add a 'restart mysql' notification.

** This particular patchset builds on the last by adding support for
rhel/centos which use a different name for the my.cnf template resource **

Change-Id: I357bf1458a1781189922032cdc8da8ad9e0a03a7
change test to use SLES platform instead of openSUSE

Change-Id: I71a6628c2c84dcd09d073528381eb295ecc33f7d
Cleaning up berks/metadata dependencies

Change-Id: I5a24fbbe8c5bb33646fcffd83971ce4fe982a14c
Merge "change test to use SLES platform instead of openSUSE"
Add ChefSpec::Coverate to spec_helper.rb

Change-Id: I96db2b0c255c044598bd55b39e7003a7125803ef
Addresses: blueprint lint-and-unit-testing-for-havana