Re: [openstack-dev] [neutron][neutron-lib]Service function defintion files

2018-01-05 Thread Mooney, Sean K
From: CARVER, PAUL [mailto:pc2...@att.com] Sent: Thursday, December 28, 2017 2:57 PM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [neutron][neutron-lib]Service function defintion files It was a

Re: [openstack-dev] [neutron][neutron-lib]Service function defintion files

2017-12-29 Thread Armando M.
On 29 December 2017 at 11:00, Ian Wells wrote: > On 28 December 2017 at 06:57, CARVER, PAUL wrote: > >> It was a gating criteria for stadium status. The idea was that the for a >> stadium project the neutron team would have review authority over the API

Re: [openstack-dev] [neutron][neutron-lib]Service function defintion files

2017-12-29 Thread Henry Fourie
(not for usage questions) Subject: Re: [openstack-dev] [neutron][neutron-lib]Service function defintion files I think it sort of was intentional, although probably not the primary focus. I don’t remember if it is a stadium requirement or merely a suggestion, but I believe it is strongly

Re: [openstack-dev] [neutron][neutron-lib]Service function defintion files

2017-12-29 Thread CARVER, PAUL
nStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [neutron][neutron-lib]Service function defintion files On 28 December 2017 at 06:57, CARVER, PAUL <pc2...@att.com<mailto:pc2...@att.com>> wrote: It was a gat

Re: [openstack-dev] [neutron][neutron-lib]Service function defintion files

2017-12-29 Thread Ian Wells
On 28 December 2017 at 06:57, CARVER, PAUL wrote: > It was a gating criteria for stadium status. The idea was that the for a > stadium project the neutron team would have review authority over the API > but wouldn't necessarily review or be overly familiar with the >

Re: [openstack-dev] [neutron][neutron-lib]Service function defintion files

2017-12-28 Thread Armando M.
On 27 December 2017 at 18:56, Ian Wells wrote: > Hey, > > Can someone explain how the API definition files for several service > plugins ended up in neutron-lib? I can see that they've been moved there > from the plugins themselves (e.g. networking-bgpvpn has >

Re: [openstack-dev] [neutron][neutron-lib]Service function defintion files

2017-12-28 Thread CARVER, PAUL
GMT-05:00) To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [neutron][neutron-lib]Service function defintion files Hey, Can someone explain how the API definition files for several service plugins ended up in neutron-lib? I can see that

[openstack-dev] [neutron][neutron-lib]Service function defintion files

2017-12-27 Thread Ian Wells
Hey, Can someone explain how the API definition files for several service plugins ended up in neutron-lib? I can see that they've been moved there from the plugins themselves (e.g. networking-bgpvpn has