Goal

Migrate PNF PNP workflow to Building Blocks (BBs/GR_API).
Include newly created BBs in Service-Macro-Create flow.
Leave legacy implementation using VNF_API intact.

By PNF PNP workflow we understand 2 BPMNs:

CreateAndActivatePnfResource
ConfigurePnfResource

Both included in CreateVcpeResCustService_simplified BPMN

JIRA

https://lf-onap.atlassian.net/browse/SO-2556

https://lf-onap.atlassian.net/browse/SO-2785

https://lf-onap.atlassian.net/browse/VID-693

Involved parties

Lukasz Grech, Damian Nowak - PNF PNP workflow migration to BBs
Oskar Malm - ConfigurePnfResource.bpmn (previous, non-BB implementation)
Henry Xie - SO-CDS integration, new API for calling CDS from SO
Yuriy Malakov - CDS, SO-CDS integration
Rahul Tyagi - PNF SW upgrade, SO-CDS integration

Proposed building blocks

Gliffy Diagram is only supported by the cloud editor

Because Forge macros arent supported by the legacy editor, you'll need to convert this content to the cloud editor to display this macro properly. Find out more about converting to the cloud editor

AssignPnfBB

Responsibility:
- Creates PNF entry in AAI (with PNF name chosen by user)
- Additionally stores PNF model-related parameters in AAI (https://lf-onap.atlassian.net/browse/SO-2640):
  - model-customization-id
  - model-invariant-id
  - model-version-id
- Makes a link in AAI between Service entry and PNF entry
- Sets PNF orchestration status in AAI to Assigned
Currently implemented in CreateAndActivatePnfResource.bpmn

WaitForPnfReadyBB

Responsibility:
- Waits for "PNF ready" event sent from PRH to DMaaP
  - pnfCorrelationId from the event must match PNF instance name provided by the user during service instantiation
- Sets PNF orchestration status in AAI to:
  - Register - when starting to wait for PNF ready event
  - Registered - when PNF ready event is successfully received
Currently implemented in CreateAndActivatePnfResource.bpmn

Support for config assign (ControllerExecutionBB, action: configAssign)

https://lf-onap.atlassian.net/browse/SO-2646

Responsibility:
- Runs config assign via CDS
Currently implemented in ConfigurePnfResource.bpmn
We will reuse generic BPMN for calling CDS (ControllerExecutionBB)
Things to consider:
- SkipPostInstantiationConfiguration should be taken into account

Support for config deploy (ControllerExecutionBB, action: configDeploy)

https://lf-onap.atlassian.net/browse/SO-2647

Responsibility:
- Runs config deploy via CDS
Currently implemented in ConfigurePnfResource.bpmn
We will reuse generic BPMN for calling CDS (ControllerExecutionBB)
Things to consider:
- SkipPostInstantiationConfiguration should be taken into account

ActivatePnfBB

Responsibility:
- Sets PNF orchestration status in AAI as Active

Sequence in Service-Macro-Create flow

AssignServiceInstanceBB
CreateNetworkCollectionBB
AssignNetworkBB
AssignVnfBB
AssignVolumeGroupBB
AssignVfModuleBB
AssignPnfBB
WaitForPnfReadyBB
ControllerExecutionBB (action: configAssign, scope: pnf)
ControllerExecutionBB (action: configDeploy, scope: pnf)
ActivatePnfBB
ConfigAssignVnfBB
CreateNetworkBB
ActivateNetworkBB
CreateVolumeGroupBB
ActivateVolumeGroupBB
CreateVfModuleBB
ActivateVfModuleBB
ConfigDeployVnfBB
ActivateVnfBB
ActivateNetworkCollectionBB
ActivateServiceInstanceBB

PNF PnP workflow migration to Building Blocks