Follow up from the ONS F2F Session the team agreed to work together to support the integration of Policy and CDS
Purpose:
Enable Closed Loop using CDS component.
Participants:
Yuriy Malakov Liam Fallon Alexis de Talhouët Oskar Malm Brinda Santh Muthuramalingam Magnus Buhrgard (Unlicensed) Rashmi Pujar Michela Bevilacqua Marc-Alexandre Choquette
What needs to be done:
1. DCAE - Finalize data stream collector, pm mapper
2. PNF simulator - Define data stream, Define YANG model for consequence action
3. TCA -Define threshold
4. Policy - Define policy
5. Blueprint Processor - Define action to trigger on the PNF
Here are the actions to be take:
| JIRA | Description | Owner | Comments |
|---|---|---|---|
PNF Content for reconfiguration PNF data file to be collected | Ericsson | Provide a sample of the pnf json/xml content that will be reconfigured using Yang Path. | |
Define Artifacts for DCAE (DFC, Mapper, TCA) | Ericsson | ||
Define Policy rule | Ericsson | ||
Define PNF Action to be taken by CDS. Define CDS blueprint to be executed | Ericsson | ||
POLICY-1656 - Getting issue details... STATUS | Get recipe to integrate plugin in APEX | Ericsson | Add another plugin for carrying events into and out of APEX, another one of these Event Carrier plugin review submitted just now: We also need an event protocol plugin to translate an APEX event into a CDS ExecutionServiceInput object. That's where the APEX and CDS metadata should meet. |
| Integrate CDS client | Bell Canada | gRPC [preferred] or HTTP SO client: https://github.com/onap/so/tree/master/common/src/main/java/org/onap/so/client/cds CDS wiki link: CCSDK Dublin Controller Design Studio Initiative | |
| Help define the CDS blueprint once action identify | Bell Canada | NOTE: This is a single action is required to reconfigure the PNF. The single action will execute the steps of param resolution, content generation and content distribution using Yang Patch. Leveraging the work done in Dublin release. | |