[
https://issues.apache.org/jira/browse/JCLOUDS-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13948532#comment-13948532
]
Jasdeep Hundal edited comment on JCLOUDS-515 at 3/26/14 10:02 PM:
------------------------------------------------------------------
Ah, I realize after looking at this end result of this, the volume was created,
but constructing the Volume object as the return value is what failed. Not sure
if the fix is elsewhere as a result of though (is something further up in the
code not setting the availability zone/is that returned from Cinder?).
was (Author: jasdeep):
Ah, I realize after looking at this end result of this, the volume was created,
but constructing the Volume object as the return value is what failed.
> Cinder volume create does not require availability zone
> -------------------------------------------------------
>
> Key: JCLOUDS-515
> URL: https://issues.apache.org/jira/browse/JCLOUDS-515
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-core
> Affects Versions: 1.7.1
> Reporter: Jasdeep Hundal
> Assignee: Jasdeep Hundal
> Fix For: 1.8.0
>
>
> Openstack Cinder does not require specifying an availability zone for volume
> creation, but the Cinder API as implemented in JClouds does. We should change
> the check in the constructor of org.jclouds.openstack.cinder.v1.domain to
> allow a null value for availability zone.
> The docs on the v1 API are not readily available but tracing through the
> Cinder source code, we find this line that gets executed if we specify no
> availability zone in either the v1 or v2 block storage APIs:
> https://github.com/openstack/cinder/blob/master/cinder/volume/flows/api/create_volume.py#L247
> It can also be noted the the Block Storage v2 request here does not require
> an availability zone:
> http://docs.openstack.org/api/openstack-block-storage/2.0/content/POST_createVolume_v2__tenant_id__volumes_Volumes.html
--
This message was sent by Atlassian JIRA
(v6.2#6252)
