<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: 12px; font-family: Calibri, sans-serif;">
<div>Just starting this discussion…</div>
<div><br>
</div>
<div>This is in reference to https://blueprints.launchpad.net/python-neutronclient/+spec/pluggable-neutronclient-auth</div>
<div><br>
</div>
<div>Originally the blueprint was for python-neutronclient only, but pluggable auth is a wide-reaching issue. With OSC/SDK on the horizon (however far), we should probably begin the discussion of how to best do this (if it hasn't been done).</div>
<div><br>
</div>
<div>A request: We have an immediate need to add pluggable auth to the python-neutronclient, modeled after python-novaclient's pluggable auth system, to maintain a consistent workflow for our users. After the discussion in the neutron-drivers meeting (<a href="http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-02-18-15.31.log.html">http://eavesdrop.openstack.org/meetings/neutron_drivers/2015/neutron_drivers.2015-02-18-15.31.log.html</a>)
it is clear that python-neutronclient will survive for Kilo +12 months, at least. During that timeframe we'd like to have pluggable auth supported so we can bridge that gap. Beyond that immediate need, we are dedicated to making OSC/SDK the way to go in the
future, and will gladly assist in adding said features.</div>
<div><br>
</div>
<div>We have a solution for our immediate solution but that may not apply to OSC/SDK. So my questions are:</div>
<div><br>
</div>
<ul>
<li>Would you benefit from pluggable auth?</li><li>What are you looking for in auth?</li><li>Would you benefit from the python-neutronclient getting nova's auth capabilities?</li></ul>
<div>Thank you for your time!</div>
<div><br>
</div>
<div>- Justin (roaet)</div>
<div><br>
</div>
<div><br>
</div>
</body>
</html>