enforcing single proposal for rabbitmq
Merge pull request #4 from arkadykanevsky/pull-req-release-pebbles-master-79c57cd7d40ba8de015310df1f8f9e8b30a9b020

enforcing single proposal for all openstack barclamps [2/9]
Merge pull request #5 from MirantisDellCrowbar/release/pebbles/master

https://github.com/crowbar/barclamp-rabbitmq/pull/5

Merged by devtool for cloudsleuth
ensure that the rabbitmq-server role is assigned in rabbitmq proposals

In the future we will hopefully support HA rabbitmq, where there could
be multiple servers.

Currently there's only one possible validation error, but we follow
the pattern used by other barclamps for building an errors array and
joining it, to allow easy addition of other errors in the future.
Fix CHEF-3694 caused by bad resource naming

Two resources have the same name, which leads to:

WARN: Cloning resource attributes for rabbitmq_user[nova] from prior resource (CHEF-3694)
WARN: Previous rabbitmq_user[nova]: /var/chef/cache/cookbooks/rabbitmq/recipes/rabbit.rb:31:in `from_file'
WARN: Current  rabbitmq_user[nova]: /var/chef/cache/cookbooks/rabbitmq/recipes/rabbit.rb:38:in `from_file'
Use correct path for rabbitmq-plugins by using Config::CONFIG["libdir"]

This will make it work on more distributions (since the path might be a
bit different, depending on the distribution: /usr/lib vs /usr/lib64,
for instance).
Merge pull request #9 from vuntz/fix-CHEF-3694

Fix CHEF-3694 caused by bad resource naming
Replace github.com/dellcloudedge mentions with github.com/crowbar
Merge pull request #10 from vuntz/replace-dellcloudedge

Replace github.com/dellcloudedge mentions with github.com/crowbar
Merge pull request #7 from aspiers/server-role-validation

ensure that the rabbitmq-server role is assigned in rabbitmq proposals
Merge pull request #8 from vuntz/rabbitmq-plugins-path

Use correct path for rabbitmq-plugins on SUSE
Use RbConfig::CONFIG instead of Config::CONFIG

The latter just doesn't work.
Merge pull request #11 from vuntz/fix-libdir

Use RbConfig::CONFIG instead of Config::CONFIG
Update rabbitmq password if it's different

This works by checking we can connect with current credentials, using
the API offered by the management plugin.
Enable management plugin on SUSE

We simply need to install the rabbitmq-server-plugins to get the plugin.
Put mochiweb port in non-configurable attribute

This is better than having it hard-coded in several places.
Correctly set default port attribute in cookbook
Correctly log only when an action is done
Rework how we automatically set a password

Do it in the same way as for database passwords.
Merge pull request #12 from vuntz/fix-new-password

Fix re-creating rabbitmq proposal