<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">With nova and Keystone both at v3 is helps to consistent versioning across all projects.<o:p></o:p></p>
<p class="MsoNormal">Still need documentation for transition clients from one API version to next.
<o:p></o:p></p>
<p class="MsoNormal">With new functionality not available in previous version it should be easier than API changes.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p>-----Original Message-----<br>
From: Walter A. Boring IV [mailto:walter.boring@hpe.com] <br>
Sent: Friday, February 19, 2016 4:18 PM<br>
To: openstack-dev@lists.openstack.org<br>
Subject: Re: [openstack-dev] [cinder] adding a new /v3 endpoint for api-microversions<br>
<br>
<br>
>> But, there are no such clients today. And there is no library that <br>
>> does this yet. It will be 4 - 6 months (or even more likely 12+) <br>
>> until that's in the ecosystem. Which is why adding the header <br>
>> validation to existing<br>
>> v2 API, and backporting to liberty / kilo, will provide really <br>
>> substantial coverage for the concern the bswartz is bringing forward.<br>
> Yeah, I have to agree with that. We can certainly have the protection <br>
> out in time.<br>
><br>
> The only concern there is the admin who set up his Kilo initial <br>
> release cloud and doesn't want to touch it for updates. But they <br>
> likely have more pressing issues than this any way.<br>
><br>
>> -Sean<br>
>><br>
>><br>
<br>
Not that I'm adding much to this conversation that hasn't been said already, but I am pro v2 API, purely because of how painful and long it's been to get the official OpenStack projects to adopt the v2 API from v1. I know we need to be sort of concerned about
other 'client's <br>
that call the API, but for me that's way down the lists of concerns. <br>
If we go to v3 API, most likely it's going to be another 3+ years before folks can use the new Cinder features that the microversioned changes will provides. This in effect invalidates the microversion capability in Cinder's API completely.<br>
<br>
/sadness<br>
Walt<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<o:p></o:p></p>
</div>
</body>
</html>