ec44fc8999
This patch adds a new REST API microversion to expose the new use_quota DB field present in volumes and snapshots. The field will be reported when listing and showing resources and can be used when filtering as well. The field is exposed in the REST API as `consumes_quota` to prevent confusion for users and admins, since exposing it as `use_quota` may give them the wrong impression that they can set it up for their own purposes. For users we say what is happening with the quota for that resource -it consumes or doesn't consume quota-, whereas internally we express instruction to the core code -whether to use quota or not-, hence the difference in the naming. APIImpact DocImpact Implements: blueprint temp-resources Change-Id: I655a47fc75ddc11caf1defe984d9a66a9ad5a2e7
15 lines
598 B
YAML
15 lines
598 B
YAML
---
|
|
features:
|
|
- |
|
|
Starting with API microversion 3.65, a ``consumes_quota`` field
|
|
is included in the response body of volumes and snapshots to indicate
|
|
whether the volume is using quota or not.
|
|
|
|
Additionally, ``consumes_quota`` can be used as a listing filter for
|
|
volumes and snapshots. Its availability is controlled by its inclusion in
|
|
``etc/cinder/resource_filters.json``, where it is included by default. The
|
|
default listing behavior is not to use this filter.
|
|
|
|
Only temporary resources created internally by cinder will have the value
|
|
set to ``false``.
|