Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Frankfurt Work ItemDESCRIPTION
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)

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-1775



...

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.

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keySO-2556

Need to sync on the VID implementation of 5G VID Instantiation/orchestration.
VCPE also wants to use these building blocks, but a fully generic solution is desired and targted.

 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. 

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.

Image RemovedImage Added


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 ITEMDESCRIPTION

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:

  1. Service Model contains a PNF resource type.

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.
We`d have to check, what capabilities and conditions could be applied to display and process this “PNF Correlation ID parameter”.

Can the same BBs could be re-used in “standard” vCPE use-case.
We`re looking at a generic solution, and we`d probably display this additional field, when we figure out, that there is a PNF resource used in a Service Model.

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:

newState

string

Yes

New state of the entity: ‘inService’, ‘maintenance’, ‘outOfService’

oldState

string

Yes

Previous state of the entity: ‘inService’, ‘maintenance’, ‘outOfService’


R6 - No Changes. BBS will test what was there, will do re-test in R6.


A&AI IMPACTS

R6 ITEMDESCRIPTION
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

...

DATETOPICWIKI

 

Discussion of Geolocation / PNFD/ Civic Address parametersPNF: PnP - PNFD/SDC AID/AAI Schema Modeling - for GeoLocation

 

Discussion of ModelingPNF: 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.541PnP - PNFD/SDC AID/AAI Schema Modeling - Discussion Dec 12, 2019

 

Review of ItemsPnP - 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 PNFsPNFD/SDC AID/AAI Schema Modeling/5G Svc Model - R7 Discussion

 

Discussion with ThinhPNFD/SDC AID/AAI Schema Modeling - Discussion Apr 9, 2020




REFERENCES

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-1775

...

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

TopicWiki
PNF PnP Integration Test Cases5G - PNF PnP - Integration Test Cases
Testing StatusDublin 5G - PNF PnP - Test Status
R6 Integration Status Page2: Frankfurt Release Integration Testing Status

DEMOS

DemoFile/Recording

ONAP/ ORAN

Plugfest Demo for Plug and Play

(Brunswick NJ - Rutgers OWL WinLab)

View file
namezoom_4.mp4
height150

ONAP/ ORAN

Plugfest Slides for Plug and Play

Presented at ONAP Plugfest

 

View file
namePNF-PlugandPlay_201912Dc05v2.pptx
height250





...