← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1828605] [NEW] [l3][scale issue] unrestricted hosting routers in network node increase service operating pressure

 

Public bug reported:

[l3][scale issue] unrestricted hosting routers in network node increase
service operating pressure


Related problem was reported here: https://bugs.launchpad.net/neutron/+bug/1828494
These issues have same background, unlimited router creation for entire cluster,
"""
Every tenant may create free routers for doing nothing. But neutron will create many resource for it, especially the HA scenario, there will be namespaces, keepalived processes, and monitor processes. It will absolutely increase the failure risk, especially for agent restart.
"""

So this bug is aimming to add config or mechanism which will add some
conditions for l3-agent to indicate whether to create resources in
network nodes. For now, the condition is whether there are resources
under the router, aka if there is no compute (virtual machind or
baremetal) resource under the router, the l3-agent in network node will
host nothing for this router.

** 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/1828605

Title:
  [l3][scale issue] unrestricted hosting routers in network node
  increase service operating pressure

Status in neutron:
  New

Bug description:
  [l3][scale issue] unrestricted hosting routers in network node
  increase service operating pressure

  
  Related problem was reported here: https://bugs.launchpad.net/neutron/+bug/1828494
  These issues have same background, unlimited router creation for entire cluster,
  """
  Every tenant may create free routers for doing nothing. But neutron will create many resource for it, especially the HA scenario, there will be namespaces, keepalived processes, and monitor processes. It will absolutely increase the failure risk, especially for agent restart.
  """

  So this bug is aimming to add config or mechanism which will add some
  conditions for l3-agent to indicate whether to create resources in
  network nodes. For now, the condition is whether there are resources
  under the router, aka if there is no compute (virtual machind or
  baremetal) resource under the router, the l3-agent in network node
  will host nothing for this router.

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