← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1526175] Re: ha router schedule to dvr agent in compute node

 

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
       Status: Incomplete => Expired

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

Title:
  ha router schedule to dvr agent in compute node

Status in neutron:
  Expired

Bug description:
  I use my conpany's environment to test the neutron DVR router.

  At first, the environment use 2 network node provide L3-ha-router, in
  neutron.conf :

  l3_ha = True
  max_l3_agents_per_router = 3
  min_l3_agents_per_router = 2

  then I change the neutron.conf to:

  l3_ha = False
  router_distributed = True
  max_l3_agents_per_router = 3
  min_l3_agents_per_router = 2

  and run dvr mode l3-agent on compute nodes, now the strange things happened, All ha-router 
  bind to this compute node.
  If i create a new ha-router ,and use "neutron l3-agent-list-hosting-router" command to watch binding

  root@controller:~# neutron l3-agent-list-hosting-router 73a5308f-dd1e-4c0e-8ccf-b9e4d2a82c5e
  +--------------------------------------+----------+----------------+-------+----------+
  | id                                   | host     | admin_state_up | alive | ha_state |
  +--------------------------------------+----------+----------------+-------+----------+
  | 0f3f65bd-9349-4f9a-af2c-7872a4fddd1f | network2 | True           | :-)   | standby  |
  | b174f741-3a41-45ed-bae0-e00ef4c1b1f9 | network1 | True           | :-)   | standby  |
  +--------------------------------------+----------+----------------+-------+----------+
  root@controller:~# neutron l3-agent-list-hosting-router 73a5308f-dd1e-4c0e-8ccf-b9e4d2a82c5e
  +--------------------------------------+----------+----------------+-------+----------+
  | id                                   | host     | admin_state_up | alive | ha_state |
  +--------------------------------------+----------+----------------+-------+----------+
  | 95f0c274-95ec-44c4-a6e7-f7e6de4b6e25 | compute3 | True           | :-)   | standby  |
  | 0f3f65bd-9349-4f9a-af2c-7872a4fddd1f | network2 | True           | :-)   | active   |
  | b174f741-3a41-45ed-bae0-e00ef4c1b1f9 | network1 | True           | :-)   | standby  |
  +--------------------------------------+----------+----------------+-------+----------+

  It will first bind to network1 and network2,then bind to compute3.
  I guess the reason is when dvr mode l3-agent start sync_router , neutron bind the ha-router to compute3

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


References