Adds hacking check for debug logging translations

bp more-code-style-automation

Change-Id: Id54f322f00b04a165bb4a7b1e24f95bb72b7f068
Do not use keystone's config for nova's port

Keystone's configuration should have no bearing on the catalog
for nova's port. Nova's port is "static" data from the templated
catalog perspective.

The 'compute_port' option has been marked as deprecated and
slated for removal in the L release. The default/sample
templated catalog files do not rely on this option any
longer.

Change-Id: I51b0ec951449360f002c2e7c900ded0f40e16044
Closes-Bug: #1335278
Make OS-FEDERATION core.Driver methods abstract

Not all methods in contrib.federation.core.Driver are decorated
with @abs.abstractmethod. This patch adds missing decorators.

Change-Id: I93962110134d4b9062a75c228760333403a4f7eb
HEAD responses should return same status as GET

According to the HTTP spec, a HEAD request should return the same
status and headers as the GET request (including content-type and
content-length). The HEAD request simply strips out the body and
returns no body. Any case where HEAD routing returned a different
status code than GET, now returns the same status and headers.

Any case where HEAD was supported where GET was not supported now
supports both GET and HEAD.

The wsgi.render_response code now handles HEAD appropriately and
will maintain headers while enforcing no body data is returned.

The bulk of this change is to support the same behavior between
deploying Keystone under eventlet and under HTTPD + mod_wsgi. In
the case of deploying under HTTPD + mod_wsgi, there are cases
where mod_wsgi will turn a HEAD request into a GET request to
ensure that the proper response is rendered. With these changes
all HEAD responses will respond in the same manner under either
eventlet or mod_wsgi.

Change-Id: I13ce159cbe9739d4bf5d321fc4bd069245f32734
Closes-Bug: #1334368
Correct the region table to be InnoDB and UTF8

The region table was not specified as being InnoDB or UTF8 under
mysql initially. The migration will fail if the defaults for MySQL
are not set correctly. A new method has been added to the
migration_helpers module to detect and correct the InnoDB / UTF8
specific issue with the region table.

Change-Id: I374c3dd46a4292e8f9e74ef75a8bb463b951f135
Closes-Bug: #1334779
Add _BaseFederationExtension class

_BaseFederationExtension class with general use methods should be added
so inheriting classes don't need to reimplement such methods

Change-Id: Ic2d8e8e96b8b16d60071f8a7fb9eeeb3d688dcb8
Merge "Correct the region table to be InnoDB and UTF8"
Merge "Make OS-FEDERATION core.Driver methods abstract"
Merge "HEAD responses should return same status as GET"
Add keystonemiddleware to requirements

Keystone middleware has been split. Keystone ec2_token middleware
has been included in the new repository. Keystone will depend on
the keystonemiddleware package and import ec2_token instead of
providing duplicated code.

Change-Id: I10534c1ca9883b9f98c998a6cb61e500f6c6ff2d
bp: split-middleware
Imported Translations from Transifex

Change-Id: Ia8bfc8f572d6f91ab39322e1a8274c5d2a12815b
Remove deprecated token_api.list_tokens

The method token_api.list_tokens was deprecated in Icehouse and
slated for removal in Juno. It was determined that the driver
version of .list_tokens was an internal method and should not
be used outside of the .delete_tokens method.

blueprint: non-persistent-tokens
Change-Id: I33e81503b1469537bbd745937bf2efe17c7ae469
Do not use lazy translation for keystone-manage

lazy translation provides the ability to translate messages to
different languages based on the request language in the HTTP
request. Since keystone-manage doesn't handle HTTP requests it
doesn't need to enable lazy translations.

Change-Id: I0abab2565b604e3325f61cad412dc8b28f768f18
Add oslo.i18n as dependency

oslo.i18n provides the i18n functions that were provided by
oslo-incubator's gettextutils module. Once Keystone is changed to
use oslo.i18n the gettextutils module can be removed.

Change-Id: Ie9db1c25ba0601258fb9a493cbc75b0ff205d0d6
multi-backend support for identity

The current code has a number of problems and limitations in its
support for having domain-specific backends (e.g. a different LDAP
server per domain).  Not least of the problems is that you cannot
always infer the domain if an API call is just handed a user_id or
group_id. These issues are so severe that this feature is currently
marked as experimental.

This patch fixes these issues by using a mapping layer to store
the domain and local ID for the public facing user and group IDs.
No API changes are required for this new support. An important
consequence of this change is that non-UUID IDs for backends
like LDAP do not escape from keystone.

To ensure backward compatibility with existing single backend
installations, the mapping is not used for the default driver.
An exception to this is that if a cloud provider wants to enable
mapping for the default LDAP driver then they can set a config
option to achieve this.

keystone-manage has been extended to provide options to purge
the mapping table.

Blueprint: multi-backend-uuids

Change-Id: I60f8965bb74b248e6a6c8f141289affa431ee3cf
Merge "Remove deprecated token_api.list_tokens"
Merge "Add oslo.i18n as dependency"
Merge "Imported Translations from Transifex"
Merge "multi-backend support for identity"
Merge "Adds hacking check for debug logging translations"