Provide support for validation by vendor L3 plugins
Provide the ability for vendor plugins to optionally perform actions before (validation), during (commit), and after (apply) actions for L3 services. This would allow a vendor to reject a configuration change, before it has been persisted, perform any additional persisting, and take any actions (like the current apply step) after persisting the change.
Blueprint information
- Status:
- Complete
- Approver:
- Kyle Mestery
- Priority:
- Low
- Drafter:
- Paul Michali
- Direction:
- Approved
- Assignee:
- Paul Michali
- Definition:
- Approved
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
-
2014.2
- Started by
- Kyle Mestery
- Completed by
- Kyle Mestery
Related branches
Related bugs
Sprints
Whiteboard
15-July (mestery): Moving to Juno-3, as the code is unlikely to land in Juno-2.
9-Jun (mestery): Setting this as Juno-2 with low priority.
Gerrit topic: https:/
Addressed by: https:/
BP: L3 Service validation call flow prototype
Gerrit topic: https:/
Addressed by: https:/
VPNaaS: Allow vendor extend/override valiadation
Gerrit topic: https:/
Addressed by: https:/
VPNaaS: separate out validation logic for ref impl
Addressed by: https:/
VPNaaS: Separate validation for Cisco impl
