Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Attendees:

Pamela Dragosh

Michael Lando

Michael Morris

libo zhu

Mahendra Raghuwanshi

Mayank Gupta

ruoyu.ying

Liam Fallon

@bharath

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.


  • No labels