...
Dublin is the start for the Policy Framework team to re-build the infrastructure in order to better support multiple PDP engines and fix many issues with policy deployment. For more specifics, please refer to these pages:
- The ONAP Policy Framework: Architectural Improvements for Dublin
- Control Loop Operation and Improvements. - NOTE this improvement will also be integrated with the existing architecture and available to Control Loop applications using the old API in Dublin.
- Current API Limitations with Respect to DCAE mS Policies - WIP to help future teams to map new API's to the old API's
A description of the new architecture is described here:
New or modified interfaces
Policy Lifecycle API - new API that is RESTful and supports TOSCA Policy Types
A brief flow has been worked by the team here: Policy Design and API Flow for Model Driven Control Loop - Draft
Swagger documentation is being built and the team will conform with API Versioning specifications
If they are modified, are the backwards compatible?
No - the design of the Old API prohibits that and isn't feasible. The current API is still available for applications that still use it.
The Policy Lifecycle API will support in Dublin the Casablanca non-TOSCA policy models for Control Loop operational policies and guard policies.
Interface naming (point to an example)
Policy Lifecycle API - Policy Design and API Flow for Model Driven Control Loop - Draft
Reference to the interfaces.
Legacy API: Policy API
What are the system limits?
...
vFW, Scale Out, vCPE, CCVPN and BBS are targeted for support.
Model driven Control Loop Design via the Control Loop Sub Committee
Listing of new or impacted models used by the project (for information only).
New Policy Type models for Control Loops is being built for Dublin. These are simply ports from existing non-TOSCA compliant models towards TOSCA compliance and a step towards integration with SDC design time. The first models are for DCAE uS Policy Models.
Will be working with the Modeling Sub Committee to hand over the models for integration with other ONAP Data and Information Models.