Update git submodules
* Update charm-keystone from branch 'master' - Merge "Replace use of admin_token with Keystone bootstrap" - Replace use of admin_token with Keystone bootstrap Stop the use of the admin_token and use the bootstrap process to initialize Keystone instead. Fortunately the implementation of the bootstrap process is both idempotent when it needs to be and it can be safely called on an existing deployment. Subsequently we can migrate by just removing the admin_token from the configuration and create new credentials for use by the charm with a call to ``keystone-manage bootstrap``. Remove configuration templates for versions prior to Mitaka, by doing this we need to move any configuration initially defined prior to Miataka forward to the ``templates/mitaka`` folder. A side effect of this migration is that newly bootstrapped deployments will get their ``default`` domain created with a literal ID of ``default``. Prior to this change third party software making assumptions about that being the case may have had issues. Closes-Bug: #1859844 Closes-Bug: #1837113 Related-Bug: #1774733 Closes-Bug: #1648719 Closes-Bug: #1578678 Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/191 Change-Id: I23940720c24527ee34149f035c3bdf9ff54812c9
This commit is contained in:
parent
e08bfe5bf5
commit
92804430de
|
@ -1 +1 @@
|
|||
Subproject commit 6d6ecea05553eb8dc3b05d7b4c5380d89ad5ddc4
|
||||
Subproject commit 7ff71cad6c9858461165d84430c6cf330c4573f9
|
Loading…
Reference in New Issue