...
PNF PLUG AND PLAY ENHANCEMENTS SUMMARY BY PROJECT:
PROJECT | IMPACT | PTL |
SDC | PNF pre-onboarding/ PNF onboarding package management and processing. | |
SO | SO to Controller to PNF communication | |
AAF | Security Enhancements | |
SDN-C/R | Controller to PNF communication (Ansible, NetConf) | |
PRH | PRH Enhancements & Integration | |
A&AI | A&AI enhancements, PNF-ID. ESR support. | |
| VID | VID enhancements & Carry over from R3 | Ofir Sonsino |
| PORTAL | Impact on Functional Menus | Manoop Talasila |
| SDC |
...
DUBLIN ITEM | DESCRIPTION | |||||
SDC1: Licensing Management | Having meta-data manage licensing. This at first (in Dublin) might be very simple but can be expanded. Feature activation licensing. Vendor licensing management systems.First step in Dublin related to Licensing is the License to be onboarded in the PNF onboarding package during Pre-Onboarding. This is being worked with the | PNF | Pre-Onboarding/PNF Onboarding Use Case. The wiki:SDC2: PNF Artifacts SDC3: (PNF Package) & PNF Modeling | Package management | Ofir Sonsino | 5G - PNF Pre-Onboarding & Onboarding
SO IMPACTS
PnP DUBLIN WORK ITEM | DESCRIPTION | ||||||||
SO1: Controller Association | [SDC/SO] The PNF controller caused quite a stir in Casablanca, the tension between Design/Platform Model vs Run-Time/Deployment Model. | ||||||||
SO2: SO support of A&AI creation | [SO] A&AI UI can create an inactive PNF (inactive) A&AI entry. In Step #19A instead of EXITING, SO would go into WAIT STATE pending rehydration of RLF w/ pnfReady 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) 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.
This is not planned to be changed in ONAP/Dublin release. | ||||||||
| SO4: SO to support updated A&AI PNF schema | [SO] Support of SO for updated AAI PNF instance model. ASSOCIATED DEVELOPMENT: See task A&AI1 and PRH1. |
...
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. 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.
| ||||||||||
| 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. DEVELOPMENT STATUS:
|
...
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 Enhancements | VID A&AI INSTANCE CREATION – (optional) (slide 20/Step 4) – VID supporting Resource Declaration a PNF A&AI Instance creation. Similar flow in eCOMP. |
| VID2VID3: 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 PNF model. Proposal to Change AAI PNF Entity to use PNF-ID as key |
...
| XTRA1: 5G RAN Work Flow | Need dedicated 5G RAN Work Flow for PNF Plug and Play (instead of it being part of the VCPE work flow). |
| XTRA2: VNF & PNF 5G Flow | CU w/ DU - New 5G Sub-Use Case. Interleaving w/ Controller association. MODELLING work to lay ground-work (SA/SD, OO, UML) 5G RAN W/F |
SDC & PRE/ONBOARDING IMPACTS
DUBLIN ITEM | DESCRIPTION |
SDC1: Licensing Management | Having meta-data manage licensing. Vendor licensing management systems. Being worked in PNF Pre-Onboarding/PNF Onboarding Use Case. Wiki: |
SDC2: PNF Artifacts SDC3: (PNF Package) & PNF Modeling | [SDC] PNF onboarding package artifacts in PNF package. Now done with Pre-Onboarding/PNF Onboarding Use Case, at: |
TESTING
Test Environment: TBD
Integration Team Liasion: TBD
Current Status:
- The Use Case is not functional yet, nor in the test laps and is not yet ready for the Dublin release
- Testing has not begun yet to show the test case works
Summary Testing Status:
| GOAL | TEST CASE | STATUS | ||||||
|---|---|---|---|---|---|---|---|---|
| SO1: Controller Association | ## |
| ||||||
| SO2: SO Support of A&AI Creation | ## |
| ||||||
| SO3: SO Support for already existing PNF A&AI Entries | ## |
| ||||||
| SO4: SO to Support updated A&AI PNF Schema | ## |
| ||||||
| AAF1: Security Enhancements | ## |
| ||||||
| CTL1: Controller - PNF Interaction | ## |
| ||||||
| PRH1: A&AI New PNF Schema Adaptation | ## |
| ||||||
| PRH2: Integration | ## |
| ||||||
| PRH3: PNF Registration Update of the A&AI Entry | ## |
| ||||||
| A&AI1: A&AI pnf-id as Index for PNF | ## |
| ||||||
| A&AI2: External Manager (EMS/NMS) [ESR] | ## |
| ||||||
| A&AI3: Cloud Home Server (A&AI) | ## |
| ||||||
| A&AI4: SO Support of A&AI Creation | ## |
| ||||||
| A&AI5: SO Support for already existing PNF A&AI Entry | ## |
| ||||||
| VID1: Vid Enhancements | ## |
| ||||||
| VID2: VID Enhancements | ## |
| ||||||
| VID3: VID PNF Management enhancements | ## |
| ||||||
| PORTAL1: Functional Menus | ## |
|