...
PnP DUBLIN WORK ITEM | DESCRIPTION | ||||||||
| PRH1: 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. 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).
| ||||||||
| 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 |
...