API for l2 agent extensions (+ovs flow management)
L2 agent extensions were introduced in Liberty. Currently they don't have any way to influence agents that they run inside. For example, there is no way they can set flows for OVS bridges, create new tables, add patch ports, etc.
Multiple subprojects (SFC, BGP-VPN) expressed the need for such mechanism that would allow them all mentioned above. Without it, they are forced to patch the agent code, which does not help their adoption, and makes Neutron platform more scattered.
Mitaka effort: http://
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Low
- Drafter:
- Miguel Angel Ajo
- Direction:
- Approved
- Assignee:
- David Shaughnessy
- Definition:
- Approved
- Series goal:
- Accepted for pike
- Implementation:
-
Implemented
- Milestone target:
-
pike-2
- Started by
- Armando Migliaccio
- Completed by
- Slawek Kaplonski
Related branches
Related bugs
Bug #1517903: [RFE] Add agent specific API for l2 agent extensions | Fix Released |
Bug #1563967: [RFE] Extend l2-extensions-api for flow management | Won't Fix |
Sprints
Whiteboard
Dec-01-2016(armax): spec in review, unlikely this is gonna make the code cut.
Sep-08-2016(armax): deferred to Ocata
Aug-02-
May-19-2016(armax): bug 1563967 prompted a continuation of this effort.
01-feb-2016(armax): spec needs merging. Status update:
http://
Specs: https:/
https:/
Patch: https:/
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
ovs-agent: Seperate VLAN mapping outside of the agent