puppet-keystone/releasenotes/notes/add-keystone-bootstrap-class-43e975beae3ec88b.yaml
Tobias Urdin bc1ff1d7cb Add keystone::bootstrap class
This class combines the keystone-manage bootstrap command
from init, the keystone::endpoint functionality that manages
the keystone endpoints and the keystone::roles::admin class
that manages users and projects.

This is one of the steps to make sure we only have a single
point of entry for bootstrapping (keystone-manage bootstrap)
and then only managing resources after that.

This is especially required since we are getting rid of the
admin token and cannot manage resources before keystone-manage
bootstrap has created the user, project, service and endpoints
for us.

These resources should always be in the default domain and
deployments should manage domain specific configuration themselves
using the provider resources.

This class uses the default values from the keystone-manage
bootstrap command.

In the past puppet-keystone has always created a openstack project
that is assumed as a admin project even though the bootstrap command
creates the admin project. Since this uses the default values from
the bootstrap command we should move away from having an openstack
project, if we need that in testing it should be created there and
not in the default deployment.

Depends-On: https://review.opendev.org/#/c/698528/
Change-Id: I683fcdd743bddf6d4e989dd7e7c553db745934db
2019-12-11 16:37:51 +00:00

20 lines
894 B
YAML

---
features:
- |
Added keystone::bootstrap class.
upgrade:
- |
Now that the keystone::endpoint and keystone::roles::admin classes is deprecated
and has no effect deployments must define the new keystone::bootstrap class with
the proper data that was earlier passed to those classes. Please go through the
parameters in keystone::bootstrap carefully and define the class.
- |
If you are using a multi-domain setup where you previously relied on keystone::endpoint
and/or keystone::roles::admin to create your domains and domain scoped admin accounts
the keystone::bootstrap does not do this and you need to ensure this is managed in your
deployment using the keystone provider resources.
deprecations:
- |
The keystone::endpoint and keystone::roles::admin classes is now deprecated
and has no effect. Please read the upgrade notes carefully!