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.
ansible-lint: upstream fix for egg_info bug
Merge pull request #638 from blueboxgroup/ansiblelint-egg_info

ansible-lint: upstream fix for egg_info bug
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 an upgrade playbook for upgrading to juno

Upgrade from havana to juno, following
http://docs.openstack.org/openstack-ops/content/upgrades_havana-icehouse-ubuntu.html
mostly.

Our databases are already UTF-8 so that step is skipped.

Roles are applied to get new software in place, without a restart of the
services, and then services are managed in order to do database
migrations.  Some attempt is made to minimize the complete downtime of
any one service.

A new stop-services role is introduced in order to be able to interleave
it with the other roles.
Add test/run ability to run upgrade.yml
Update python-novaclient and python-neutronclient to meet neutron icehouse requirements
update glance, horizon, keystone, neutron and nova to stable/icehouse
Hide external networks from launch instance workflow
Hide Neutron LBaaS in Horizon
Upgrade Neutron to icehouse
neutron nova notifications
Neutron: nova notification config
Run update-ca-certificates during SSL task in common
Update keystone to juno

Adds public_workers and admin_workers options

Refresh keystone-paste.ini and policy.json from upstream
Enable forced database migrations

Existing check will just read back what's in the database as reported by
the manage utility, which just reads the database, so I'm a bit confused
as to what it was trying to accomplish. Either way this change
introduces a way to force a migration.