While I love deleting code as much (or more) than the next developer, we can’t just remove this in 1.8. We'd be effectively penalizing early adopters of OpenStack and jclouds.
When it comes to removing code I’d like jclouds to stick to semver as much as possible. Backwards incompatible changes are only done in major point releases. In this case, the quotas code should be deprecated and comment made saying why it’s deprecated, what should be used instead, and that it will be removed in 2.0. Thoughts? Everett On Apr 8, 2014, at 7:24 PM, Jasdeep Hundal <[email protected]> wrote: > 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
