[openstack-dev] [Neutron] Etherpad from the Ops Meetup

Doug Wiegley dougwig at parksidesoftware.com
Wed Aug 19 21:49:39 UTC 2015


To expand on that a bit, I think the DVR complaints were vague because of the simple fact that the overwhelming majority were or wanted to run linuxbridge, not OVS, so DVR was a theoretical thing for them.

doug

> On Aug 19, 2015, at 2:21 PM, Salvatore Orlando <salv.orlando at gmail.com> wrote:
> 
> The etherpad contains some complaints around DVR implementation that might deserve furhter exploration.
> However, as pointed out by Jay, the comments made leave very little room for actionable items.
> It would be great if the author(s) could fill in with more details.
> 
> Salvatore
> 
> On 19 August 2015 at 23:11, Ryan Moats <rmoats at us.ibm.com <mailto:rmoats at us.ibm.com>> wrote:
> One thing came up during lunch was including unit and functional testing of dual stack in the check and gate queues - I was regaled over lunch with one operator's experiences in trying to run Neutron on a dual stack system.
> 
> Ryan Moats (regXboi)
> 
> Edgar Magana <edgar.magana at workday.com <mailto:edgar.magana at workday.com>> wrote on 08/19/2015 03:43:44 PM:
> 
> > From: Edgar Magana <edgar.magana at workday.com <mailto:edgar.magana at workday.com>>
> > To: "OpenStack Development Mailing List (not for usage questions)" 
> > <openstack-dev at lists.openstack.org <mailto:openstack-dev at lists.openstack.org>>
> > Date: 08/19/2015 03:44 PM
> 
> 
> > Subject: Re: [openstack-dev] [Neutron] Etherpad from the Ops Meetup
> > 
> > Actually, there were very few requirements collected. So, your 
> > summary is correct.
> > 
> > I feel that this time we did not get a lot of input s we got during 
> > the Ops meet-up in Philadelphia.
> > 
> > I also recommend to read the burning issues ether pads, there are 
> > few suggestions on the networking side. Actually, I believe 
> > Operators has expressed in this session some good feedback that they
> > probaly did not want to repeat during the networking section.
> > 
> > https://etherpad.openstack.org/p/PAO-ops-burning-issues <https://etherpad.openstack.org/p/PAO-ops-burning-issues>
> > 
> > Cheers,
> > 
> > Edgar
> > 
> > From: Assaf Muller
> > Reply-To: "OpenStack Development Mailing List (not for usage questions)"
> > Date: Wednesday, August 19, 2015 at 1:34 PM
> > To: "OpenStack Development Mailing List (not for usage questions)"
> > Subject: Re: [openstack-dev] [Neutron] Etherpad from the Ops Meetup
> > 
> > On Wed, Aug 19, 2015 at 2:52 PM, Edgar Magana <edgar.magana at workday.com <mailto:edgar.magana at workday.com>
> > > wrote:
> > Folks,
> > 
> > I just want to share with you the feedback collected today during 
> > the networking session on Ops Meet-up:
> > https://etherpad.openstack.org/p/PAO-ops-network-model <https://etherpad.openstack.org/p/PAO-ops-network-model>
> > 
> > Special thanks to Ryan and Doug for helping on some questions.
> > 
> > The only action items for Neutron developers that I can spot are:
> > 1. Linux bridge + DVR / multi host
> > 2. Prevent data loss when restarting the OVS agent (The patch [1] is
> > very close to merge anyway, nothing more to do here)
> > 3. Work as described by [2] (Big deployers team)
> > The rest is either polling (Who uses what feature / plugin / etc) or
> > generic comments with no actionable bugs or RFEs.
> > Did I miss anything?
> > 
> > [1] https://review.openstack.org/#/c/182920/ <https://review.openstack.org/#/c/182920/>
> > [2] https://etherpad.openstack.org/p/Network_Segmentation_Usecases <https://etherpad.openstack.org/p/Network_Segmentation_Usecases>
> > 
> > Cheers,
> > 
> > Edgar
> > 
> > __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe <http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe>
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> 
> > __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe <http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe>
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> 
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe <http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150819/10cbb3c7/attachment.html>


More information about the OpenStack-dev mailing list