Make L3 agent more responsive to RPC
On agent restart, the L3 agent immediately kicks off a periodic task called
*_sync_
*_rpc_loop* until it is done. This makes the L3 agent unresponsive to new work
coming in via RPC. Floating IPs need to wait to become active or inactive,
router gateways don't get plugged or unplugged, and subnet ports cannot be
manipulated. This gives a poor impression to a user who has just made an API
call to get something done.
Blueprint information
- Status:
- Complete
- Approver:
- Kyle Mestery
- Priority:
- Medium
- Drafter:
- Carl Baldwin
- Direction:
- Approved
- Assignee:
- Carl Baldwin
- Definition:
- Approved
- Series goal:
- Accepted for juno
- Implementation:
- Implemented
- Milestone target:
- 2014.2
- Started by
- Carl Baldwin
- Completed by
- Kyle Mestery
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
L3 agent prefers RPC messages over full sync
Gerrit topic: https:/
Addressed by: https:/
Improve the responsiveness of the L3 agent