You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

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

PROJECTPTLUser Story / EpicRequirement
A&AI

James Forsyth



AAF
Jonathan Gathman


APPC

Takamune Cho



CLAMP

Gervais-Martial Ngueko



CC-SDK

Dan Timoney

Controller to PNF exchange (Epic)
  1. Support NetConf
  2. 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

 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 to NF Association


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

CONTROLLER IMPACTS

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

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&AI1: 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 )

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&AI4: A&AI pnf-id as INDEX for PNF

[A&AI] New A&AI schema adaptations: discrepancy between PNFs and VNFs; VNFs are identified via VNF-ID (UUID), and PNFs - via PNF-name. 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).

July 31th 2019 → AAI team has cancelled this request (redacted).

CANCELED


  • No labels