Versions Compared

Old Version 32

changes.mady.by.user Benjamin Cheung

Saved on

compared with

New Version 33

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

CTL1: Controller PNF Interaction

[CONTROLLER] Controller definition (SDN-C) came so late in Casablanca, we had defined some additional optional parameter for the step37 Service Configuration but likely more evolution needs to be done. SDN-C was not the theoretical proper controller and people objected as this is conceptually the L0-L3 controller.

[STEP 35-37] - The SO to SDN-C and Controller to PNF exchange (Ansible or NetConf) was a carry-over item from R3. This requires that an API between SO to SDN-C is in place to support this. It requires that SDN-C support the appropriate Ansible Playbook and Directed Graph. Generic API. CDS has its own API to SO.

Controller Design Studio (Design Time) - to customize configuration. This might be used to set the values of parameters that might be send down to a PNF.

NetConf - see the NetConf 5G U/C Wiki: 5G - Configuration with NETCONF


PRH IMPACTS


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: Integration[PRH] There might be more integration or development for the PRH in Dublin.
PRH3: 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.

PRH shall update A&AI with all fields from pnfRegistration VES event into all corresponding fields of A&AI entry. See the 5G - PNF Plug and Play wiki

DEVELOPMENT STATUS:

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

...

PnP DUBLIN WORK ITEM

DESCRIPTION

VID1: VID Enhancements

WORK ORDER (Optional) – Supporting Work Order. Supported with service specific  applications. Inventory systems (optional). Future extension to ONAP. Interface w/ BSS-OSS systems (API).

ACTION: Error cases (check if SDC model parameters != A&AI PNF entry)

VID2: VID EnhancementsVID A&AI INSTANCE CREATION – (optional) (slide 20/Step 4) – VID supporting Resource Declaration a PNF A&AI Instance creation. Similar flow in eCOMP.
VID3: VID PNF Mgmt.
Enhancements		VID comes with certain PNF management capabilities.
These will be impacted by an A&AI PNF model changes, and VID will have to be updated to support the new AAI Schema change PNF model .(PNF-id vs PNF-name)
Proposal to Change AAI PNF Entity to use PNF-ID as key

...