[openstack-dev] [nova][glance] Proposal to remove `nova image-*` commands from novaclient

Nikhil Komawar nik.komawar at gmail.com
Wed Apr 6 17:46:28 UTC 2016


Need a inline clarification.

On 4/6/16 10:58 AM, Flavio Percoco wrote:
> On 06/04/16 08:26 -0400, Sean Dague wrote:
>> On 04/06/2016 04:13 AM, Markus Zoeller wrote:
>>> +1 for deprecation and removal
>>>
>>> To be honest, when I started with Nova during Kilo, I didn't get
>>> why we have those passthrough APIs. They looked like convenience APIs.
>>> A short history lesson, why they got introduced, would be cool. I only
>>> found commit [1] which looks like they were there from the beginning.
>>>
>>> References:
>>> [1]
>>> https://github.com/openstack/python-novaclient/commit/7304ed80df265b3b11a0018a826ce2e38c052572#diff-56f10b3a40a197d5691da75c2b847d31R33
>>>
>>
>> The short history lesson is nova image API existed before glance. Glance
>> was a spin out from Nova of that API. Doing so doesn't immediately make
>> that API go away however. Especially as all these things live on
>> different ports with different end points. So the image API remained as
>> a proxy (as did volumes, baremetal, and even to some extend networks).
>>
>> It's not super clear how you deprecate and remove these things without
>> breaking a lot of people, as a lot of the libraries implement the nova
>> image resources -
>> https://github.com/fog/fog-openstack/blob/master/lib/fog/openstack/compute.rb
>>
>
> We can deprecate it without removing it. We make it work with v2 and
> start
> warning people that the API is not supported anymore. We don't fix
> bugs in that
> API but tell people to use the newer version.
>
> I think that should do it, unless I'm missing something.
> Flavio
>

Is it a safe practice to not fix bugs on a publicly exposed API? What
are the recommendations for such cases?

>>
>>     -Sean
>>
>> -- 
>> Sean Dague
>> http://dague.net
>>
>> __________________________________________________________________________
>>
>> 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
>
>
>
> __________________________________________________________________________
> 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

-- 

Thanks,
Nikhil

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160406/cbd31991/attachment.html>


More information about the OpenStack-dev mailing list