yahoo-eng-team team mailing list archive

[Rodolfo Alonso <1593788@xxxxxxxxxxxxxxxxxx>]

Bug closed due to lack of activity, please feel free to reopen if
needed.

** Changed in: neutron
       Status: In Progress => 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/1593788

Title:
  Without using AZ aware Scheduler, dhcp can recognize AZ, while l3
  can't

Status in neutron:
  Won't Fix

Bug description:
  I have a env with 3 network nodes.

  The dhcp scheduler is configured as:
  network_scheduler_driver = neutron.scheduler.dhcp_agent_scheduler.WeightScheduler
  The l3 scheduler is configured as:
  router_scheduler_driver = neutron.scheduler.l3_agent_scheduler.LeastRoutersScheduler

  I create 51 legacy routers use the following command:

  neutron router-create router${i} --availability-zone-hint nova2
  neutron router-gateway-set router${i} public

  After router creation, check the routers in L3 agent, the resut is recorded at:
  http://paste.openstack.org/show/516896/
  The routers are spawned evenly in the 3 L3 agents.

  
  I create 51 network use the following command:

  neutron net-create net${i} --availability-zone-hint nova2
  neutron subnet-create net${i} ${i}.0.0.0/24

  After network creation, check the networks in dhcp agent, the result is recorded at:
  http://paste.openstack.org/show/516897/
  The networks are only spawned in nova2.

  
  Expected result:
  DHCP and L3 should act the same. I would prefer to let l3 be AZ aware even if the AZ scheduler is not used. The AZ aware scheduler will share load among AZs. For normal scheduler, the AZ should work as constraint for scheduling.

  This might be fixed during the work at bug 1509046

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