os-quota-class-sets API reference is confusing for volume type usage

Bug #1794120 reported by Matt Riedemann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Medium
Matt Riedemann

Bug Description

Looking at https://developer.openstack.org/api-ref/block-storage/v3/#update-quota-classes-for-a-project it has a "volume-type" request parameter, but there isn't a quota class set on a specific volume type, it's quota for a specific resource within a volume type, and those are "volumes", "gigabytes" and "snapshots".

The https://developer.openstack.org/api-ref/block-storage/v3/#update-quotas-for-a-project API reference is actually more clear because it has parameters like:

volumes_{volume_type}

snapshots_{volume_type}

gigabytes_{volume_type}

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

Fix proposed to branch: master
Review: https://review.openstack.org/604808

Changed in cinder:
assignee: nobody → Matt Riedemann (mriedem)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.openstack.org/604808
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=b2276d693a45d8595d4317f8d84fe8bbcae41664
Submitter: Zuul
Branch: master

commit b2276d693a45d8595d4317f8d84fe8bbcae41664
Author: Matt Riedemann <email address hidden>
Date: Mon Sep 24 11:08:24 2018 -0400

    api-ref: fix req/resp params for v3 os-quota-class-sets

    The volume-type parameter in the update quota class sets
    API reference was confusing. The volume_type is a namespace
    on quota class values for snapshots, volumes and gigabytes.
    The os-quota-sets API reference had this documented correctly,
    so the os-quota-sets parameter values are re-used here for
    os-quota-class-sets.

    Change-Id: I6e8993f909834797572ec4b911bf709c3701fff1
    Closes-Bug: #1794120

Changed in cinder:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/cinder 14.0.0.0rc1

This issue was fixed in the openstack/cinder 14.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.