Hi Fawad, If I understood your question correctly , here some ways to do
[1] you want to extend your client side packages . you can include entry point in “setup.cfg” https://review.openstack.org/#/c/200065/1/setup.cfg [2] To extend python-neutronclient base packages , you can add in “requirement.txt” https://review.openstack.org/#/c/166564/3/requirements.txt https://review.openstack.org/#/c/204963/ Thanks., Mohankumar.N From: Fawad Khaliq [mailto:[email protected]] Sent: 2015年8月5日 14:23 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [python-neutronclient][neutron] sub-project client extensions Thanks Amir. This will be a step forward in that direction Extending my question to Henry and Kyle, as they are driving the decomposition phase II. Hello Henry/Kyle, 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. Thanks, Fawad Khaliq On Tue, Aug 4, 2015 at 5:51 PM, Amir Sadoughi <[email protected]<mailto:[email protected]>> wrote: 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 https://bugs.launchpad.net/python-neutronclient/+bug/1446428. I submitted a bugfix here https://review.openstack.org/#/c/202597/. Amir ________________________________ From: Fawad Khaliq <[email protected]<mailto:[email protected]>> Sent: Tuesday, August 4, 2015 6:10 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [python-neutronclient][neutron] sub-project client extensions Folks, 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. 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. [1] https://github.com/openstack/python-neutronclient/tree/master/neutronclient/neutron/v2_0 [2] https://review.openstack.org/#/c/148318/16 Thanks, Fawad Khaliq __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe<http://[email protected]?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
