openstack
/
cinder
Code Issues Proposed changes

Fix multiattach policy names in release note 

The policy rules pointed out in this release note were using
variables from the code, not the actual policy rule names that
are actually used in code and would be overridden in the policy
file.

Change-Id: I00ea8702327f5ad5083f97182098346093dd00ee
This commit is contained in:
Matt Riedemann 2018-01-24 15:46:59 -05:00
parent 6bbab2ff57
commit 76f2158d47
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
releasenotes/notes/add_multiattach_policies-8e0b22505ed6cbd8.yaml
View File

@ -3,25 +3,25 @@ features:
- Added policies to disallow multiattach operations. This includes two
policies, the first being a general policy to allow the creation or
retyping of multiattach volumes is a volume create policy with the name
``MULTIATTACH_POLICY``.
``volume:multiattach``.
The second policy is specifically for disallowing the ability to create
multiple attachments on a volume that is marked as bootable, and is an
attachment policy with the name ``MULTIATTACH_BOOTABLE_VOLUME_POLICY``.
attachment policy with the name ``volume:multiattach_bootable_volume``.
The default for these new policies is ``ADMIN_OR_OWNER``; be aware that
if you wish to disable either of these policies for your users you will
need to modify the default policy settings.
The default for these new policies is ``rule:admin_or_owner``; be aware
that if you wish to disable either of these policies for your users you
will need to modify the default policy settings.
upgrade:
- Added policies to disallow multiattach operations. This includes two
policies, the first being a general policy to allow the creation or
retyping of multiattach volumes is a volume create policy with the name
``MULTIATTACH_POLICY``.
``volume:multiattach``.
The second policy is specifically for disallowing the ability to create
multiple attachments on a volume that is marked as bootable, and is an
attachment policy with the name ``MULTIATTACH_BOOTABLE_VOLUME_POLICY``.
attachment policy with the name ``volume:multiattach_bootable_volume``.
The default for these new policies is ``ADMIN_OR_OWNER``; be aware that
if you wish to disable either of these policies for your users you will
need to modify the default policy settings.
The default for these new policies is ``rule:admin_or_owner``; be aware
that if you wish to disable either of these policies for your users you
will need to modify the default policy settings.