Versions Compared

Old Version 10

changes.mady.by.user Damian Nowak

Saved on

compared with

New Version 11

changes.mady.by.user Damian Nowak

Saved on

Key

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

...

PnP DUBLIN WORK ITEM

DESCRIPTION

Controller Association

[SDC/SO] The PNF controller caused quite a stir in Casablanca, the tension between Design/Platform Model vs Run-Time/Deployment Model.
As a result the SO controller design was sub-optimal and should be addressed in Dublin.

SO support of A&AI creation

[SO] A&AI UI can create an inactive PNF (inactive) A&AI entry.
A Service provider might use an inventory system and A&AI UI to create a PNF A&AI entry.

In Step #19A instead of EXITING, SO would go into WAIT STATE pending rehydration of RLF w/ pnfReady
This is already covered in ONAP/Casablanca:

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-797

SO support for already existing PNF A&AI entryentries

[SO] Support of SO for an already existing PNF (active) A&AI Entry

(use case with a deleted & recreated service or instantiating 2nd service using the same PNF)
Within ONAP/Beijing - In Step #19B SO would exit and service creation would continue

In ONAP/Casablanca this was updated, and irrespective of AAI entry existence for a PNF instance, the workflow execution always waits to receivea PNF registration event.

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-797

This is not planned to be changed in ONAP/Dublin release.

SO to support updated A&AI PNF schema[SO] Support of SO for updated AAI PNF instance model.
PNF-ID is going to be used as unique PNF idenitifcator, instead of PNF-Name, used in ONAP/Casablanca.
PNF PnP sub-flow might need modifications related to how PNF instance objects are created.

...