Re: [openstack-dev] [python-neutronclient][neutron] sub-project client extensions

2015-08-05 Thread Fawad Khaliq
-- *From:* Fawad Khaliq fa...@plumgrid.com *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

Re: [openstack-dev] [python-neutronclient][neutron] sub-project client extensions

2015-08-05 Thread Mohankumar N
: [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

Re: [openstack-dev] [python-neutronclient][neutron] sub-project client extensions

2015-08-05 Thread Fawad Khaliq
://review.openstack.org/#/c/204963/ Thanks., Mohankumar.N *From:* Fawad Khaliq [mailto:fa...@plumgrid.com] *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

[openstack-dev] [python-neutronclient][neutron] sub-project client extensions

2015-08-04 Thread Fawad Khaliq
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

Re: [openstack-dev] [python-neutronclient][neutron] sub-project client extensions

2015-08-04 Thread Amir Sadoughi
From: Fawad Khaliq fa...@plumgrid.com 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