<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2015-08-29 2:07 GMT+08:00 Matt Riedemann <span dir="ltr"><<a href="mailto:mriedem@linux.vnet.ibm.com" target="_blank">mriedem@linux.vnet.ibm.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
On 8/28/2015 10:35 AM, Joe Gordon wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
On Aug 28, 2015 6:49 AM, "Sean Dague" <<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a><br></span><div><div class="h5">
<mailto:<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>>> wrote:<br>
><br>
> On 08/28/2015 09:32 AM, Alex Meade wrote:<br>
> > I don't know if this is really a big problem. IMO, even with<br>
> > microversions you shouldn't be implementing things that aren't<br>
backwards<br>
> > compatible within the major version. I thought the benefit of<br>
> > microversions is to know if a given feature exists within the major<br>
> > version you are using. I would consider a breaking change to be a major<br>
> > version bump. If we only do a microversion bump for a backwards<br>
> > incompatible change then we are just using microversions as major<br>
versions.<br>
><br>
> In the Nova case, Microversions aren't semver. They are content<br>
> negotiation. Backwards incompatible only means something if time's arrow<br>
> only flows in one direction. But when connecting to a bunch of random<br>
> OpenStack clouds, there is no forced progression into the future.<br>
><br>
> While each service is welcome to enforce more compatibility for the sake<br>
> of their users, one should not assume that microversions are semver as a<br>
> base case.<br>
><br>
> I agree that 'latest' is basically only useful for testing. The<br>
<br>
Sounds like we need to update the docs for this.<br>
<br>
> python-novaclient code requires a microversion be specified on the API<br>
> side, and on the CLI side negotiates to the highest version of the API<br>
> that it understands which is supported on the server -<br>
><br>
<a href="https://github.com/openstack/python-novaclient/blob/d27568eab50b10fc022719172bc15666f3cede0d/novaclient/__init__.py#L23" rel="noreferrer" target="_blank">https://github.com/openstack/python-novaclient/blob/d27568eab50b10fc022719172bc15666f3cede0d/novaclient/__init__.py#L23</a><br>
<br>
Considering how unclear these two points appear to be, are they clearly<br>
documented somewhere? So that as more projects embrace microversions,<br>
they don't end up having the same discussion.<br>
</div></div></blockquote>
<br>
Yar: <a href="https://review.openstack.org/#/c/218403/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/218403/</a></blockquote><div><br></div><div>Also agree with warning this. ++ for the doc update.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
><br>
> -Sean<br>
><br>
> --<br>
> Sean Dague<br>
> <a href="http://dague.net" rel="noreferrer" target="_blank">http://dague.net</a><br>
><br>
><br>
__________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br></span>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><span class=""><br>
<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</span></blockquote><span class="HOEnZb"><font color="#888888">
<br>
-- <br>
<br>
Thanks,<br>
<br>
Matt Riedemann</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>