<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body>
Need a inline clarification.<br>
<br>
<div class="moz-cite-prefix">On 4/6/16 10:58 AM, Flavio Percoco
wrote:<br>
</div>
<blockquote cite="mid:20160406145848.GF2567@redhat.com" type="cite">On
06/04/16 08:26 -0400, Sean Dague wrote:
<br>
<blockquote type="cite">On 04/06/2016 04:13 AM, Markus Zoeller
wrote:
<br>
<blockquote type="cite">+1 for deprecation and removal
<br>
<br>
To be honest, when I started with Nova during Kilo, I didn't
get
<br>
why we have those passthrough APIs. They looked like
convenience APIs.
<br>
A short history lesson, why they got introduced, would be
cool. I only
<br>
found commit [1] which looks like they were there from the
beginning.
<br>
<br>
References:
<br>
[1]
<br>
<a class="moz-txt-link-freetext" href="https://github.com/openstack/python-novaclient/commit/7304ed80df265b3b11a0018a826ce2e38c052572#diff-56f10b3a40a197d5691da75c2b847d31R33">https://github.com/openstack/python-novaclient/commit/7304ed80df265b3b11a0018a826ce2e38c052572#diff-56f10b3a40a197d5691da75c2b847d31R33</a>
<br>
</blockquote>
<br>
The short history lesson is nova image API existed before
glance. Glance
<br>
was a spin out from Nova of that API. Doing so doesn't
immediately make
<br>
that API go away however. Especially as all these things live on
<br>
different ports with different end points. So the image API
remained as
<br>
a proxy (as did volumes, baremetal, and even to some extend
networks).
<br>
<br>
It's not super clear how you deprecate and remove these things
without
<br>
breaking a lot of people, as a lot of the libraries implement
the nova
<br>
image resources -
<br>
<a class="moz-txt-link-freetext" href="https://github.com/fog/fog-openstack/blob/master/lib/fog/openstack/compute.rb">https://github.com/fog/fog-openstack/blob/master/lib/fog/openstack/compute.rb</a>
<br>
</blockquote>
<br>
We can deprecate it without removing it. We make it work with v2
and start
<br>
warning people that the API is not supported anymore. We don't fix
bugs in that
<br>
API but tell people to use the newer version.
<br>
<br>
I think that should do it, unless I'm missing something.
<br>
Flavio
<br>
<br>
</blockquote>
<br>
Is it a safe practice to not fix bugs on a publicly exposed API?
What are the recommendations for such cases?<br>
<br>
<blockquote cite="mid:20160406145848.GF2567@redhat.com" type="cite">
<blockquote type="cite">
<br>
-Sean
<br>
<br>
-- <br>
Sean Dague
<br>
<a class="moz-txt-link-freetext" href="http://dague.net">http://dague.net</a>
<br>
<br>
__________________________________________________________________________
<br>
OpenStack Development Mailing List (not for usage questions)
<br>
Unsubscribe:
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
<br>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Thanks,
Nikhil</pre>
</body>
</html>