...
PROJECT | PTL | User Story / Epic | Requirement | ||||||||||||||||||||||||||||
A&AI | |||||||||||||||||||||||||||||||
AAF | Epic #4 Secure PnP (just a dependency) Functionality will be developed in separate release requirement
| Epic #4:
| |||||||||||||||||||||||||||||
APPC | |||||||||||||||||||||||||||||||
CLAMP | |||||||||||||||||||||||||||||||
CC-SDK | Epic#1: Controller to PNF exchange (Epic) STEP 37 | Epic #1:
| |||||||||||||||||||||||||||||
DCAE | Epic #1: Secure PnP
____________________________ Epic #2: Adjust VES collector to SECCOM requirements | Epic #1:
Epic #1:
_________________________________ 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. | 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 |
...
The Plug and Play Epic for R6 Frankfurt is Jira REQ-134 :
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
...
PNF PnP 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. DEVELOPMENT STATUS: Stretch goal in Frankfurt release. |
AssignPnfBB
...
PnP R6 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
...
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 ONLY |
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 |
...
SUPPORTING FILES & PRESENTATIONS
Presentation | File | ||||||
---|---|---|---|---|---|---|---|
Presentation for Epic #4: Secure Communication between xNFs & ONAP |
| ||||||
Slides for SO work (Generic SO BBs for PNFs) |
| ||||||
...
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 |
| ||
REFERENCES
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
...
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
|
| ||||||
...