yahoo-eng-team team mailing list archive

[LIU Yulong <1891448@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

For now if the L3 agent change the agent mode (dvr to dvr_no_external,
or dvr_no_external to dvr), the floating IP traffic will not recover.
There is a mannully workflow to achive the transition, but it will need
to shutdown the router during the transition. The backwards is obviously
the floating IP under the router will be shutdown for a bit long time
(admin state down/up). And the floating IPs not related to this compute
host will be influenced as well.

So, IMO, neutron should support such agent mode change for varied cloud
deployments.

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  [RFE] l3 agent mode transition between dvr and dvr_no_external

Status in neutron:
  New

Bug description:
  For now if the L3 agent change the agent mode (dvr to dvr_no_external,
  or dvr_no_external to dvr), the floating IP traffic will not recover.
  There is a mannully workflow to achive the transition, but it will
  need to shutdown the router during the transition. The backwards is
  obviously the floating IP under the router will be shutdown for a bit
  long time (admin state down/up). And the floating IPs not related to
  this compute host will be influenced as well.

  So, IMO, neutron should support such agent mode change for varied
  cloud deployments.

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