yahoo-eng-team team mailing list archive

[yangjianfeng <1881085@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The neutron API support add some routes which have same destioation and defferent gateways to a router. In other words, the below command can be executed successfully:
"openstack router set 79cf5d9d-c4ab-45d7-8959-30963cba2ea4 --route destination=10.30.30.35/32,gateway=10.30.30.2 --route destination=10.30.30.35/32,gateway=10.30.30.3"
This look like the neutron support add ECMP route to l3 router.

But, in agent side these routes don't be processed correctly. The qrouter-79cf5d9d-c4ab-45d7-8959-30963cba2ea4 namespace's route entity as below:
10.30.30.35 via 10.30.30.3 dev qr-905cfb1e-43 
10.30.30.35 via 10.30.30.2 dev qr-905cfb1e-43
or (The second route entity override the first one. Aout why has the difference, I haven't found the reason yet.)
10.30.30.35 via 10.30.30.2 dev qr-905cfb1e-43
But, I think the route entity shoule be like below:
10.30.30.35 
	nexthop via 10.30.30.2 dev qr-905cfb1e-43 weight 1 
	nexthop via 10.30.30.3 dev qr-905cfb1e-43 weight 1

By the way, The neutron-specs has a patch [1] that propose to extend neutron API to implement a similar feature. But I don't think the neutron API need to be extended, as my comment in [2].
[1] https://review.opendev.org/#/c/729532/
[2] https://review.opendev.org/#/c/723864/4/specs/version1.1/alternative-active-active-l3-distributor.rst@45

** Affects: neutron
     Importance: Undecided
         Status: Invalid

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

Title:
  About l3 router support ECMP

Status in neutron:
  Invalid

Bug description:
  The neutron API support add some routes which have same destioation and defferent gateways to a router. In other words, the below command can be executed successfully:
  "openstack router set 79cf5d9d-c4ab-45d7-8959-30963cba2ea4 --route destination=10.30.30.35/32,gateway=10.30.30.2 --route destination=10.30.30.35/32,gateway=10.30.30.3"
  This look like the neutron support add ECMP route to l3 router.

  But, in agent side these routes don't be processed correctly. The qrouter-79cf5d9d-c4ab-45d7-8959-30963cba2ea4 namespace's route entity as below:
  10.30.30.35 via 10.30.30.3 dev qr-905cfb1e-43 
  10.30.30.35 via 10.30.30.2 dev qr-905cfb1e-43
  or (The second route entity override the first one. Aout why has the difference, I haven't found the reason yet.)
  10.30.30.35 via 10.30.30.2 dev qr-905cfb1e-43
  But, I think the route entity shoule be like below:
  10.30.30.35 
  	nexthop via 10.30.30.2 dev qr-905cfb1e-43 weight 1 
  	nexthop via 10.30.30.3 dev qr-905cfb1e-43 weight 1

  By the way, The neutron-specs has a patch [1] that propose to extend neutron API to implement a similar feature. But I don't think the neutron API need to be extended, as my comment in [2].
  [1] https://review.opendev.org/#/c/729532/
  [2] https://review.opendev.org/#/c/723864/4/specs/version1.1/alternative-active-active-l3-distributor.rst@45

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