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.
Update glance to Juno

Some conf entries are deprecated in favor of new ones.

sync paste and policy from upstream.
  Disable osprofiler by default.
Upgrade cinder to juno

Had to add a whole new keystoneauth section for new options.

api-paste updates
  sync with upstream
  clean up keystone middleware for correct options

refresh policy.json from upstream
Upgrade nova to juno

Required a glance and neutron section for associated configs.
Required a keystone_authtoken for renamed settings.
Removed image_service, has been gone since 2012
Update api-paste to match upstream
  v3 and v21 paths.
  request ID logging
  Updated keystone authtoken argument for identity_uri
  (http://www.jamielennox.net/blog/2014/05/21/identity-uri-in-auth-token-middleware/)
Neutron juno upgrade

Updated keystone options.

update api-paste from upstream
  Also use keystone middleware identity_uri

refresh policy from upstream

Update nova notification details with the right tenant
Upgrade percona to 5.6

A neutron migration will crash 5.5
sst method upgraded to v2. Previous version does not work.