Versions Compared

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. The work being done with the CDS work is re-used for PnP U/C, so no new development needs to be done.

ASSOCIATED DEVELOPMENT:

(Jira)

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 R6 Frankfurt WORK ITEM

DESCRIPTION

PRH2: Integration[PRH] There might be more integration or development for the PRH in Dublin.
PRH1: A&AI New PNF
Schema Adaptation

New A&AI schema adaptations: PNF PLUG and PLAY in R6 Frankfurt 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/Casablanca 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.

Added March 13th 2019 → AAI team got a recommendation from architecture committee to defer this item to ONAP/El Alto release.

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

PRH(discuss): Step 37a PNF "Activated" message to ONAP

State Change VES Event (type = State Change)

Old state & New State.

CPE Authentication Notification

BBS U/C is using this flow to "update" ONAP letting ONAP know that the PNF has been successfully been activated.

From VES Event Listener Document:

newState

string

Yes

New state of the entity: ‘inService’, ‘maintenance’, ‘outOfService’

oldState

string

Yes

Previous state of the entity: ‘inService’, ‘maintenance’, ‘outOfService’



A&AI IMPACTS

DUBLIN ITEMDESCRIPTION
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
)

MOVED TO R5 EL ALTO
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. Note: The External Manager info is optional

LOW PRIORITY
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

LOW PRIORITY

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: PNF PLUG and PLAY in R6 Frankfurt ).  The URI will change, as a query parameter.
Get naming indexing consistency with PNFs and VNFs. Schema A&AI model update.

API change in A&AI. No external API impacts.

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

Added March 13th 2019 → AAI team got a recommendation from architecutre committee to defer this item to ONAP/El Alto release.

ASSOCIATED DEVELOPMENT:

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAAI-2096
(Epic)

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAAI-2148
(Story)

July 17, 2019 - James Forsyth  has indicated that this will not happen. Cancelling this request.

...