<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none"><!-- p { margin-top: 0px; margin-bottom: 0px; }--></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p><span style="font-size:12pt">Hi All,</span><br>
</p>
<p><br>
</p>
<p>In the IRC meeting yesterday, I brought up this new blueprint I opened.<br>
</p>
<p><br>
</p>
<p><a href="https://blueprints.launchpad.net/magnum/+spec/pluggable-keystone-model">https://blueprints.launchpad.net/magnum/+spec/pluggable-keystone-model</a><br>
</p>
<p><br>
</p>
<p>The goal of this blueprint is to allow magnum operators to integrate with their version of keystone easily with downstream patches.<br>
</p>
<p><br>
</p>
<p>The goal is <strong>NOT</strong> to implement support for keystone version 2 upstream, but to make it easy for operators to integrate with V2 if they need to.<br>
</p>
<p><br>
</p>
<p>Most of the work required for this is already done in this patch.<br>
</p>
<p><br>
</p>
<p><a href="https://review.openstack.org/#/c/218699">https://review.openstack.org/#/c/218699</a><br>
</p>
<p><br>
</p>
<p>However, we didn't want to address this change in the same review.<br>
</p>
<p><br>
</p>
<p>We just need to refactor the code a little further and isolate all version specific keystone code to one file.<br>
</p>
<p><br>
</p>
<p>See my comments in the following review for details on what this change entails.<br>
</p>
<p><br>
</p>
<p><a href="https://review.openstack.org/#/c/218699/5/magnum/common/clients.py">https://review.openstack.org/#/c/218699/5/magnum/common/clients.py</a><br>
</p>
<p><br>
</p>
<p><a href="https://review.openstack.org/#/c/218699/5/magnum/common/keystone.py">https://review.openstack.org/#/c/218699/5/magnum/common/keystone.py</a><br>
</p>
<p><br>
</p>
<p>Thanks,<br>
</p>
<p>Murali<br>
</p>
</body>
</html>