...
| 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 ). The URI will change, as a query parameter. API change in A&AI. No external API impacts. ACTIONS: Inform Clients of break in change & migration. ASSOCIATED DEVELOPMENT:
| ||||||||||||||||||||
| 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 | ||||||||||||||||||||
| MOVED TO R5 EL ALTO | |||||||||||||||||||||
| 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 | ||||||||||||||||||||
...
- 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
Integration Wiki Test Cases: 5G - PNF PnP - Integration Test Cases
Summary Testing Status:
| GOAL | TEST CASE | STATUS | ||||||
|---|---|---|---|---|---|---|---|---|
| SO1: SO Support of A&AI Creation | #SO1 A&AI Creation |
| ||||||
| SO2: Service & NF Instance Association (VID UI) | #SO2 Service & NF Instance |
| ||||||
| SO3: SO Support for already existing PNF A&AI Entries | #SO3: Existing A&AI Entry |
| ||||||
| SO4: SO to Support updated A&AI PNF Schema | #SO4: A&AI PNF Schema update |
| ||||||
| AAF1: Security Enhancements | #AAF1: Security Enhancement |
| ||||||
| CTL1: Controller - PNF Interaction | #CTL1: Controller PNF Interaction |
| ||||||
| PRH1: A&AI New PNF Schema Adaptation | #PRH1: A&AI PNF Schema Adaptation |
| ||||||
| PRH2: Integration | #PRH2: Integration |
| ||||||
| PRH3: PNF Registration Update of the A&AI Entry | #PRH3: Registration Update |
| ||||||
| PRH4: Re-Registration Epic (w/ BBS U/C) | #PRH4: Re-Registration |
| ||||||
| A&AI1: A&AI pnf-id as Index for PNF | #PRH4: A&AI Schema update |
| ||||||
| A&AI4: SO Support of A&AI Creation | #A&AI4: SO Support of A&AI Creation |
| ||||||
| A&AI5: SO Support for already existing PNF A&AI Entry | #A&AI5: Existing A&AI Entry on PnP |
| ||||||
| VID1: Confirm UI Changes. Compatibility | #VID1: Confirm UI Changes |
| ||||||
| VID2: A&AI Schema Changes | #VID2: A&AI Schema Changes |
| ||||||
| VID3: VID PNF Management enhancements | #VID3: PNF Management |
| ||||||
| PORTAL1: Functional Menus | #PORTAL1: Functional Menus |
|
...
The following table summarized Requirements impacts
| PNF PnP Task | Requirements Impact (VNF-RQTS) |
|---|---|
| SO1: SO Support of A&AI Creation | (ONAP Platform centric) |
| SO2: Service & NF Instance Association (VID UI) | (ONAP Platform centric) |
| SO3: SO Support for already existing PNF A&AI Entries | (ONAP Platform centric) |
| SO4: SO to Support updated A&AI PNF Schema | (pnfRegistration event already sends the pnf-id and pnf-name) |
| AAF1: Security Enhancements |
? (TLS 1.2 certificates / optional) VNFRQTS - Certificate Authentication for HTTPS/TLS
| ||||||||||
| CTL1: Controller - PNF Interaction | ? (step 37) - ansible/netconf to PNF | |||||||||
| PRH1: A&AI New PNF Schema Adaptation | (ONAP Platform centric) | |||||||||
| PRH2: Integration | (ONAP Platform centric) | |||||||||
| PRH3: PNF Registration Update of the A&AI Entry | (ONAP Platform centric) | |||||||||
| PRH4: Re-Registration Epic (w/ BBS U/C) | ? CPauthenticated, triggers registration of PNF & tunnels. PNF sends confirmation notification/message additional event from state change. | |||||||||
| A&AI1: A&AI pnf-id as Index for PNF | (ONAP Platform centric) | |||||||||
| A&AI4: SO Support of A&AI Creation | (ONAP Platform centric) | |||||||||
| A&AI5: SO Support for already existing PNF A& |
| AI Entry | (ONAP Platform centric) |
| VID1: Confirm UI Changes. Compatibility | (ONAP Platform centric) |
| VID2: A&AI Schema Changes | (ONAP Platform centric) |
| VID3: VID PNF Management enhancements | (ONAP Platform centric) |
| PORTAL1: Functional Menus | (ONAP Platform centric) |
R4 API changes used by Plug and Play
The only API change used by PnP is the A&AI API change resulting from the A&AI schema change to (pnf-id)