Comment 4 for bug 1450625

Cathy, both bug 1450617 and bug 1450625 make a lot of sense.

Bear in mind that the RFE bugs are not strictly necessary since your spec proposal predates the change in the feature submission process.

I think that the scope of this feature is large enough to have this be developed in autonomy, without too much oversight from the Neutron drivers team, and without too much burden due to process.

What I mean by this is that we should consider starting a new project (but still part of the Neutron tent), where we can iterate and experiment faster than we could in the Neutron core. This means setting up a new repo, a new weekly meeting, new team, etc.

I can help you setting up all of this, if you are a bit lost.

The amount of work that the drivers team is asked to review has become so vast these days, that having smaller and more focused teams collaborate in isolation is the most sensible way to achieve progress in a timely manner.

Having said that, we'd want SFC to plug back into the Neutron core where it makes sense, and for the missing pieces that would be required for tighter integration with the core, we can follow the RFE process defined in [1]. The drivers team should have enough capacity to provide input and guidance on RFE's of a much smaller scope.

If you have any question, please feel free to reach out to us on #openstack-neutron or openstack-dev ML [neutron].

Thanks,
Armando

[1] https://github.com/openstack/neutron/blob/master/doc/source/policies/blueprints.rst