...

Both included in CreateVcpeResCustService_simplified BPMN

Proposed building blocks

AssignPnfBB

• Responsibility:
  • Creates PNF entry in AAI
  • Makes a link in AAI between Service entry and PNF entry
• Currently implemented in CreateAndActivatePnfResource.bpmn
• Things to consider:
  • In current implementation connecting PNF entry in AAI with service entry is done at the end of CreateAndActivatePnfResource (after the "PNF ready" event is received)

WaitForPnfReadyBB

• Responsibility:
  
  • Waits for "PNF ready" event sent from PRH to DMaaP
• Currently implemented in CreateAndActivatePnfResource.bpmn
• Things to consider:
  • BBS-related parameters stored in AAI?
  • Make new BBs generic enough (i.e. wait for an event sent to DMaaP) that they could be reused in other flows (request from Seshu)

ConfigAssignPnfBB

• Responsibility:
  
  • Runs config assign via CDS
• Currently implemented in ConfigurePnfResource.bpmn
• Things to consider:
  • New approach to calling CDS/controllers - ControllerExecutionBB/actor in SDC model (Henry Xie, see https://wiki.onap.org/display/DW/SO+Weekly+Meeting+2019-12-4)
  • Service decompositioon should handle SkipPostInstantiationConfiguration
    
    

ConfigDeployPnfBB

• Responsibility:
  
  • Runs config deploy via CDS
• Currently implemented in ConfigurePnfResource.bpmn
• Things to consider:
  
  • New approach to calling CDS/controllers - ControllerExecutionBB/actor in SDC model (Henry Xie, see https://wiki.onap.org/display/DW/SO+Weekly+Meeting+2019-12-4)
  • Service decompositioon should handle SkipPostInstantiationConfiguration
    

ActivatePnfBB

• Responsibility:
  • Sets PNF orchestration status in AAI as Active

Other considerations

• Are all required PNF parameters included in GeneralBuildingBlock->ServiceInstance→Pnf? 
  • Currently those are:
    • pnf-id
    • pnf-name
    • role
    • orchestration-status
    • cloud-region
  • Currently AAI schema (aai_schema_v19.xsd) for PNF contains: 
    • Fields: pnf-name, pnf-name2, selflink, pnf-name2-source, pnf-id, equip-type, equip-vendor, equip-model, management-option, orchestration-status, ipaddress-v4-oam, sw-version, in-maint, frame-id, serial-number, ipaddress-v4-loopback-0, ipaddress-v6-loopback-0, ipaddress-v4-aim, ipaddress-v6-aim, ipaddress-v6-oam, inv-status, resource-version, prov-status, nf-role, admin-status, operational-status, model-customization-id, model-invariant-id, model-version-id (from SO cataloge), pnf-ipv4-address, pnf-ipv6-address
    • Sub-structures: software-versions, relationship-list, p-interfaces, lag-interfaces, vrfs
  •  BBInputSetup implementation does not mention PNF at all - is it even initialized in GeneralBuildingBlock?
  • PNF ip is resolved by CDS by PNF ID (it should be in AAI) - it's populated by PRH
• How to include new BBs in Service-Macro-Create flow?
  • Where to put new BBs in the flow sequence?
  • Service decomposition in WorkflowActionBB may not unserstand PNFs (Retrieve BB Execution List)
  • Service decompositioon should handle SkipPostInstantiationConfiguration
• PNF orchestration status changes in AAI - which states should be assigned in which steps of the workflow
  • Should we have ActivatePnfBB? 
• PNF SW upgrade (Oskar Malm)
  • PNF should be active - PNP is finished
  • new Upgrade flow will be created (BBs vs traditional considered)
• 5G NRM Configuration - plan for new BB which invokes configuration via CDS of NRM resource(?) (Yaoguang Wang, see https://wiki.onap.org/display/DW/SO+Weekly+Meeting+2019-12-4)
• Make new BBs generic enough that they could be reused in other flows (request from Seshu)
• Service-Macro-Delete
  • Should we delete PNF resource from AAI on service deletion?
    
    • We plan to leave it. What orchestration status should it get? Inactive?

Proposed sequence in Service-Macro-Create flow

1. AssignServiceInstanceBB
2. CreateNetworkCollectionBB
3. AssignNetworkBB
4. AssignVnfBB
5. AssignVolumeGroupBB
6. AssignVfModuleBB
7. AssignPnfBB
8. WaitForPnfReadyBB
9. ActivatePnfBB
10. CreateNetworkBB
11. ActivateNetworkBB
12. CreateVolumeGroupBB
13. ActivateVolumeGroupBB
14. CreateVfModuleBB
15. ActivateVfModuleBB
16. ActivateVnfBB
17. ActivateNetworkCollectionBB
18. ActivateServiceInstanceBB

Current implementation

All variables mentioned below (unless stated otherwise) are BPMN execution variables.

CreateAndActivatePnfResource

Check inputs (PnfCheckInputs)

Inputs:

• pnfCorrelationId
• pnfUuid
• serviceInstanceId
• aai.pnfEntryNotificationTimeout (from application properties)
  

Checks if following variables are set (throws exception if not):

• pnfCorrelationId
• pnfUuid
• serviceInstanceId
• aai.pnfEntryNotificationTimeout (in application properties)

Check AAI for pnf_correlation_id (CheckAaiForPnfCorrelationIdDelegate)

Inputs:

• pnfCorrelationId

Reads the info about PNF from AAI (org.onap.aai.domain.yang.Pnf) based on pnfCorrelationId.

Outputs:

• aaiContainsInfoAboutPnf - true if entry in AAI exists, false otherwise

Create Pnf entry in AAI (CreatePnfEntryInAaiDelegate)

Inputs:

• pnfCorrelationId
• pnfUuid

Creates PNF entry in AAI (org.onap.aai.domain.yang.Pnf) and sets:

• pnfId (in Pnf object) as pnfUuid
• pnfName (in Pnf object) as pnfCorrelationId

This is conditional task executed only if aaiContainsInfoAboutPnf is set to false.

Register in Dmaap (InformDmaapClient)