Re: [openstack-dev] [neutron] Status of Neutron at Juno-3

2014-09-08 Thread loy wolfe
Is TOR based vxlan really a common interest to most of the people, and should a BP be taken care now with its designed use case of 3rd TOR backend integration? On Fri, Sep 5, 2014 at 10:54 PM, Robert Kukura wrote: > Kyle, > > Please consider an FFE for https://blueprints.launchpad. > net/neutro

Re: [openstack-dev] [neutron] Status of Neutron at Juno-3

2014-09-05 Thread Kyle Mestery
On Fri, Sep 5, 2014 at 9:54 AM, Robert Kukura wrote: > Kyle, > > Please consider an FFE for > https://blueprints.launchpad.net/neutron/+spec/ml2-hierarchical-port-binding. > This was discussed extensively at Wednesday's ML2 meeting, where the > consensus was that it would be valuable to get this i

Re: [openstack-dev] [neutron] Status of Neutron at Juno-3

2014-09-05 Thread Robert Kukura
Kyle, Please consider an FFE for https://blueprints.launchpad.net/neutron/+spec/ml2-hierarchical-port-binding. This was discussed extensively at Wednesday's ML2 meeting, where the consensus was that it would be valuable to get this into Juno if possible. The patches have had core reviews from

Re: [openstack-dev] [neutron] Status of Neutron at Juno-3

2014-09-04 Thread Kyle Mestery
On Thu, Sep 4, 2014 at 3:38 AM, Miguel Angel Ajo Pelayo wrote: > > I didn't know that we could ask for FFE, so I'd like to ask (if > yet in time) for: > > https://blueprints.launchpad.net/neutron/+spec/agent-child-processes-status > > https://review.openstack.org/#/q/status:open+project:openstack/

Re: [openstack-dev] [neutron] Status of Neutron at Juno-3

2014-09-04 Thread Miguel Angel Ajo Pelayo
I didn't know that we could ask for FFE, so I'd like to ask (if yet in time) for: https://blueprints.launchpad.net/neutron/+spec/agent-child-processes-status https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/agent-child-processes-status,n,z To get th

Re: [openstack-dev] [neutron] Status of Neutron at Juno-3

2014-09-03 Thread Kyle Mestery
On Wed, Sep 3, 2014 at 10:19 AM, Mark McClain wrote: > > On Sep 3, 2014, at 11:04 AM, Brian Haley wrote: > >> On 09/03/2014 08:17 AM, Kyle Mestery wrote: >>> Given how deep the merge queue is (146 currently), we've effectively >>> reached feature freeze in Neutron now (likely other projects as we

Re: [openstack-dev] [neutron] Status of Neutron at Juno-3

2014-09-03 Thread Mark McClain
On Sep 3, 2014, at 11:04 AM, Brian Haley wrote: > On 09/03/2014 08:17 AM, Kyle Mestery wrote: >> Given how deep the merge queue is (146 currently), we've effectively >> reached feature freeze in Neutron now (likely other projects as well). >> So this morning I'm going to go through and remove BP

Re: [openstack-dev] [neutron] Status of Neutron at Juno-3

2014-09-03 Thread Brian Haley
On 09/03/2014 08:17 AM, Kyle Mestery wrote: > Given how deep the merge queue is (146 currently), we've effectively > reached feature freeze in Neutron now (likely other projects as well). > So this morning I'm going to go through and remove BPs from Juno which > did not make the merge window. I'll

[openstack-dev] [neutron] Status of Neutron at Juno-3

2014-09-03 Thread Kyle Mestery
Given how deep the merge queue is (146 currently), we've effectively reached feature freeze in Neutron now (likely other projects as well). So this morning I'm going to go through and remove BPs from Juno which did not make the merge window. I'll also be putting temporary -2s in the patches to ensu