...
| 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)
| ||||||||
...
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. 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: 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
...
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 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 |
...
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
| 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 |
...