Thanks ☺ From: Duncan Thomas [mailto:duncan.tho...@gmail.com] Sent: 26 May 2015 18:07 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Cinder] Do we need to fix issues in V1 API?
I don't think either of those are likely to be accepted for V1, certainly I'd vote against it. They should be fixed in V2 however. On 26 May 2015 at 15:13, Deore, Pranali11 <pranali11.de...@nttdata.com<mailto:pranali11.de...@nttdata.com>> wrote: Hi Duncan, I am planning to fix following issues for V1 API, 1. https://bugs.launchpad.net/cinder/+bug/1454244 2. “VolumeNotFound” exception error message should be consistent across all APIs Please suggest. Thanks From: Duncan Thomas [mailto:duncan.tho...@gmail.com<mailto:duncan.tho...@gmail.com>] Sent: 26 May 2015 17:14 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Cinder] Do we need to fix issues in V1 API? In general, V1 is not being changed / fixed, though it is case-by-case, for example security issues will always be fixed. What exactly were you thinking about fixing? On 26 May 2015 at 14:17, Deore, Pranali11 <pranali11.de...@nttdata.com<mailto:pranali11.de...@nttdata.com>> wrote: Hello, While fixing issues in V2 API, do we need to fix in V1 API? As per following blueprint description, V1 API is being deprecated in liberty-1. https://blueprints.launchpad.net/cinder/+spec/deprecate-v1-api Thanks & Regards, Pranali Deore ______________________________________________________________________ Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Duncan Thomas ______________________________________________________________________ Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Duncan Thomas ______________________________________________________________________ Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding.
__________________________________________________________________________ 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
