Versions Compared

Old Version 45

changes.mady.by.user Benjamin Cheung

Saved on

compared with

New Version 46

changes.mady.by.user Benjamin Cheung

Saved on

Key

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

...

PnP DUBLIN WORK ITEM

DESCRIPTION

SO1: 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

DEVELOPMENT STATUS:
This is already covered in ONAP/Casablanca:

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-797

 SOx SO2: Service & NF Instance Association

Associating a xNF to a Service. Seen in the VID UI, after instantiation waiting for registration see only a Service instance, and beyond that a PNF resource instance associated with it. 

DEVELOPMENT STATUS:


SO2SO3: SO support for already existing PNF A&AI entries

[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

DEVELOPMENT STATUS:

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

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-797

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

SO3SO4: 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.

ASSOCIATED DEVELOPMENT:

See task A&AI1 and PRH1.

JIRA:  (Depends on the A&AI work:

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2096
).

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-1273

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-1277
.

Epic Created:

SO Dublin Page: Service Orchesrator Dublin Release

FUTURE (El Alto)

SO-future: Controller Association

[FUTURE MOVED TO EL ALTO]

[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.

...