create volume from image API level constraints
Bug #1111308 reported by
Mate Lakat
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Creating volumes from glance does make assumptions on the underlying copy implementation. Hardwired values tie together the api and the implementation.
An example to make it clearer:
- If there is a volume driver, that could deal with ovf images as well, it should be able to tell the API to let such requests in.
The change that added the constraints is:
https:/
The constraints should be exposed by the driver.
Changed in cinder: | |
status: | New → Fix Committed |
Changed in cinder: | |
milestone: | none → grizzly-3 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | grizzly-3 → 2013.1 |
To post a comment you must log in.
The same problem happens during upload:
+ cinder upload-to-image --container- format= ovf --disk-format=vhd f1aab857- 2459-419a- b7d2-527458f5a9 ef imagefromvolume d927-437f- 807e-f307f56fb4 1f)
ERROR: Invalid input received: Image format must be one of raw, qcow2, vmdk, or vdi. (HTTP 400) (Request-ID: req-c4a63731-