Wiki to the "Base" PNF Plug and Play Page: 5G - PNF Plug and Play

PRH update handling of Logical Links (move to SO) - introduced in R4 Dublin for BBS/Re-registration Epic

DEVELOPMENT IMPACTS

PROJECT	PTL	User Story / Epic	Requirement
A&AI	James Forsyth
AAF	Jonathan Gathman
APPC	Takamune Cho
CLAMP	Gervais-Martial Ngueko
CC-SDK	Dan Timoney	Controller to PNF exchange (Epic)	Support NetConf Support of Parameter x
DCAE	Vijay Venkatesh Kumar
DMaaP	Mandar Sawant
External API	Matthieu Geerebaert
MODELING	Hui Deng
Multi-VIM / Cloud	Bin Yang
OOF	Sarat Puthenpura
POLICY	Pamela Dragosh
PORTAL	Manoop Talasila
SDN-C	Dan Timoney
SDC	Ofir Sonsino
SO	Seshu Kumar Mudiganti
VID	Ofir Sonsino
VNFRQTS	Steven Wright
VNF-SDK	Weitao Gao
CDS	Yuriy Malakov

List of PTLs:Approved Projects

SO IMPACTS

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: SO-797 - Getting issue details... STATUS
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:
SO3: 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. SO-797 - Getting issue details... STATUS This is not planned to be changed in ONAP/Dublin release.
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.
SO4: 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. Added March 13th 2019 → AAI team got a recommendation from architecutre committee to defer this item to ONAP/El Alto release. ASSOCIATED DEVELOPMENT: See task A&AI1 and PRH1. JIRA: (Depends on the A&AI work: AAI-2096 - Getting issue details... STATUS ). SO-1273 - Getting issue details... STATUS SO-1277 - Getting issue details... STATUS . Epic Created: SO Dublin Page: Service Orchestrator Dublin Release

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: DCAEGEN2-885 - Getting issue details... STATUS

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 ITEM	DESCRIPTION
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 - SO-797 - Getting issue details... STATUS )
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: AAI-2096 - Getting issue details... STATUS (Epic) AAI-2148 - Getting issue details... STATUS (Story) July 17, 2019 - James Forsyth has indicated that this will not happen. Cancelling this request.

Space shortcuts

Page tree

DEVELOPMENT IMPACTS

SO IMPACTS