diff options
| author | Stephen Finucane <sfinucan@redhat.com> | 2021-11-29 11:26:13 +0000 |
|---|---|---|
| committer | Stephen Finucane <sfinucan@redhat.com> | 2022-10-11 16:52:08 +0100 |
| commit | 09ff9a0f4c118f50924d2fc078d6a4501e696224 (patch) | |
| tree | cf42bc22f0c9754ae9f846d3769ae4f646177418 /releasenotes/notes | |
| parent | 1ff839da76545f1c3e1a7df48eb8fb91ebf45abb (diff) | |
| download | python-openstackclient-09ff9a0f4c118f50924d2fc078d6a4501e696224.tar.gz | |
quota: Deprecate "force" behavior for network quotas
In change Idc1b99492d609eb699d0a6bef6cd760458a774f6, we added a
'--check-limit' option to enable "no force" behavior for network quotas.
This was already the default for compute quotas. Provide a path for
harmonizing the behavior of the two options by instead using a
'--no-force' option which will become the eventual default for the
network quotas also.
Change-Id: I25828a3d68e2e900f498e17a0d01fb70be77548e
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
Diffstat (limited to 'releasenotes/notes')
| -rw-r--r-- | releasenotes/notes/no-force-limit-quota-cc7f291dd1b537c1.yaml | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/releasenotes/notes/no-force-limit-quota-cc7f291dd1b537c1.yaml b/releasenotes/notes/no-force-limit-quota-cc7f291dd1b537c1.yaml new file mode 100644 index 00000000..53b7eb8d --- /dev/null +++ b/releasenotes/notes/no-force-limit-quota-cc7f291dd1b537c1.yaml @@ -0,0 +1,13 @@ +--- +features: + - Add ``--no-force`` option to the ``openstack quota set`` command (only + for compute and network commands). When specified, the compute and network + quota engine will check the resource usage before setting the new quota + limit. This is the default behavior of the compute quota engine and will + become the default for the network quota engine in a future release. +deprecations: + - The ``openstack quota set`` command currently defaults to ``--force`` + behavior for network quotas. This behavior is now deprecated and a future + release will switch to ``--no-force`` behavior. Users should explicitly + specify one of these options to prevent a potentially breaking change in + behavior. |