openstack/keystone
Code Issues Proposed changes

Readability/Typo Fixes in Release Notes

Browse Source 
Fixed a number of readability and typo issues with the release notes
found while reviewing them.

Change-Id: Iff20bce313e93192f9e0c6d2df3bb0e9908a21d4
This commit is contained in:
Kenny Johnston 2017-02-06 15:50:07 -06:00 committed by Steve Martinelli
parent aeb51c84bb
commit 2fadadbb8c
4 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
releasenotes/notes/bp-allow-expired-f5d845b9601bc1ef.yaml
View File

@ -12,7 +12,7 @@ upgrade:
expired tokens via the ``allow_expired`` flag. The length of time a token is
retrievable for beyond its traditional expiry is managed by the
``[token] allow_expired_window`` option and so the data must be retrievable
for this about of time. When using fernet tokens this means that the key
rotation period must exceed this time so that older tokens are still
decrytable. Ensure that you do not rotate fernet keys faster than
for this amount of time. When using fernet tokens this means the key
rotation period must exceed this time so older tokens are still
decryptable. Ensure you do not rotate fernet keys faster than
``[token] expiration`` + ``[token] allow_expired_window`` seconds.

2
releasenotes/notes/bp-support-federated-attr-94084d4073f50280.yaml
View File

@ -3,5 +3,5 @@ features:
- >
[`blueprint support-federated-attr <https://blueprints.launchpad.net/keystone/+spec/support-federated-attr>`_]
Added new filters to the `list user` API (``GET /v3/users``) to support
querying federted identity atttributes: ``idp_id``, ``protocol_id``, and
querying federated identity atttributes: ``idp_id``, ``protocol_id``, and
``unique_id``.

8
releasenotes/notes/bug-1561054-dbe88b552a936a05.yaml
View File

@ -4,13 +4,13 @@ prelude: >
upgrade:
- >
[`bug 1561054 <https://bugs.launchpad.net/keystone/+bug/1561054>`_]
The default token provider has switched from UUID to Fernet. Please note that
The default token provider has switched from UUID to Fernet. Please note
Fernet requires a key repository to be in place prior to running Ocata,
this can be done running ``keystone-manage fernet_setup``.
Additionally, for multi-node deployments, it is imperative that a key
this can be done by running ``keystone-manage fernet_setup``.
Additionally, for multi-node deployments, it is imperative a key
distribution process be in use before upgrading. Once a key repository has
been created it should be distributed to all keystone nodes in the deployment.
This ensures that each keystone node will be able to validate tokens issued
This ensures each keystone node will be able to validate tokens issued
across the deployment. If you do not wish to switch token formats, you will
need to explicitly set the token provider for each node in the deployment
by setting ``[token] provider`` to ``uuid`` in ``keystone.conf``.

2
releasenotes/notes/bug-1642687-5497fb56fe86806d.yaml
View File

@ -12,7 +12,7 @@ upgrade:
- >
[`bug 1642687 <https://bugs.launchpad.net/keystone/+bug/1642687>`_]
Upon a successful upgrade, all existing ``identity providers`` will now
be associated with a automatically created domain. Each ``identity provider``
be associated with an automatically created domain. Each ``identity provider``
that existed prior to the `Ocata` release will now have a ``domain_id`` field.
The new domain will have an ``id`` (random UUID), a ``name`` (that will match
the ``identity provider`` ID , and be ``enabled`` by default.