07-05-2018 ONAP Policy - SDC Service Distribution Application Discussion

Attendees:

Agenda:

This meeting discussed the requirement to distribute policies from SDC to the ONAP Policy Framework.The epic for thi work is POLICY-701.

Notes:

For HPA, the requirement is to read the TOSCA descriptor from a CSAR, read the node types, insert them into a placement policy, and then make this policy available in the XACML PDP so that it can be accessed by OOF.

We want to have support so that a policy can be stored in SDC in a CSAR or possibly in another artifact and that it is distributed to the PF. However, for HPA, it is a special case where the TOSCA descriptor is read , a policy is composed in the ONAP PF using the TOSCA descriptor.

When using the SDC client, The ONAP PF needs to register with SDC using the API as "Policy". It also needs to comply with the SDC auditing rules. Auditing events are sent to SDC at different phases in the downloading process so that the process can be audited.

Today, everything that is needed is in the CSAR. In the future there may be other documents that can be downloaded.

SDC client handles all the communication over ONAP, the user does not need to worry on the details of this communication over ONAP. Just use the Client java API.

How does version control work? You get a new UUID for the new version, you need to subscribe to and download those new/changed version into the ONAP PF. We will need to handle the policy versions in the deployment handling in the ONAP PF.

in HPA, the TOSCA contains node types, not policies, these somehow need to be come policies so we need a way of creating the policy specifically for HPA. We need to address this in the PF.

SDC has a TOSCA parser. The PF will use the TOSCA parser because then the PF is always guaranteed that the parsing will work on TOSCA provided by SDC.

Simulator needed for SDC client to act as simulator for DMaaP and SDC. There is also a connection to SO which sends a notification to SDC called "Distribution complete" . SO keeps track of who has downloaded services, it uses this to keep track of what services are fully and completely deployed.

Auuomation and recovery is not fully there yet in ONAP. In the meantime, we'll use good error and progress logging while we await better support in ONAP.

The SDC distribution component in the PF must follow all the manageability/coverage/SONAR/logging requirements that all software components must follow in the ONAP PF.