Provide support for validation by vendor L3 plugins

Registered by Paul Michali on 2014-03-24

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:
milestone icon 2014.2
Started by
Kyle Mestery on 2014-06-09
Completed by
Kyle Mestery on 2014-07-25

Related branches

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://review.openstack.org/#q,topic:bp/L3,n,z

Addressed by: https://review.openstack.org/91437
    BP: L3 Service validation call flow prototype

Gerrit topic: https://review.openstack.org/#q,topic:bp/l3-svcs-vendor-validation,n,z

Addressed by: https://review.openstack.org/96946
    VPNaaS: Allow vendor extend/override valiadation

Gerrit topic: https://review.openstack.org/#q,topic:pcm/bp/validate-ref,n,z

Addressed by: https://review.openstack.org/102351
    VPNaaS: separate out validation logic for ref impl

Addressed by: https://review.openstack.org/107473
    VPNaaS: Separate validation for Cisco impl

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.