...
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: 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. | ||||||||
| PRH3: Integration | [PRH] There might be more integration or development for the PRH in Dublin. |
...
| DUBLIN ITEM | DESCRIPTION | ||||||||
| 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: Chesla Wechsler ). ACTIONS: Inform Clients of break in change & migration. server | ONAP JIRA | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb | key | AAI-1551 | |||
| 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/ | ||||||||
| 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 | ||||||||
| A&AI4: 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: (Completed in ONAP/Casablanca -
| ||||||||
| A&AI5: 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 |
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. |
| VID2: 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 |
PORTAL
Interface update change.
Functional menu accesable to any ONAP users from portal.
provide seamless user experience when multiple back-end components involved e.g. SDC, VID, A&AI etc
when user goes from 1 component to another e.g. modeling, pnf instance decalaration, activation
can be provided as functional menus in PORTAL.
If a new user doesn't know what the next step is to perform, the PORTAL can recomment the next step via notifications or alerts.
USE CASE SPAWNS
| 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 |
...