| 1 |
--- |
| 2 |
features: |
| 3 |
- | |
| 4 |
**Policy configuration changes** |
| 5 |
|
| 6 |
Over the Xena and Yoga development cycles, cinder's default policy |
| 7 |
configuration is being modified to take advantage of the default |
| 8 |
authentication and authorization apparatus supplied by the Keystone |
| 9 |
project. This will give operators a rich set of default policies to |
| 10 |
control how users interact with the Block Storage service API. |
| 11 |
|
| 12 |
The details of this project are described in `Policy Personas and |
| 13 |
Permissions |
| 14 |
<https://docs.openstack.org/cinder/xena/configuration/block-storage/policy-personas.html>`_ |
| 15 |
in the `Cinder Service Configuration Guide`. We encourage you to |
| 16 |
read through that document. The following is only a summary. |
| 17 |
|
| 18 |
The primary change in the Xena release is that cinder's default policy |
| 19 |
configuration will recognize the ``reader`` role on a project. |
| 20 |
Additionally, |
| 21 |
|
| 22 |
* Some current rules defined in the policy file are being DEPRECATED |
| 23 |
and will be removed in the Yoga release. You only need to worry |
| 24 |
about this if you have used any of these rules yourself in when |
| 25 |
writing custom policies, as you cannot rely on the following rules |
| 26 |
being pre-defined in the Yoga release. |
| 27 |
|
| 28 |
* ``rule:admin_or_owner`` |
| 29 |
* ``rule:system_or_domain_or_project_admin`` |
| 30 |
* ``rule:volume_extension:volume_type_encryption`` |
| 31 |
|
| 32 |
* Some current policies that were over-general (that is, they governed both |
| 33 |
read and write operations on a resource) are being replaced by a set of |
| 34 |
new policies that provide greater granularity. The following policies |
| 35 |
are DEPRECATED and will be removed in the Yoga release: |
| 36 |
|
| 37 |
* ``group:group_types_manage`` is replaced by: |
| 38 |
|
| 39 |
* ``group:group_types:create`` |
| 40 |
* ``group:group_types:update`` |
| 41 |
* ``group:group_types:delete`` |
| 42 |
|
| 43 |
* ``group:group_types_specs`` is replaced by: |
| 44 |
|
| 45 |
* ``group:group_types_specs:get`` |
| 46 |
* ``group:group_types_specs:get_all`` |
| 47 |
* ``group:group_types:create`` |
| 48 |
* ``group:group_types:update`` |
| 49 |
* ``group:group_types:delete`` |
| 50 |
|
| 51 |
* ``volume_extension:quota_classes`` is replaced by: |
| 52 |
|
| 53 |
* ``volume_extension:quota_classes:get`` |
| 54 |
* ``volume_extension:quota_classes:update`` |
| 55 |
|
| 56 |
* ``volume_extension:types_manage`` is replaced by: |
| 57 |
|
| 58 |
* ``volume_extension:type_create`` |
| 59 |
* ``volume_extension:type_update`` |
| 60 |
* ``volume_extension:type_delete`` |
| 61 |
|
| 62 |
* ``volume_extension:volume_image_metadata`` is replaced by: |
| 63 |
|
| 64 |
* ``volume_extension:volume_image_metadata:show`` |
| 65 |
* ``volume_extension:volume_image_metadata:set`` |
| 66 |
* ``volume_extension:volume_image_metadata:remove`` |
| 67 |
|
| 68 |
* A new policy was introduced to govern an operation previously |
| 69 |
controlled by a policy that is not being removed, but whose other |
| 70 |
governed actions are conceptually different: |
| 71 |
|
| 72 |
* ``volume_extension:volume_type_access:get_all_for_type`` |
| 73 |
|
| 74 |
* A new policy was introduced as part of the feature described |
| 75 |
in the `User visible extra specs |
| 76 |
<https://docs.openstack.org/cinder/xena/admin/blockstorage-user-visible-extra-specs.html>`_ |
| 77 |
section of the `Cinder Administration Guide`: |
| 78 |
|
| 79 |
* ``volume_extension:types_extra_specs:read_sensitive`` |
| 80 |
|
| 81 |
* Many policies had their default values changed and their previous |
| 82 |
values deprecated. These are indicated in the sample policy |
| 83 |
configuration file, which you can view in the `policy.yaml |
| 84 |
<https://docs.openstack.org/cinder/xena/configuration/block-storage/samples/policy.yaml.html>`_ |
| 85 |
section of the `Cinder Service Configuration Guide`. |
| 86 |
|
| 87 |
* In particular, we direct your attention to the default values |
| 88 |
for the policies associated with the Default Volume Types API |
| 89 |
(introduced with microversion 3.62 of the Block Storage API). |
| 90 |
These had experimentally recognized "scope", but for consistency |
| 91 |
with the other rules, their default values no longer recognize |
| 92 |
scope. (Scope will be introduced to all cinder policy defaults |
| 93 |
in the Yoga release.) |
| 94 |
|
| 95 |
* When a policy value is deprecated, the oslo.policy engine will |
| 96 |
check the new value, and if that fails, it will evaluate the |
| 97 |
deprecated value. This behavior may be modified so *only* |
| 98 |
the new policy value is used by setting the configuration option |
| 99 |
``enforce_new_defaults=True`` in the ``[oslo_policy]`` section of |
| 100 |
the cinder configuration file. |
| 101 |
deprecations: |
| 102 |
- | |
| 103 |
The following policy rules have been DEPRECATED in this release and will be |
| 104 |
removed in Yoga: |
| 105 |
|
| 106 |
* ``rule:admin_or_owner`` |
| 107 |
* ``rule:system_or_domain_or_project_admin`` |
| 108 |
* ``rule:volume_extension:volume_type_encryption`` |
| 109 |
|
| 110 |
For more information, see the 'New Features' section of this document and |
| 111 |
`Policy Personas and Permissions |
| 112 |
<https://docs.openstack.org/cinder/xena/configuration/block-storage/policy-personas.html>`_ |
| 113 |
in the `Cinder Service Configuration Guide`. |
| 114 |
- | |
| 115 |
The following policies have been DEPRECATED in this release and will be |
| 116 |
removed in Yoga: |
| 117 |
|
| 118 |
* ``group:group_types_manage`` |
| 119 |
* ``group:group_types_specs`` |
| 120 |
* ``volume_extension:quota_classes`` |
| 121 |
* ``volume_extension:types_manage`` |
| 122 |
* ``volume_extension:volume_image_metadata`` |
| 123 |
|
| 124 |
For more information, see the 'New Features' section of this document and |
| 125 |
`Policy Personas and Permissions |
| 126 |
<https://docs.openstack.org/cinder/xena/configuration/block-storage/policy-personas.html>`_ |
| 127 |
in the `Cinder Service Configuration Guide`. |