<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Thanks. This addresses my concerns.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Tim<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Morgan Fainberg [mailto:morgan.fainberg@gmail.com]
<br>
<b>Sent:</b> 19 April 2015 18:34<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [keystone] keystone middleware package changing release method in Liberty<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><br>
<br>
On Sunday, April 19, 2015, Tim Bell <<a href="mailto:Tim.Bell@cern.ch">Tim.Bell@cern.ch</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal" style="margin-bottom:12.0pt">> -----Original Message-----<br>
> From: Morgan Fainberg [mailto:<a href="javascript:;">morgan.fainberg@gmail.com</a>]<br>
> Sent: 18 April 2015 05:20<br>
> To: OpenStack Development Mailing List<br>
> Subject: [openstack-dev] [keystone] keystone middleware package changing<br>
> release method in Liberty<br>
><br>
> Hi everyone,<br>
><br>
> I wanted to communicate to the community that the Keystone development<br>
> team has determined that keystonemiddleware package should no longer be<br>
> released in the same manner as the client libraries. Instead we will be releasing<br>
> keystonemiddleware in the same manner as Keystone, in the coordinated style.<br>
><br>
> There are a number of reasons but the largest factor is coordinating the<br>
> requirements. Since keystonemiddleware runs in the process space / interpreter<br>
> for the services (e.g. Nova) there is no expectation that the version of<br>
> keystonemiddleware from Juno will run in Liberty nova (or vice versa).<br>
><br>
<br>
Will this require that the keystonemiddleware is upgraded at the same as the Keystone server across a cloud or at the same time as services such as Nova ?<br>
<br>
Many sites do a component based staged upgrade. This would mean an approach such as upgrading ceilometer or cinder to Liberty significantly before the Nova upgrade with Keystone in the middle.<br>
<br>
- Would the new keystonemiddleware work with the old Keystone version ?<br>
- How would multi-service controllers be upgraded where services such as Nova and cinder controllers share the same server ?<o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Keystonemiddleware will work with different versions of keystone. It will be coupled to the requirements for nova/glance/etc (and have tags for the milestones for the named release). The stability of keystone's APIs and how middleware communicates
to keystone will not change. We may have 2-cycle deprecation of lingering unused features. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">This is strictly that we will be doing following the release schedule of the server projects not changing stability or interoperability. With the exception of potentially doing a 2-cycle deprecation of un-used features (as mentioned above). <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">--Morgan <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">> With this in mind we will be updating all of the testing and gating to make<br>
> keystonemiddleware conform in the same manner as the services that utilize it.<br>
> This change will start with the Liberty release cycle. Kilo and previous releases of<br>
> OpenStack will continue to rely on the 1.x.x semver releases that mirror the<br>
> stable/xxx branches of keystonemiddleware.<br>
><br>
> Version numbers and other choices related to this change will be discussed with<br>
> the Release Management team and updated during the Liberty cycle. This will<br>
> not impact or change our support plans for the kilo or Juno releases / associated<br>
> versions of keystonemiddleware. (Full support and maintenance is planned for<br>
> the lifespan of Juno and Kilo releases).[1]<br>
><br>
> Please feel free to respond in this thread or speak with us on IRC if you have<br>
> questions of concerns about this change.<br>
><br>
> Cheers,<br>
> Morgan<br>
><br>
><br>
> [1] Note: keystonemiddleware was not used by the integrated release until Juno.<br>
><br>
> Sent via mobile<br>
> _________________________________________________________________<br>
> _________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>