...
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 |
...
| PNF Package management | Ofir Sonsino |
SO IMPACTS
PnP DUBLIN WORK 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 | [SDC] In Casablanca we did not get in artifacts in time, and for Dublin we are looking to incorporate actual Artifacts. VES Events require their YAML definitions to be supported as PNF artifacts (incorporated into a PNF CSAR package). This is vital for the VES events that the PNFs emit to be recognized by ONAP. Some parameters were identified for PNF model and pushed to Dublin for example the Package version. This is now being worked with the Pre-Onboarding/PNF Onboarding Use Case, the Wiki can be found here: |
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 | |||||||||||||
| Jira Legacy | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| server | System Jira | SO1: 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:
| ||||||||||
| SO2: Service & NF Instance Association | Associating a xNF to a Service. Seen in the VID UI, after instantiation waiting for registration see only a Service instance, and beyond that a PNF resource instance associated with it. 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. | ||||||||||||
| FUTURE (El Alto) | |||||||||||||
SO-future: Controller Association [FUTURE MOVED TO EL ALTO] | [SDC/SO] The PNF controller caused quite a stir in Casablanca, the tension between Design/Platform Model vs Run-Time/Deployment Model. As a result the SO controller design was sub-optimal and should be addressed in Dublin. | ||||||||||||
| SO4: SO to support updated A&AI PNF schema | [SO] Support of SO for updated AAI PNF instance model. Added March 13th 2019 → AAI team got a recommendation from architecutre committee to defer this item to ONAP/El Alto release. ASSOCIATED DEVELOPMENT: See task A&AI1 and PRH1. JIRA: (Depends on the A&AI work:
| SO
| 797This 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. | ||||||||||||
AAF SECURITY IMPACTS
...
PnP DUBLIN WORK ITEM
...
DESCRIPTION
...
AAF1: Security Enhancement
[AAF] Security enhancements slated for Dublin will need to be working for PnP Use Case. Discussing with DCAE about supporting TLS authentication just with Certificate without Username & Password. If the NF already uses the UN&P for the HTTP connection (that should still work).
Certificate use should be working in Dublin to setup the HTTPS connection.
PROPOSAL: Thus, both Certificate & Username & Password will be supported. (This is suggested for backward compatibility). i.e. there are already existing deployment.
PROPOSAL: It is recommended to use the Certificate.
Certificates as part of the authorization? Subject of the certificate is something that can be used as authorization, the proposal to DCAE is that there is a list of authorized users/subjects. Initially it could be manually configured, but the objective is that this would come from AAF.
Start with Certificates local check: subjects against a list (w/ wildcards). Agree w/ appropriate interface w/ AAF then integrate w/ AAF. If identity not found use basic authentication a second check w/ username & password. otherwise access is rejected (HTTP return code).
SDN-C/R (Controller) IMPACTS
The Controller to PNF service configuration happens in Steps 36 & 37 in the PNF Plug and Play flow (you can read more at the PNF PnP Wiki).
...
PnP DUBLIN WORK ITEM
...
DESCRIPTION
...
CTL1: Controller PNF Interaction
...
[CONTROLLER] Controller definition (SDN-C) came so late in Casablanca, we had defined some additional optional parameter for the step37 Service Configuration but likely more evolution needs to be done. SDN-C was not the theoretical proper controller and people objected as this is conceptually the L0-L3 controller.
[STEP 35-37] - The SO to SDN-C and Controller to PNF exchange (Ansible or NetConf) was a carry-over item from R3. This requires that an API between SO to SDN-C is in place to support this. It requires that SDN-C support the appropriate Ansible Playbook and Directed Graph.
PRH IMPACTS
...
PnP DUBLIN WORK ITEM
...
DESCRIPTION
...
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.
This work is to be covered here:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
A&AI IMPACTS
| DUBLIN ITEM | DESCRIPTION | A&AI1: A&AI pnf-id as INDEX for PNF | |||||||||||||||||||||||
| 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 -
Epic Created: SO Dublin Page: Service Orchestrator Dublin Release |
AAF SECURITY IMPACTS
PnP DUBLIN WORK ITEM | DESCRIPTION | ||||||||||
AAF1: Security Enhancement | [AAF] Security enhancements slated for Dublin will need to be working for PnP Use Case. Discussing with DCAE about supporting TLS authentication just with Certificate without Username & Password. If the NF already uses the UN&P for the HTTP connection (that should still work). Certificate use should be working in Dublin to setup the HTTPS connection. PROPOSAL: Thus, both Certificate & Username & Password will be supported. (This is suggested for backward compatibility). i.e. there are already existing deployment. PROPOSAL: It is recommended to use the Certificate. Certificates as part of the authorization? Subject of the certificate is something that can be used as authorization, the proposal to DCAE is that there is a list of authorized users/subjects. Initially it could be manually configured, but the objective is that this would come from AAF. Start with Certificates local check: subjects against a list (w/ wildcards). Agree w/ appropriate interface w/ AAF then integrate w/ AAF. If identity not found use basic authentication a second check w/ username & password. otherwise access is rejected (HTTP return code). ASSOCIATED DEVELOPMENT: VNFRQTS - Certificate Authentication for HTTPS/TLS -
DCAE Development for Authentication for HTTPS/TLS - |
SDN-C/R (Controller) IMPACTS
The Controller to PNF service configuration happens in Steps 36 & 37 in the PNF Plug and Play flow (you can read more at the PNF PnP Wiki).
PnP DUBLIN WORK ITEM | DESCRIPTION |
CTL1: Controller PNF Interaction | [CONTROLLER] Controller definition (SDN-C) came so late in Casablanca, we had defined some additional optional parameter for the step37 Service Configuration but likely more evolution needs to be done. SDN-C was not the theoretical proper controller and people objected as this is conceptually the L0-L3 controller. [STEP 35-37] - The SO to SDN-C and Controller to PNF exchange (Ansible or NetConf) was a carry-over item from R3. This requires that an API between SO to SDN-C is in place to support this. It requires that SDN-C support the appropriate Ansible Playbook and Directed Graph. Generic API. CDS has its own API to SO. The work being done with the CDS work is re-used for PnP U/C, so no new development needs to be done. ASSOCIATED DEVELOPMENT: (Jira) Controller Design Studio (Design Time) - to customize configuration. This might be used to set the values of parameters that might be send down to a PNF. NetConf - see the NetConf 5G U/C Wiki: 5G - Configuration with NETCONF |
PRH IMPACTS
PnP DUBLIN WORK ITEM | DESCRIPTION | ||||||||||
| 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. PRH shall update A&AI with all fields from pnfRegistration VES event into all corresponding fields of A&AI entry. See the 5G - PNF Plug and Play wiki DEVELOPMENT STATUS:
| ||||||||||
| PRH4: PRH Re-Registration Support | PRH support for the Re-Registration Use Case in PNF PnP (for BBS Nomadic ONT PNF Re-registration Use Case). Which fields to compare in mapping field to determine a reregistration PNF. DEVELOPMENT STATUS:
API CHANGE: New field for event publishing on pnfReady topic & pnfUpdate topic enhanced with additional fields as received in pnfRegistration event (a 1-to-1 copy). Was reviewed & agreed with BBS U/C team and change made in code (continuous integration system). Mar 14, 2019 | ||||||||||
| DEFERED TO EL ALTO | |||||||||||
| PRH1: A&AI New PNF Schema Adaptation | New A&AI schema adaptations: 5G - PNF Plug and Play (Casablanca carry-over items) 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. Added March 13th 2019 → AAI team got a recommendation from architecutre committee to defer this item to ONAP/El Alto release. ASSOCIATED DEVELOPMENT: See task A&AI1 and SO4.
| ||||||||||
| PRH(discuss): Step 37a PNF "Activated" message to ONAP | State Change VES Event (type = State Change) Old state & New State. CPE Authentication Notification BBS U/C is using this flow to "update" ONAP letting ONAP know that the PNF has been successfully been activated. From VES Event Listener Document:
| ||||||||||
A&AI IMPACTS
| DUBLIN ITEM | DESCRIPTION | ||||||||||||||||||||
| 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 | ||||||||||||||||||||
[A&AI] Using the pnf-id (instead of pnf-name) as the index for PNF into A&AI. (discussion started in R3, socialized, Contact: 5G - PNF Plug and Play (Casablanca carry-over items) ). 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:
| |||||||||||||||||||||
VID ENHANCEMENTS
PnP DUBLIN WORK ITEM | DESCRIPTION | ||||||||||||||||||||
VID1: VID Enhancements (Test only) | Confirm the PNF PnP still works with ONAP Dublin UI changes. There was VID GUI changes that happened in R4 Dublin to for new presentation layer with redesign of how VID presentation layer, new layout & buttons. VID displays pages only with certain conditions e.g. only shows PNF if it finds a PNF resource in the service model. HIGH PRIORITY. TESTING STATUS: | ||||||||||||||||||||
| VID3: 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. LOW PRIORITY. | ||||||||||||||||||||
| VID4: Error Cases | ACTION: Error cases (check if SDC model parameters != A&AI PNF entry). LOW PRIORITY. | ||||||||||||||||||||
| DEFERRED TO R5 EL ALTO | |||||||||||||||||||||
| VID2: VID PNF Mgmt. Enhancements | VID A&AI Schema Changes PNF-id vs PNF-name. VID will have to be updated to support the new A&AI Schema change PNF model (PNF-id vs PNF-name). HIGH PRIORITY. PROPOSAL: ASSOCIATED DEVELOPMENT:
| ||||||||||||||||||||
PORTAL IMPACTS
| DUBLIN ITEM | DESCRIPTION | ||||||||
| Impact on Functional Menus | PNF PnP will have a Portal Interface update in R4. Functional menu accessible to any ONAP users from portal. The Portal project provides a seamless user experience when multiple back-end components involved e.g. SDC, VID, A&AI etc When user goes from one component to another e.g. modeling, pnf instance declaration, activation. These provided as functional menus in PORTAL. If a new user doesn't know what the next step is to perform, the PORTAL can recommend the next step via notifications or alerts. DEVELOPMENT STATUS:
ASSOCIATED DEVELOPMENT: More details are here - 5G Usecase Impacts on Portal platform |
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 |
| XTRA3 BSS Work Order Mgmt | WORK ORDER (Optional) – Supporting Work Order. Supported with service specific applications. Inventory systems (optional). Future extension to ONAP. Interface w/ BSS-OSS systems (API). External Application belonging to BSS (of operators IT landscape) |
SDC & PRE/ONBOARDING IMPACTS
Plug and Play has NO IMPACT on SDC (as these are now completely done in PNF Pre-onboarding/onboarding Use Case
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: Wind River Integration Lab, Nokia ONAP Integration Lab
Integration Team Liaison: Marcin Przybysz , Krzysztof Kuzmicki
Resources Needed: Integration team liaison, Test & Integration Dedicated U/C team
Contributing Resources: Nokia
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
Integration Wiki Test Cases: 5G - PNF PnP - Integration Test Cases
Integration Wiki (BBS U/C): The new flow of PnP comes from the Re-registration U/C.
Master Integration Test Page: Dublin Release Integration Testing Status
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 |
|
REQUIREMENTS (VNF-RQTS) IMPACTS
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) DEFERRED TO EL ALTO | ||||||||||||
| AAF1: Security Enhancements | (TLS 1.2 certificates / optional) VNFRQTS - Certificate Authentication for HTTPS/TLS
| SO
| 797)|||||||||||
| 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 |
VID ENHANCEMENTS
...
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)
...
PORTAL IMPACTS
...
PNF PnP will have a Portal Interface update in R4.
Functional menu accessible to any ONAP users from portal.
The Portal project provides a seamless user experience when multiple back-end components involved e.g. SDC, VID, A&AI etc
When user goes from one component to another e.g. modeling, pnf instance declaration, activation. These provided as functional menus in PORTAL.
If a new user doesn't know what the next step is to perform, the PORTAL can recommend the next step via notifications or alerts.
DEVELOPMENT STATUS:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
ASSOCIATED DEVELOPMENT:
More details are here - 5G Usecase Impacts on Portal platform
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
| ||||||||||
| CTL1: Controller - PNF Interaction | (step 37) - Ansible/Netconf to PNF (Requirements will be handled by NetConf U/C)
| ||||||||||
| 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) | ? CP authenticated, triggers registration of PNF & tunnels. PNF (ONT) sends confirmation notification/message, confirms tunnel is setup. 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)