v2 API doesn't allow specifying volume type by name

Bug #1228835 reported by Avishay Traeger on 2013-09-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
High
Huang Zhiteng

Bug Description

v2 API doesn't allow specifying volume type by name while v1 does allow it.

Changed in cinder:
assignee: nobody → Huang Zhiteng (zhiteng-huang)
Changed in cinder:
importance: Undecided → High
status: New → Confirmed
Changed in cinder:
milestone: none → havana-rc1
Changed in cinder:
status: Confirmed → In Progress

Reviewed: https://review.openstack.org/47986
Committed: http://github.com/openstack/cinder/commit/64f24b9323b0860ddf01bcd012f986c65d2956cc
Submitter: Jenkins
Branch: master

commit 64f24b9323b0860ddf01bcd012f986c65d2956cc
Author: Zhiteng Huang <email address hidden>
Date: Tue Sep 24 16:09:42 2013 +0800

    Allow v2 Volume API to create volume with type name

    v2 API only accepts volume type ID when creating volume, while v1
    API allows both volume type name and ID (volume type name is unique
    in Cinder). This patch enables v2 API to accept volume type name
    as create() parameter. Aslo volume type validation code block
    in v1 API create() is refactored to a slimmer version.

    Change-Id: I4ee98b67a0a0e98ff4d402749e12b1335d45f64d
    Close-bug: 1228835

Thierry Carrez (ttx) on 2013-09-30
Changed in cinder:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2013-10-04
Changed in cinder:
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2013-10-17
Changed in cinder:
milestone: havana-rc1 → 2013.2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers