Open Stack

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 the ProcessMonitor implemented in the l3_agent and dhcp_agent at least.

I believe the work is ready (I need to check the radvd respawn in the l3 agent).
The ProcessMonitor class is already merged.

Best regards,
Miguel Ángel.

----- Original Message -----
> On Wed, Sep 3, 2014 at 10:19 AM, Mark McClain <mark at mcclain.xyz> wrote:
> >
> > On Sep 3, 2014, at 11:04 AM, Brian Haley <brian.haley at hp.com> 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 BPs from Juno which
> >>> did not make the merge window. I'll also be putting temporary -2s in
> >>> the patches to ensure they don't slip in as well. I'm looking at FFEs
> >>> for the high priority items which are close but didn't quite make it:
> >>>
> >>> https://blueprints.launchpad.net/neutron/+spec/l3-high-availability
> >>> https://blueprints.launchpad.net/neutron/+spec/add-ipset-to-security
> >>> https://blueprints.launchpad.net/neutron/+spec/security-group-rules-for-devices-rpc-call-refactor
> >>
> >> I guess I'll be the first to ask for an exception for a Medium since the
> >> code
> >> was originally completed in Icehouse:
> >>
> >> https://blueprints.launchpad.net/neutron/+spec/l3-metering-mgnt-ext
> >>
> >> The neutronclient-side code was committed in January, and the neutron
> >> side,
> >> https://review.openstack.org/#/c/70090 has had mostly positive reviews
> >> since
> >> then.  I've really just spent the last week re-basing it as things moved
> >> along.
> >>
> >
> > +1 for FFE.  I think this is good community that fell through the cracks.
> >
> I agree, and I've marked it as RC1 now. I'll sort through these with
> ttx on Friday and get more clarity on it's official status.
> 
> Thanks,
> Kyle
> 
> > mark
> >
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>