<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Can you clarify if the feature is being deprecated – as in still usable but not recommended with a warning, or dropped, as-in, won’t work at all? You mention both in the first two sentences.</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Morgan Fainberg <<a href="mailto:morgan.fainberg@gmail.com">morgan.fainberg@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, February 19, 2015 at 12:32 PM<br>
<span style="font-weight:bold">To: </span>openstack-operators <<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>[Openstack-operators] [Keystone] Deprecation of Eventlet deployment in Kilo (Removal for "M"-release)<br>
</div>
<div><br>
</div>
<div><style>body{font-family:Helvetica,Arial;font-size:13px}</style>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
<div id="bloop_customfont" style="margin: 0px;">The Keystone development team is planning to deprecate deployment of Keystone under Eventlet during the Kilo cycle. Support for deploying under eventlet will be dropped as of the “M”-release of OpenStack.</div>
<div id="bloop_customfont" style="margin: 0px;"><br>
</div>
<div id="bloop_customfont" style="margin: 0px;">The reasoning behind this move is multifaceted but the core of the reasons are as follows:</div>
<div id="bloop_customfont" style="margin: 0px;"><br>
</div>
<ul>
<li>Keystone relies on apache/web-server modules to handle federated identity (validation of SAML, etc) and similar SSO type authentication (Kerberos).</li><li>Eventlet has proven problematic when it comes to workloads within Keystone, notably that a number of actions cannot yield (either due to lacking in Eventlet, or that the dependent library uses C-bindings that eventlet is not able to work with).</li><li>Keystone has recommended (for multiple cycles) deploying Keystone under apache instead of eventlet. In the gate we primarily test all new development under Apache/mod_wsgi deployments. </li><li>Most deployers I’ve discussed keystone deployment with are either already on httpd+mod_wsgi or looking to move that direction (for support of features such as federated auth).</li></ul>
<div>The review to finalize the deprecation is: <a href="https://review.openstack.org/#/c/157495/">https://review.openstack.org/#/c/157495/</a> (Please only provide comments on deprecation, verbiage can be modified separately from the actual act of deprecation).</div>
<div><br>
</div>
<div>Please comment on the review or in reply to this Email.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>—Morgan</div>
<br>
<div id="bloop_sign_1424373821460910080" class="bloop_sign">
<div style="font-family: helvetica, arial;">-- <br>
Morgan Fainberg</div>
</div>
</div>
</div>
</div>
</span><br>
<hr>
<font face="Arial" color="Gray" size="1">This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely
for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to
this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.<br>
</font>
</body>
</html>