Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-2785

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVID-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

...

  • Responsibility:
    • Runs config assign via CDS
  • Currently implemented in ConfigurePnfResource.bpmn
  • Things to consider:

ControllerExecutionBB (action: configDeploy)

...

  • Responsibility:
    • Runs config deploy via CDS
  • Currently implemented in ConfigurePnfResource.bpmn
  • Things to consider:
    • SkipPostInstantiationConfiguration should be taken into account

ActivatePnfBB

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

...

Service decomposition (Retrieve BB Execution List)

  • PNFs should be recognized in service model and proper BBs should be assigned for execution.

...

  • PNF resources should be properly initialized in GeneralBuildingBlock→ServiceInstance

PNF PNP workflow integration with CDS

Gliffy Diagram
macroId670810bb-3ef5-466b-9dfe-77084b450687
namePNF PNP workflow integration with CDS
pagePin13

...

Generic controller BB working with PNFs

PNF PNP workflow integration with CDS

Gliffy Diagram
macroId670810bb-3ef5-466b-9dfe-77084b450687
namePNF PNP workflow integration with CDS
pagePin14

VID - required changes

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVID-693

Updates for service macro instantiation:

...

  • 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
    • (warning) 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 decomposition should handle SkipPostInstantiationConfiguration
  • PNF orchestration status changes in AAI - which states should be assigned in which steps of the workflowShould 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?