[openstack-dev] [Cinder] Do we need to fix issues in V1 API?

Ivan Kolodyazhny e0ne at e0ne.info
Tue May 26 12:44:19 UTC 2015


 AFAIK, we're going to remove API v1 from Cinder in Liberty. So it makes no
sense to fix it in master.


Regards,
Ivan Kolodyazhny

On Tue, May 26, 2015 at 3:36 PM, Duncan Thomas <duncan.thomas at gmail.com>
wrote:

> 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.deore at 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.thomas at 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.deore at 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-request at 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-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Duncan Thomas
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150526/29c756c9/attachment.html>


More information about the OpenStack-dev mailing list