yahoo-eng-team team mailing list archive

[Armando Migliaccio <1528235@xxxxxxxxxxxxxxxxxx>]

@Assaf: so you concur with me?

** Changed in: neutron
       Status: Triaged => Won't Fix

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

Title:
  [RFE]Add weight to l3 agent

Status in neutron:
  Won't Fix

Bug description:
  [Existing problem]
  Currently, neutron will treat all l3 agent as the same. The default LeastRoutersScheduler will chose l3 agent, based on the load of l3 agents. But the hosts of l3 agents may be different. Some hosts may have better CPU, larger memory and better network bandwidth. Admins/Operators may want the host with higher performance to take more load.

  [Proposal]
  Add a configuration to l3_agent.ini to represent the weight of l3 agent. Admins/Operators can set higher weight to the l3 agent with higher performance. The l3 agent with higher weight will have higher chance to be selected by the L3Scheduler.

  A simple algorithm of weight is to be linear correlation with performance of hosts. And Admins/Operators will need to estimate the performance of hosts. For example, performance of host A is 10 times than host B. Admins/Operators then set weight of l3 agent in host A to 10, and l3 agent in host B to 1. L3Scheduler will calculate load of l3 agents with such comparison:
  X/10 ~ Y/1(X=routers in l3 agent A; Y=routers in l3 agent B)

  [Benefits]
  Neutron can provide a better scheduling by leveraging the difference of performance of l3 agents' hosts

  [What is the enhancement?]
  Configuration file changes.
  Code change in the L3 scheduler.

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