Replace local storage of domain UUIDs with leader storage
Currently the Keystone leader charm creates new domains and stores
the UUIDs locally on disk. This approach predates charm relation-/
leader- storage, is error prone, and causes problems in HA setups.
Move to leader storage and remove old interfaces. There is no need
to migrate the on-disk stored data as it is read from the deployment
and stored as a part of the upgrade process.
Do not set default values for service_tenant_id, admin_domain_id and
default_domain_id. This will cause context to be incomplete on peer
units until the values are actually available.
Change functional tests to run on Keystone cluster to verify contents of
configuration and operation of services in clustered environment.
Reviewed: https:/ /review. openstack. org/403601 /git.openstack. org/cgit/ openstack/ charm-keystone/ commit/ ?id=4d2ab6668f8 601a17bbda1bf89 ab7633f22d8d3d
Committed: https:/
Submitter: Jenkins
Branch: master
commit 4d2ab6668f8601a 17bbda1bf89ab76 33f22d8d3d
Author: Frode Nordahl <email address hidden>
Date: Mon Nov 28 09:33:55 2016 +0100
Replace local storage of domain UUIDs with leader storage
Currently the Keystone leader charm creates new domains and stores
the UUIDs locally on disk. This approach predates charm relation-/
leader- storage, is error prone, and causes problems in HA setups.
Move to leader storage and remove old interfaces. There is no need
to migrate the on-disk stored data as it is read from the deployment
and stored as a part of the upgrade process.
Do not set default values for service_tenant_id, admin_domain_id and domain_ id. This will cause context to be incomplete on peer
default_
units until the values are actually available.
Change functional tests to run on Keystone cluster to verify contents of
configuration and operation of services in clustered environment.
Closes-Bug: 1637453 27cc691e9b52dd8 89d60c05fa9
Change-Id: Id0eaf7bfceead6