You mean outside of the LDT filing an RFE bug with neutron to get segmented/routed network support added to neutron complete with an etherpad of all the ways we are using that at our companies and our use cases [1] . Or where we (GoDaddy) came to the neutron Mid-cycle in Fort Collins to further talk about said use case as well as to put feelers out for ip-usages-extension. Which was commited to Neutron in the Mitaka release [2]. These are just the things that I was am aware of and have been involved in neutron alone in the past 6 months, I am sure there are many more. [1] - https://etherpad.openstack.org/p/Network_Segmentation_Usecases & https://bugs.launchpad.net/neutron/+bug/1458890 [2] - https://github.com/openstack/neutron/commit/2f741ca5f9545c388270ddab774e9e030b006d8a ___________________________________________________________________ Kris Lindgren Senior Linux Systems Engineer GoDaddy On 4/11/16, 9:11 AM, "Sean M. Collins" <sean at coreitpro.com> wrote: >To be blunt: Are we ensuring that all this work that people are >capturing in these working groups is actually getting updated and >communicated to the developers? > >As I become more involved with rolling upgrades, I will try and attend >meetings and be available from the WG side, but I don't believe I've >ever seen someone from the WG side come over to Neutron and say "We need >XYZ and here's a link to what we've captured in our repo to explain what >we mean" > >But then again I'm not on the neutron-drivers team or a core. > >Anyway, I updated what I've been involved with in the Mitaka cycle, when >it comes to Neutron and upgrades (https://review.openstack.org/304181) > >-- >Sean M. Collins > >_______________________________________________ >OpenStack-operators mailing list >OpenStack-operators at lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators