<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div dir="ltr">Just a thought: With the way we currently do microversions, wouldnt this request 2.40 for every request ? There's a pretty good chance that would break things.<br>
<br>
Rob</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 20 January 2017 at 00:02, Richard Jones <span dir="ltr">
<<a href="mailto:r1chardj0n3s@gmail.com" target="_blank">r1chardj0n3s@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
FFE granted for the three patches. We need to support that nova API change.<br>
<div>
<div class="h5"><br>
On 20 January 2017 at 01:28, Radomir Dopieralski <<a href="mailto:openstack@sheep.art.pl">openstack@sheep.art.pl</a>> wrote:<br>
> I would like to request a feature freeze exception for the following patch:<br>
><br>
> <a href="https://review.openstack.org/#/c/410337" rel="noreferrer" target="_blank">
https://review.openstack.org/#<wbr>/c/410337</a><br>
><br>
> This patch adds support for retrieving the simple tenant usages from Nova in<br>
> chunks, and it is necessary for correct data given that related patches have<br>
> been already merged in Nova. Without<br>
> it, the data received will be truncated.<br>
><br>
> In order to actually use that patch, however, it is necessary to set the<br>
> Nova API version to at least<br>
> version 3.40. For this, it's necessary to also add this patch:<br>
><br>
> <a href="https://review.openstack.org/422642" rel="noreferrer" target="_blank">
https://review.openstack.org/<wbr>422642</a><br>
><br>
> However, that patch will not work, because of a bug in the VersionManager,<br>
> which for some reason<br>
> uses floating point numbers for specifying versions, and thus understands<br>
> 2.40 as 2.4. To fix that, it<br>
> is also necessary to merge this patch:<br>
><br>
> <a href="https://review.openstack.org/#/c/410688" rel="noreferrer" target="_blank">
https://review.openstack.org/#<wbr>/c/410688</a><br>
><br>
> I would like to request an exception for all those three patches.<br>
><br>
> An alternative to this would be to finish and merge the microversion<br>
> support, and modify the first patch to make use of it. Then we would need<br>
> exceptions for those two patches.<br>
><br>
</div>
</div>
> ______________________________<wbr>______________________________<wbr>______________<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.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">
http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
><br>
<br>
______________________________<wbr>______________________________<wbr>______________<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.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</blockquote>
</div>
<br>
</div>
</body>
</html>