[JCLOUDS-515] Cinder volume create does not require availability zone

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.1
• Fix Version/s: 1.7.2, 1.8.0
• Component/s: jclouds-core
• Assignee: Jasdeep Hundal
• Reporter: Jasdeep Hundal
• Created: 25/Mar/14 23:49
• Updated: 31/Mar/14 19:17
• Resolved: 31/Mar/14 19:17

Description

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