<div dir="ltr">Thanks Amir. This will be a step forward in that direction<div><br></div><div>Extending my question to Henry and Kyle, as they are driving the decomposition phase II.</div><div><br></div><div>Hello Henry/Kyle,</div><div><br></div><div>With devref [1] for Neutron sub-projects getting in and sub-projects owners working towards completing the phase II, the Neutron tree decomposition is excellently described, however, the python-neutron client side of changes are not completely clear and seem optional. So what you guys suggest for client implementation of vendor specific extensions? Should they be out of python-neutronclient tree or be in tree? I would prefer former as its much cleaner and aligns better with phase II. If former is the case, can we please enhance the devref to capture how the process will work for python-neutronclient.</div><div><br></div><div class="gmail_extra">Thanks,<br clear="all"><div><div><div dir="ltr">Fawad Khaliq<div><br></div></div></div></div>
<br><div class="gmail_quote">On Tue, Aug 4, 2015 at 5:51 PM, Amir Sadoughi <span dir="ltr"><<a href="mailto:amir.sadoughi@rackspace.com" target="_blank">amir.sadoughi@rackspace.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr" style="font-size:12pt;color:#000000;background-color:#ffffff;font-family:Arial,Helvetica,sans-serif">
<p>I started down the path of making a python-neutronclient extension, but got stuck on the lack of support for child resource extensions as described here <a href="https://bugs.launchpad.net/python-neutronclient/+bug/1446428" target="_blank">https://bugs.launchpad.net/python-neutronclient/+bug/1446428</a>.
I submitted a bugfix here <a href="https://review.openstack.org/#/c/202597/" target="_blank">https://review.openstack.org/#/c/202597/</a>. <br>
</p>
<p><br>
</p>
<p>Amir<br>
</p>
<p><br>
</p>
<div style="color:rgb(33,33,33)">
<hr style="display:inline-block;width:98%">
<div dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Fawad Khaliq <<a href="mailto:fawad@plumgrid.com" target="_blank">fawad@plumgrid.com</a>><br>
<b>Sent:</b> Tuesday, August 4, 2015 6:10 AM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> [openstack-dev] [python-neutronclient][neutron] sub-project client extensions</font>
<div> </div>
</div><div><div>
<div>
<div dir="ltr">
<div>Folks,</div>
<div><br>
</div>
<div>In networking-plumgrid project, we intend to implement client side for some of the vendor specific extensions. Looking at the current implementation for client side for some vendors, I see the code is part of python-neutronclient tree [1]. I do see this
change [2] talking about a way to load extensions through entry points, however, I could not find any example extension module.</div>
<div><br>
</div>
<div>Has anyone gone through the route of implementing out of tree extensions for Neutron client, which extend python-neutronclient shell and load at run/install time? With decomposition phase II, it makes sense to keep the client side in the respective projects
as well.</div>
<div><br>
</div>
<div>[1] <a href="https://github.com/openstack/python-neutronclient/tree/master/neutronclient/neutron/v2_0" target="_blank">https://github.com/openstack/python-neutronclient/tree/master/neutronclient/neutron/v2_0</a></div>
<div>[2] <a href="https://review.openstack.org/#/c/148318/16" target="_blank">https://review.openstack.org/#/c/148318/16</a></div>
<div><br>
</div>
<div>Thanks,</div>
<div>
<div>
<div dir="ltr">Fawad Khaliq
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div></div></div>
</div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>