Updated openstack/openstack
Project: openstack/tempest  ff956a6669ecd546de89d43d52771aade0f56896
null
Implement pluggability for tempest (exceptions)

First patch of three patches:
->1. exceptions
  2. config (+ module_utils.py)
  3. clients

The main intend is in moving currently existed single 'exceptions' module in
exceptions tree.
It allows separate exceptions by differencies:
- base
- main/common
- project-specific

It also allows to simplify search and using of exceptions, merge changes into
Tempest with minimized amount of merge conflicts.

Partially-implements: bp make-tempest-pluggable

Change-Id: I5c50affba0fce721583a6d56216e56c94ec3b188
Updated openstack/openstack
Project: openstack/keystone  1017859b81c4c512673174fe065c9e1bcd4bc448
null
Add the last of the outstanding helpstrings to config

Add the last of the outstanding help strings to the options defined
in keystone.common.config.

Adds in periods to the end of the helpstrings that were missing
proper ending punctuation.

DocImpact

Related-Bug: #1229941
Change-Id: Iebe0358a19f645220eb7b3dfca0dc868716f5bc8
Updated openstack/openstack
Project: openstack/keystone  b870d88c7deeb89bb06b3c58e6dda4ff11510409
null
Always include 'enabled' field in endpoint response

The 'enabled' field wasn't always returned in an endpoint response.

The 'enabled' attribute for endpoints was stored in the 'extra'
column as part of a JSON string. Now the 'enabled' attribute is in
its own column. It will also be easier to filter out disabled
endpoints now that enabled is a separate column.

With the 'enabled' field being a Boolean column in the database,
the server also needs to validate that the value is a Boolean (if
it's present). This is done in the same way that the server checks
the type of the 'enabled' value when creating users.

Closes-Bug: #1282266

Change-Id: I9b9379f4531c298c14508418dbfb629bdd6c2850