...
See Pamela Dragosh's presentation from Santa Clara, especially the workflow/state diagram for policy design/test/certification
ONAP Beijing Release Developer Forum, Dec. 11-13, 2017, Santa Clara, CA US
...
Policy Design can occur in several places during a "design" process. During design time the models should allow a service designer and/or operations team to be able to express and capture policy both at its highest abstraction as well as using a specific policy language if desired.
Model Driven VF Policy Design via VNF SDK Packaging
VF vendors express policies such as SLA, Licenses, run-time metric suggestions, etc. These details are captured within the VNF SDK and uploaded into the SDC Catalog.
For example, SLA policies may be captured via TOSCA specification. License policies can be captured via TOSCA or XACML specification (TBD). Run-time metric vendor recommendations can be captured via VES Standard specification.
Model Driven Policy Design via SDC GUI
The SDC GUI supports several types of policies that can be captured during design time. DCAE micro service configuration policies can be onboarded via the DCAE-DS (DCAE Design Studio). Service policies such as Optimization, Placement policies can also be captured via TOSCA model during design time.
Model Driven Policy Design via Policy Dashboard (exposed via ONAP Portal SDK)
- The Policy GUI Dashboard is created from the ONAP Portal SDK to create a consistent user experience
- The Policy GUI Designer is created from the ONAP SDC SDK to create a consistent user experience
...