Versions Compared

Old Version 24

changes.mady.by.user Benjamin Cheung

Saved on

compared with

New Version 25

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

PRH1: A&AI New PNF
Schema Adaptation

New A&AI schema adaptations: Chesla Wechsler found a discrepancy between PNFs and VNFs; VNFs are identified via VNF-ID (UUID), and PNFs - via PNF-name.
So PNF-id should be used for Identities. This differentiates the way that PRH is searching for PNFs in A&AI, when PRH does the PNF registration in A&AI (may also require SO change).

A PNF-name parameter will be used to search a relevant PNF instance, and then CRUD operations will be executed using the PNF-ID value obtained from that previous instance search.

PNF-id = UUID;

PNF-name = Correlation ID.

PRH use search API to find PNF instance based on PNF-name then get the PNF-id.

pnfRegistration VES Event to get the Key to search A&AI. use "sourcename" (part of VES Common header). Take value of sourcename search A&AI to find a PNF entry. In R3/Casa search against PNF-name = sourcename (search for object get PNFid); In R4/Dublin search against PNF-name = sourcename (with a different API). search for object. Change in primary key in A&AI.

ASSOCIATED DEVELOPMENT:

See task A&AI1 and SO4.
This work is to be covered here:

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-885

PRH2: PRH with actual DUIt would be nice if in Dublin (or Frankfurt) if the Plug and Play Use Case actually worked with a real DU.
PRH3: Integration[PRH] There might be more integration or development for the PRH in Dublin.
PNF Registration Update the A&AI Entry

When the PNF registers, PRH should update the A&AI entry with the information in the VES event.

DEVELOPMENT STATUS:

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


A&AI IMPACTS

DUBLIN ITEMDESCRIPTION
A&AI1: A&AI pnf-id as INDEX for PNF

[A&AI] Using the pnf-id (instead of pnf-name) as the index for PNF into A&AI. (discussion started in R3, socialized, Contact: Chesla Wechsler ).
Get naming indexing consistency with PNFs and VNFs. Schema A&AI model update.

ACTIONS: Inform Clients of break in change & migration.
Details: Proposal to Change AAI PNF Entity to use PNF-ID as key
ASSOCIATED DEVELOPMENT:


A&AI2: External Manager (EMS/NMS) [ESR]

[A&AI] IP address or association with the External Manager. Is the ESR concept sufficient? https://onap.readthedocs.io/en/beijing/submodules/aai/esr-server.git/docs/

During PnP, the IP address of the External Manager would saved/stored or set by user or by the PNF. Where would that be stored? would it be in A&AI. Information about the External Manager is discovered & stored.

A&AI3: Cloud Home Server (A&AI)[A&AI] Tracking the Cloud Home Server (CLLI, Cloud ID); is the association with the COMPLEX Object sufficient? How-To: Register a VIM/Cloud Instance to ONAP
A&AI4: 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:

(Completed in ONAP/Casablanca -

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

A&AI5: SO support for already existing PNF A&AI entry

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

In Step #19B SO would exit and service creation would continue

...