Yeah we’re still using v1 as the clients that are packaged with most distros don’t support v2 easily.
Eg. with Ubuntu Trusty they have version 1.1.1, I just updated our “volume” endpoint to point to v2 (we have a volumev2 endpoint too) and the client breaks. $ cinder list ERROR: OpenStack Block Storage API version is set to 1 but you are accessing a 2 endpoint. Change its value through --os-volume-api-version or env[OS_VOLUME_API_VERSION]. Sam > On 29 Sep 2015, at 8:34 am, Matt Fischer <m...@mattfischer.com> wrote: > > Yes, people are probably still using it. Last time I tried to use V2 it > didn't work because the clients were broken, and then it went back on the > bottom of my to do list. Is this mess fixed? > > http://lists.openstack.org/pipermail/openstack-operators/2015-February/006366.html > > <http://lists.openstack.org/pipermail/openstack-operators/2015-February/006366.html> > > On Mon, Sep 28, 2015 at 4:25 PM, Ivan Kolodyazhny <e...@e0ne.info > <mailto:e...@e0ne.info>> wrote: > Hi all, > > As you may know, we've got 2 APIs in Cinder: v1 and v2. Cinder v2 API was > introduced in Grizzly and v1 API is deprecated since Juno. > > After [1] is merged, Cinder API v1 is disabled in gates by default. We've got > a filed bug [2] to remove Cinder v1 API at all. > > > According to Deprecation Policy [3] looks like we are OK to remote it. But I > would like to ask Cinder API users if any still use API v1. > Should we remove it at all Mitaka release or just disable by default in the > cinder.conf? > > AFAIR, only Rally doesn't support API v2 now and I'm going to implement it > asap. > > [1] https://review.openstack.org/194726 <https://review.openstack.org/194726> > [2] https://bugs.launchpad.net/cinder/+bug/1467589 > <https://bugs.launchpad.net/cinder/+bug/1467589> > [3] > http://lists.openstack.org/pipermail/openstack-dev/2015-September/073576.html > <http://lists.openstack.org/pipermail/openstack-dev/2015-September/073576.html> > Regards, > Ivan Kolodyazhny > > _______________________________________________ > OpenStack-operators mailing list > openstack-operat...@lists.openstack.org > <mailto:openstack-operat...@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators> > > > _______________________________________________ > OpenStack-operators mailing list > openstack-operat...@lists.openstack.org > <mailto:openstack-operat...@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators>
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
