Detect network delete with Neutron registry callbacks
Currently, our bagpipe driver relies on a specific bgpvpn_notify mechanism driver, which could be used to react on networks being deleted and cleanup the associations when that happens.
However:
• this is driver-specific
• it has the drawback of requiring an ML2 driver
• it is not yet used to clean up the associations (implements a behavior that we abandon where deleting a network associated with a BGPVPN would be blocked)
What needs to be done:
• extend the Neutron registry callbacks to produce events for network delete events (similarly as https:/
• in drivers that rely on Neutron doing the persistency, rely on these callbacks to clean up the associations when networks are deleted
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Thomas Morin
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Thomas Morin
Related branches
Related bugs
Sprints
Whiteboard
Mathieu: thomas, don't you think that this bp is superseded by:
https:/
Thomas: no, because the other blueprint is about port create/
Close as superseded, for the reason above.
