jclouds-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jasdeep Hundal <jasdeep.singh.hun...@gmail.com>
Subject Fixing JClouds after removal of volume code from Nova in Grizzly
Date Wed, 09 Apr 2014 00:24:03 GMT
Nova-volume was deprecated in Folsom/removed in Grizzly. Now Nova returns
errors when trying to submit volume related quotas, which JClouds always
does when submitting a Quota. I'm going to want to fix this, but is it
better to make those elements optional in order to support folks using
older versions of Nova or to remove this entirely from JClouds 1.8 onwards?

It may also make sense to make every quota setting optional, since that
should be possible according to the API docs:
http://docs.openstack.org/api/openstack-compute/2/content/PUT_os-quota-sets-v2_updateQuota_v2__tenant_id__os-quota-sets__tenant_id__ext-os-quota-sets.html

Ticket for this issue with a bit more detail:
https://issues.apache.org/jira/browse/JCLOUDS-527

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message