Remove how to contribute section in favor of CONTRIBUTING.rst

Change-Id: I5364d9d930ca0871bd839917b23ef3199eff3340
Adds tests for XML version response

Adds tests for the version response when use
 Accept: application/xml

To share code, moved assertEqualXML from test_serializer
to keystone.test.

Change-Id: I92e28a9167d0c77fc7efbd1eda2893ec1128354f
LDAP get_project_users should not return password

Also with this fix no need to skip get_project_users for LDAP.

Fixes bug1190286

Change-Id: I6ab6b4179c36d49b8a2eab1ea67ce0d6339751f5
Remove a stat warning log

If using load balancer before keystone and the port numbers was
different between load balancer and keystone, too many stat warning logs
could be found in logs. The root cause is the keystone servers' stat
logic getting the request host information which point to load balancer
ip address and port rather than the ips and ports of themselves.

Fixes bug #1189118
Change-Id: Ic837af77bc2509086c0e37194ba70b683f693ae5
Correct the resolving api logic in stat middleware

If the admin_port string is a substring of public_port string, all the
requests would be stated as 'admin' either their real dest port is
admin_port or public_port. It's due to the incorrect logic in stat
middleware.
For example, if public_port = 35000, admin_port = 5000, the first
judgement branch: "if str(CONF.admin_port) in host" in
StatsMiddleware::_resolve_api() would always return "True" either the
host port number equal to 5000 or 35000, so that the following judgement
branches would be incorrectly ignored.

Fixes bug #1189121
Change-Id: I1086b7d11f83dd218d66376f79747a1f720eb807
Http 400 when project enabled is not a boolean

Having enabled="true" in json data when updating tenant will produce 500

When updating a project, no type check was performed on the enabled
attribute. Therefore, if enabled value in JSON/XML is not a boolean but
a string, keystone responds with an incorrect Http 500 error code and
the stacktrace.

The change introduces a type validation of the enabled attribute at
identity manager. If the type is not a boolean, keystone now returns an
appropriate Http 400 error code with a message pointing a bad format for
the attribute.

Test cases have been added to file test_backend and test_content_types
for testing the case when enabled attribute is a string or int when
updating project.

Fixes bug #1191384

Change-Id: I86dd7e71d4bac1e3fd6fcabaa1a2136a47722e5f
Move user fileds type check to identity.Manager

The fileds type's checking logic during creating and updating
users apply to all driver calls. It should be centralized in the
identity.Manager rather that continuing the trend of spreading them out
between controllers, managers and drivers.

This patch move the enable type checking logic to identity.Manager and
modify the related test cases in test_backend.py.

Change-Id: I37df56a61cd5ab332dcc9d74a7e99ee9041aa32e
Imported Translations from Transifex

Change-Id: Idbe625a32001b08e4e2c125d65397ba61ff58589
Merge "LDAP get_project_users should not return password"
Merge "Remove how to contribute section in favor of CONTRIBUTING.rst"
Merge "Imported Translations from Transifex"
Merge "Http 400 when project enabled is not a boolean"
Merge "Remove a stat warning log"
Merge "Correct the resolving api logic in stat middleware"
Merge "Move user fileds type check to identity.Manager"
Merge "Adds tests for XML version response"