yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1828494] [NEW] [RFE][L3] l3-agent should have its capacity

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: LIU Yulong <yulong@xxxxxxxxxxxxx>
Date: Fri, 10 May 2019 02:05:45 -0000
Reply-to: Bug 1828494 <1828494@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Public bug reported:

Recently we meet some scale issue about L3-agent. According to what I'm
informed, most cloud service provider does not charge for the neutron
virtual router. This can become a headach for the operators. 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 RFE is aimming to add a scheduling mechanism, and for l3-agent,
it will collect and report some resource usage, for instance available
bandiwidth. So during the router scheduler process, if there is no more
available, the number of routers can be under a controlled range.

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

Title:
  [RFE][L3] l3-agent should have its capacity

Status in neutron:
  New

Bug description:
  Recently we meet some scale issue about L3-agent. According to what
  I'm informed, most cloud service provider does not charge for the
  neutron virtual router. This can become a headach for the operators.
  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 RFE is aimming to add a scheduling mechanism, and for
  l3-agent, it will collect and report some resource usage, for instance
  available bandiwidth. So during the router scheduler process, if there
  is no more available, the number of routers can be under a controlled
  range.

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