...
Wiki to the "Base" PNF Plug and Play Page: 5G - PNF Plug and Play
PRH update handling of Logical Links (move to SO) - introduced in R4 Dublin for BBS/Re-registration Epic
DEVELOPMENT IMPACTS
| PROJECT | PTL | User Story / Epic | Requirement |
| A&AI | |||
| AAF | |||
| APPC | |||
| CLAMP | |||
| CC-SDK | Epic#1: Controller to PNF exchange (Epic) STEP 37 | Epic #1:
|
| DCAE | Epic #2: Adjust VES collector to SECCOM requirements | Epic #2:
| |||||||||||
| DMaaP | |||||||||||||
| External API | |||||||||||||
| MODELING | Epic #2: Geolocation parameters | Epic #2:
| |||||||||||
Multi-VIM / Cloud | |||||||||||||
| OOF | Shankaranarayanan Puzhavakath Narayanan | ||||||||||||
| POLICY | |||||||||||||
| PORTAL | |||||||||||||
| SDN-C | |||||||||||||
| SDC | Epic #6: CDS Integration with SDC (Low priority) | Epic #6: CDS integration with SDC (VF/PNF Resource artifact upload screens) (Best effort)
| |||||||||||
| SO | Epic #3: SO Building Blocks. |
Refactor PBMN workflow. Clean up.
E#3a: Change to the onboarding (definition) of the BPMN workflow. To bring war file with the workflow. E#3b: Migrate existing workflows to existing building blocks.
Need to sync on the VID implementation of 5G VID Instantiation/orchestration.
| ||||||||||||||||||||||||||||
| VID | Epic #3: SO Building Blocks | Need to sync on the VID implementation of 5G VID Instantiation/Orchestration. VCPE also wants to use these building blocks, a fully generic solution is desired here. | ||||||||||||||||||||||||||
| VNFRQTS | ||||||||||||||||||||||||||||
| VNF-SDK |
List of PTLs: Approved Projects
EPIC / REQ
The Plug and Play Epic for R6 Frankfurt is Jira REQ-134 :
| Jira | ||||||||
|---|---|---|---|---|---|---|---|---|
|
DCAE
| Frankfurt Work Item | DESCRIPTION | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| DCAE2: Adjust VES collector to SECCOM requirements | Secure VES collector - make sure client certificate authentication (together with Basic authentication) is default authentication method (according to SECCOM requirements). OPEN: Use Cert w/ border components (not in R6). Modified config of VES collectors option #1/#2. Cnfg "set basicauth" and "noauth" (refactored)
| ||||||||
SO IMPACTS
PNF PnP DUBLIN FRANKFURT WORK ITEM | DESCRIPTION | ||||||||||
| SO1: Building Blocks | Refactor BPMN workflow. Clean up work previously done in R4. Migrate existing workflows to existing building blocks.
Need to sync on the VID implementation of 5G VID Instantiation/orchestration. | ||||||||||
| SO2: Service & NF Instance Association | Associating a xNF to a Service. OPEN: cfg assign/cfg deploy dependent on code being created by other contributors. converted existing PnP WF to make it aligned with R5 need to include cfg steps. (Missing some code). (Open point) DEVELOPMENT STATUS: | SO3: SO support for already existing PNF A&AI entries |
| Jira | ||||||
|---|---|---|---|---|---|---|
|
SO-future: Controller to NF Association
CONTROLLER IMPACTS
Stretch goal in Frankfurt release. |
AssignPnfBB
- Responsibility: Creates PNF entry in A&AI
- Makes a link in AAI between service entry and PNF entry
- currently implemented in CreateAndActivatePnfResource.bpmn
WaitForPnfReadyBB
- Responsibility: Waits for "PNF ready" event sent from PRH to DMaaP
- Currently implemented in CreateAndActivePnfResource.bpmn
ConfigAssignPnfBB
- Responsibility: Runs config assign via CDS
- Currently implemented in ConfigurePnfResource.bpmn
ConfigDeployPnfBB
- Responsibility: Runs config assign via CDS
- Currently implemented in ConfigurePnfResource.bpmn
SO PNF PNP migration is being documented: https://wiki.onap.org/display/DW/PNF+PnP+workflow+migration+to+Building+Blocks
The JIRA to track progress: https://jira.onap.org/browse/SO-2556.
Lukasz Grech and Lukasz Muszkieta (Nokia) are leading the SO changes related to migration of PNF PnP sub-flows (sub-Processes_ to building blocks.
This link is about the current (Dublin + El Alto) implementation: https://wiki.onap.org/display/DW/PNF+PNP+workflow+-+current+implementation
The SO BPMN code can be found at CreateAndActivatePnfResource.bpmn.
This is where the implementation is stored today.
Also refer to the following topic in Gerrit: pnf_bb
https://gerrit.onap.org/r/#/q/status:merged+project:so+branch:master+topic:pnf_bb
This is where other changes expected for the PNF PnP BBs are expected to be added.
A few building blocks will be created in R6 (expected by end of February 2020).
The currently available workflows dealing for PNF PnP can be seen at the PNF PnP test-cases descriptions in the ONAP Integration project.
VID IMPACTS
| R6 ITEM | DESCRIPTION |
|---|---|
VID1 Migration of Sub-worksflows (Post-poned to R7) | Migration of existing PNF PnP sub-workflows to a new BB approach (probably we will be creating 4-5 new BBs). VID Impact: Within “old” VID macro orchestration pages, a special field to provide a pnf-id parameter (shall be actually called “correlationID” or “PNF correlationID”) has been displayed under the following conditions:
When we migrate to BB approach, we`d keep the possibility to provide this parameter (PNF correlationID) to the SO API call as input. How this will change with SO/BB approach, and with new VID GUI targeted at macro (GR) flows – we`d see exactly, after we execute some tests with new VID UI, and updated SO PNF BB code. In R6: only accessible via SO API not the VID GUI, E2E tests prepare environment cover case w/ SO API. |
CONTROLLER IMPACTS
PnP R6 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 R6 Frankfurt Work Item | DESCRIPTION |
|---|---|
BBS Event Processing Micro-Service
PnP R6 Frankfurt WORK ITEM | DESCRIPTION | ||||||||
PRH(discuss): Step 37a PNF "Activated" message to ONAP BBS event processing micro-service. (Being done by the BBS U/C team) Post-poned to Rx | 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:
R6 - No Changes. BBS will test what was there, will do re-test in R6. |
A&AI IMPACTS
| DUBLIN R6 ITEM | DESCRIPTION |
| 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 / Model MODELING | [A&AI] GeoLocation information for the PNF reported via pnfRegistration VES Event This will ONLY be modeling work in R6, functionality it moved to future release MODELING WORK ONLYLOW PRIORITY (Nice to have) |
A&AI4: A&AI pnf-id as INDEX for PNF CANCELED | [A&AI] New A&AI schema adaptations: discrepancy between PNFs and VNFs; VNFs are identified via VNF-ID (UUID), and PNFs - via PNF-name. PNF-id should be used for Identities. This differentiates the way that PRH is searching for PNFs in A&AI, when PRH does the PNF registration in A&AI (may also require SO change). July 31th 2019 → AAI team has cancelled this request (redacted). CANCELED |
MODEL IMPACTS
| DUBLIN R6 ITEM | DESCRIPTION |
| Model | [Modeling] GeoLocation alignment in Modeling with RFC 6225 and the PNFD, A&AI schema, and SDC AID Data model. (Sept 5) "Place" object (off of the Root) platform ONAP info-model. GB922 Location standards Latitude/ Longitude / Altitude (RFC 6225) > GP922 TMF GB922 > ONAP > Complex & Place object. LOW PRIORITY (Nice to have) |
SUPPORTING FILES & PRESENTATIONS
| Presentation | File | ||||||
|---|---|---|---|---|---|---|---|
Presentation for Epic #4: Secure Communication between xNFs & ONAP |
| ||||||
| Slides for SO work (Generic SO BBs for PNFs) |
| ||||||
Presentation given at the DDF (Prague Jan 13-16) https://wiki.lfnetworking.org/pages/viewpage.action?pageId=25364127 |
| ||||||
MEETINGS & RECORDINGS
| DATE | TOPIC | WIKI |
|---|---|---|
| Discussion of Geolocation / PNFD/ Civic Address parameters | PNF: PnP - PNFD/SDC AID/AAI Schema Modeling - for GeoLocation |
...
| Discussion of Modeling | PNF: PnP - PNFD/SDC AID/AAI Schema Modeling - for GeoLocation Discussion Sept 5 2019 |
| Discussion of Civic Address / Place-Location Model | PNF: PnP - PNFD/SDC AID/AAI Schema Modeling - Discussion Oct 3 2019 |
| Presentation of Place concept Model | PNF: PnP - PNFD/SDC AID/AAI Schema Modeling - |
...
| Discussion Nov 7, 2019 | ||
| Discussion of 5G Service Model analysis from 3GPP TS28.541 | PnP - PNFD/SDC AID/AAI Schema Modeling - Discussion Dec 12, 2019 |
| Review of Items | PnP - PNFD/SDC AID/AAI Schema Modeling - Discussion Jan 2, 2020 |
| Team discussion | PNFD/SDC AID/AAI Schema Modeling - Discussion Mar 26, 2020 |
| Complex Model Analysis , Discussion of PNF Place as use of Complex for PNFs | PNFD/SDC AID/AAI Schema Modeling/5G Svc Model - R7 Discussion |
| Discussion with Thinh | PNFD/SDC AID/AAI Schema Modeling - Discussion Apr 9, 2020 |
REFERENCES
| Jira | ||||||||
|---|---|---|---|---|---|---|---|---|
|
INTEGRATION & TESTING
This section discusses the Testing & Integration for R6 PnP
- WHO IS TESTING - what company, team, and people will be doing the testing & responsibilities for testing.
- TEST ENVIRONMENT - which does the lab & test environment.
- RESOURCES NEEDED - what resources are needed.
- WHO IS CONTRIBUTING RESOURCES - what resources will be provided and by whom/what company.
- NETWORK CONNECTIVITY - How will a PNF make connectivity to ONAP DCAE VES Event Listener
- TEST/INTEGRATION LEADER - Marcin Przybysz
- INTEGRATION LEAD DEFINITION - ONAP "Use Case/Requirement" Integration Lead
PNF PnP Integration Test Cases. These can be navigated to from the Integration team page hierarchy.
5G - PNF PnP - Integration Test Cases
Testing Status
Dublin 5G - PNF PnP - Test Status
Release R6 Integration Status Page:
2: Frankfurt Release Integration Testing Status
TEST & INTEGRATION
| Topic | Wiki |
|---|---|
| PNF PnP Integration Test Cases | 5G - PNF PnP - Integration Test Cases |
| Testing Status | Dublin 5G - PNF PnP - Test Status |
| R6 Integration Status Page | 2: Frankfurt Release Integration Testing Status |
DEMOS
| Demo | File/Recording | ||||||
|---|---|---|---|---|---|---|---|
ONAP/ ORAN Plugfest Demo for Plug and Play (Brunswick NJ - Rutgers OWL WinLab) |
| ||||||
ONAP/ ORAN Plugfest Slides for Plug and Play Presented at ONAP Plugfest
|
| ||||||