<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Jamie<br>
<br>
<div class="moz-cite-prefix">On 2016年04月13日 17:26, Jamie Hannaford
wrote:<br>
</div>
<blockquote cite="mid:1460539600779.87003@rackspace.com" type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style type="text/css" style="display:none"><!-- p { margin-top: 0px; margin-bottom: 0px; }--></style>
<p>I recently discovered that Magnum supports microversions [1] -
but it doesn't seem to be incrementing the API in accordance
with new functionality releases. Is this due to the v1 API not
being locked yet? What is the status of freezing the API, so
that we can move to a microversions-based release cycle?<br>
</p>
</blockquote>
<br>
Microversion is only used after API freezed (to avoid broken SDK
user), but for now, the team don't think Magnum APIs are mature yet.<br>
<br>
I remembered I suggested to bump microversion in one of Magnum
meeting I got the answers.<br>
<br>
<blockquote cite="mid:1460539600779.87003@rackspace.com" type="cite">
<p>
</p>
<p>The API-WG has recently published a guideline [2] that is
very slightly different from how Magnum has implemented it. I'm
in the process of filing a few bugs to address this.<br>
</p>
<p><br>
</p>
</blockquote>
<br>
Yes, I agree to align with API-WG, It will be good to align it with
API-WG. Feel free to submit patch to address them, I am glad to help<br>
review(yes, I'v been involved Nova's microversion development)<br>
<br>
Thanks Eli.<br>
<br>
<blockquote cite="mid:1460539600779.87003@rackspace.com" type="cite">
<p>
</p>
<p>Jamie<br>
</p>
<p><br>
</p>
<p>[1] <a moz-do-not-send="true"
href="https://review.openstack.org/#/c/184975/">https://review.openstack.org/#/c/184975/</a>
<br>
</p>
<p>[2] <a moz-do-not-send="true"
href="https://specs.openstack.org/openstack/api-wg/guidelines/microversion_specification.html">https://specs.openstack.org/openstack/api-wg/guidelines/microversion_specification.html</a> <br>
</p>
<hr>
Rackspace International GmbH a company registered in the Canton of
Zurich, Switzerland (company identification number
CH-020.4.047.077-1) whose registered office is at
Pfingstweidstrasse 60, 8005 Zurich, Switzerland. Rackspace
International GmbH privacy policy can be viewed at
<a class="moz-txt-link-abbreviated" href="http://www.rackspace.co.uk/legal/swiss-privacy-policy">www.rackspace.co.uk/legal/swiss-privacy-policy</a> - This e-mail
message may contain confidential or privileged information
intended for the recipient. Any dissemination, distribution or
copying of the enclosed material is prohibited. If you receive
this transmission in error, please notify us immediately by e-mail
at <a class="moz-txt-link-abbreviated" href="mailto:abuse@rackspace.com">abuse@rackspace.com</a> and delete the original message. Your
cooperation is appreciated.
<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>
<br>
<pre class="moz-signature" cols="72">--
Best Regards, Eli Qiao (乔立勇)
Intel OTC China</pre>
</blockquote>
</body>
</html>