cc869ec7bb
* This commit updates any formatting, grammatical or other issues
in the release notes for Newton
* It also adds any missing yet important release notes to be part of
the release
Also, this commit standardizes release note page ordering:
* In order to support automatically updating the release notes when we
create stable branches, we want the pages to be in a standard order.
This patch updates the order to be reverse chronological, so the
most recent notes appear at the top. ( Inspired by Change
Ib364dcc8eb31275a31c83b68d7914263b183e393 )
Co-Authored-By: Nikhil Komawar <nik.komawar@gmail.com>
Co-Authored-By: Brian Rosmaita <brian.rosmaita@rackspace.com>
Co-Authored-By: Steve Lewis <stevelle@gmail.com>
Change-Id: I9247feb75d2b1b63eecfc4a750fd2aa070ea874b
33 lines
1.4 KiB
YAML
33 lines
1.4 KiB
YAML
---
|
|
prelude: >
|
|
- Deprecate the ``show_multiple_locations`` configuration
|
|
option in favor of the existing Role Based Access
|
|
Control (RBAC) for Image locations which uses
|
|
``policy.json`` file to define the appropriate rules.
|
|
upgrade:
|
|
- |
|
|
Some additional points about ``show_multiple_locations``
|
|
configuration option deprecation.
|
|
|
|
* Maintaining two different ways to configure, enable
|
|
and/or disable a feature is painful for developers and
|
|
operators, so the less granular means of controlling
|
|
this feature will be eliminated in the **Ocata**
|
|
release.
|
|
* For the Newton release, this option will still be
|
|
honored. However, it is important to update
|
|
``policy.json`` file for glance-api nodes. In
|
|
particular, please consider updating the policies
|
|
``delete_image_location``, ``get_image_location`` and
|
|
``set_image_location`` as per your requirements. As
|
|
this is an advanced option and prone to expose some
|
|
risks, please check the policies to ensure security
|
|
and privacy of your cloud.
|
|
* Future releases will ignore this option and just
|
|
follow the policy rules. It is recommended that this
|
|
option is disabled for public endpoints and is used
|
|
only internally for service-to-service communication.
|
|
* As mentioned above, the same recommendation applies
|
|
to the policy-based configuration for exposing
|
|
multiple image locations.
|