Integrate monitiring into associated roles

Monitoring was a stand alone playbook, that was almost like a role, but
not quite. This change moves all the monitoring tasks directly into the
associated roles for those tasks.

All the tasks have been tagged with "monitoring" and "common" which can
allow for doing a monitoring only run.

All roles that have monitoring need to depend on the monitoring-common
role, to pick up the common handler. Since there is no true common role
that everything depends on this will have to do.

nimble was put into the cinder control role, but that can easily be
moved elsewhere if desired.
Merge pull request #618 from blueboxgroup/monitoring-by-role

Integrate monitoring into associated roles
bbg-repo: add the bbg openstack repo
Merge pull request #645 from blueboxgroup/bbg-repo

bbg-repo: add the bbg openstack repo
Use yaml syntax instead of key=value for keypair

The key value is multiline and needs to be done with yaml syntax,
otherwise it'll get double white spaces.

See https://github.com/ansible/ansible-modules-core/issues/33
Merge pull request #646 from blueboxgroup/fix-keypair

Use yaml syntax instead of key=value for keypair
Add a rally role

This will be used to benchmark our stack. This role installs rally in a
venv and adds a deployment for it, as well as a benchmark set. Rally is
set to log directly to /var/log/rally.log and the data is kept in a
local sqlite database. For now the rally REST service is not enabled.

To get rally going, add a rally group in hosts and add a host to the
group. Test clusters will get rally by default.