yahoo-eng-team team mailing list archive

[Armando Migliaccio <1450067@xxxxxxxxxxxxxxxxxx>]

Technically speaking we could do as Assaf suggested on comment #2, but
that makes my teeth grind a bit.

Having said that, I think this issue is really collateral damage, and
there is a much, much larger problem at play here: what happens if
another mech driver wants to support DVR, but in a fundamentally
different way? We're stuck with a pervasive DVR logic within the plugin
itself that makes certain architectural assumptions, like the presence
of agents (L2 and L3). This makes the work incredibly difficult, if not
virtually impossible.

I have been toying with some ideas in the context of the L2/L3
decoupling and the security groups support for agentless mech drivers,
but oh boy that's hard!

I really don't see any value in addressing this particular issue (even
though it could be considered a decent cosmetic stop-gap fix), but I'd
rather nail the larger objective of moving aways from extensions in the
context of [1], and trying to disentangle control from management plane
in the context of [2].

[1] https://review.openstack.org/#/c/136760/
[2] https://review.openstack.org/#/c/176501/


** Changed in: neutron
       Status: New => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1450067

Title:
  Server with ML2 & L3 service plugin exposes dvr extension even if OVS
  agent is unused

Status in OpenStack Neutron (virtual network service):
  Opinion

Bug description:
  In a deployment using the L3 service plugin, the DVR extension is
  always declared as available, this is even if the ML2 OVS mech driver
  is not configured. Deployments could be using the LB mech driver or
  others. Not only is the extension declared, DVR router creation is not
  blocked. We should not rely only on documentation, but additionally
  provide expected behavior (Fail gracefully, not expose the extension).

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1450067/+subscriptions