You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and `system scope specification <https://specs.openstack.org/openstack/keystone-specs/specs/keystone/queens/system-scope.html>`_ to understand the scope concept.
43
43
44
-
In the Nova 21.0.0 (Ussuri) release, Nova policies implemented
44
+
In the Nova 25.0.0 (Yoga) release, Nova policies implemented
45
45
the scope concept and default roles provided by keystone (admin, member,
46
46
and reader). Using common roles from keystone reduces the likelihood of
47
47
similar, but different, roles implemented across projects or deployments
@@ -112,15 +112,15 @@ Policies with a ``scope_type`` of ``system and project`` means a user with a
112
112
resource. All the system and project level operation's policies have defaulted
113
113
to ``scope_type`` of ``['system', 'project']``.
114
114
115
-
For example, consider the ``POST /servers/{server_id}/action (os-migrateLive)``
115
+
For example, consider the ``GET /flavors/{flavor_id}/os-extra_specs/{flavor_extra_spec_key}``
116
116
API.
117
117
118
118
.. code::
119
119
120
-
# Live migrate a server to a new host without a reboot
121
-
# POST /servers/{server_id}/action (os-migrateLive)
120
+
# Show an extra spec for a flavor
121
+
# GET /flavors/{flavor_id}/os-extra_specs/{flavor_extra_spec_key}
0 commit comments