yahoo-eng-team team mailing list archive

[LIU Yulong <1934948@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In the L3 meeting 2021-06-30, I mentioned this topic.
https://meetings.opendev.org/meetings/neutron_l3/2021/neutron_l3.2021-06-30-14.00.log.html#l-28

Current L3 resources (floating IPs, router interface, router external gateway) processing procedure is a bit heavy, and sometimes waste of times. For instance, if one floating IP is bind to a port under one router, the steps are:
1. floating IP updated
2. notify L3 agent that this floating IPs router is updated
3. L3 agent sync the router info
4. L3 agent reprocess all router related resources

The alternative is we can use resource cache for router related resources, then the procedure for floating IP update can be changed to:
1. floating IP updated.
2. OVO object update event send out.
3. L3 agents which has the related router resident will do the processing of floating IP only, no sync of full router info, no processing of all router resources again!

This can be a huge performace improvement for L3 related resources
processing.

Thoughts?

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

Title:
  [RFE] refactor of L3 resources update procedure

Status in neutron:
  New

Bug description:
  In the L3 meeting 2021-06-30, I mentioned this topic.
  https://meetings.opendev.org/meetings/neutron_l3/2021/neutron_l3.2021-06-30-14.00.log.html#l-28

  Current L3 resources (floating IPs, router interface, router external gateway) processing procedure is a bit heavy, and sometimes waste of times. For instance, if one floating IP is bind to a port under one router, the steps are:
  1. floating IP updated
  2. notify L3 agent that this floating IPs router is updated
  3. L3 agent sync the router info
  4. L3 agent reprocess all router related resources

  The alternative is we can use resource cache for router related resources, then the procedure for floating IP update can be changed to:
  1. floating IP updated.
  2. OVO object update event send out.
  3. L3 agents which has the related router resident will do the processing of floating IP only, no sync of full router info, no processing of all router resources again!

  This can be a huge performace improvement for L3 related resources
  processing.

  Thoughts?

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