...
PnP DUBLIN WORK ITEM | DESCRIPTION |
Controller Association | [SDC/SO] The PNF controller caused quite a stir in Casablanca, the tension between Design/Platform Model vs Run-Time/Deployment Model. |
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 |
SO support for already existing PNF A&AI entry | [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) In Step #19B SO would exit and service creation would continue |
| 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. |
AAF SECURITY IMPACTS
PnP DUBLIN WORK ITEM | DESCRIPTION |
Security Enhancement | [AAF] Security enhancements slated for Dublin will need to be working for PnP Use Case |
...
PnP DUBLIN WORK ITEM | DESCRIPTION |
PRH with actual DU | It would be nice if in Dublin (or Frankfurt) if the Plug and Play Use Case actually worked with a real DU. |
| Integration | [PRH] There might be more integration or development for the PRH in Dublin. |
| A&AI New PNF Schema Adaptation | New AAI schema adaptations: Chesla Wechsler found a discrepancy between PNFs and VNFs; VNFs are idenitifed via VNF-ID (UUID), and PNFs - via PNF-Name. |
A&AI IMPACTS
| DUBLIN ITEM | DESCRIPTION | ||||||||
| 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: Chesla Wechsler). Get naming indexing consistency with PNFs and VNFs. Schema A&AI model update. Details: Proposal to Change AAI PNF Entity to use PNF-ID as key | ||||||||
| 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/ | ||||||||
| 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 | ||||||||
| 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 (Completed in ONAP/Casablanca -
| ||||||||
| SO support for already existing PNF A&AI entry | [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) In Step #19B SO would exit and service creation would continue |
...
PnP DUBLIN WORK ITEM | DESCRIPTION |
VID Enhancements | #4 – 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) #5 – VID A&AI INSTANCE CREATION – (optional) (slide 20/Step 4) – VID supporting Resource Declaration a PNF A&AI Instance creation. Similar flow in eCOMP. |
| VID PNF Mgmt. Enhancements | VID comes with certain PNF management capabilities. |
USE CASE SPAWNS
| 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). |
| 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 |
...