...
- Responsibility: Runs config assign via CDS
- Currently implemented in ConfigurePnfResource.bpmn
SO PNF PNP migration is being documented: https://wiki.onap.org/display/DW/PNF+PnP+workflow+migration+to+Building+Blocks
The JIRA to track progress: https://jira.onap.org/browse/SO-2556.
Lukasz Grech and Lukasz Muszkieta (Nokia) are leading the SO changes related to migration of PNF PnP sub-flows (sub-Processes_ to building blocks.
This link is about the current (Dublin + El Alto) implementation: https://wiki.onap.org/display/DW/PNF+PNP+workflow+-+current+implementation
The SO BPMN code can be found at CreateAndActivatePnfResource.bpmn.
This is where the implementation is stored today.
Also refer to the following topic in Gerrit: pnf_bb
https://gerrit.onap.org/r/#/q/status:merged+project:so+branch:master+topic:pnf_bb
This is where other changes expected for the PNF PnP BBs are expected to be added.
A few building blocks will be created in R6 (expected by end of February 2020).
The currently available workflows dealing for PNF PnP can be seen at the PNF PnP test-cases descriptions in the ONAP Integration project.
VID IMPACTS
| R6 ITEM | DESCRIPTION |
|---|---|
| VID1 Migration of Sub-worksflows | Migration of existing PNF PnP sub-workflows to a new BB approach (probably we will be creating 4-5 new BBs). VID Impact: Within “old” VID macro orchestration pages, a special field to provide a pnf-id parameter (shall be actually called “correlationID” or “PNF correlationID”) has been displayed under the following conditions:
When we migrate to BB approach, we`d keep the possibility to provide this parameter (PNF correlationID) to the SO API call as input. How this will change with SO/BB approach, and with new VID GUI targeted at macro (GR) flows – we`d see exactly, after we execute some tests with new VID UI, and updated SO PNF BB code. |
...