Versions Compared

Old Version 67

changes.mady.by.user Benjamin Cheung

Saved on

compared with

New Version Current

changes.mady.by.user Benjamin Cheung

Saved on

Key

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

...

PROJECTPTLUser Story / EpicRequirement
A&AI

James Forsyth



AAF
Jonathan Gathman



APPC

Takamune Cho



CLAMP

Gervais-Martial Ngueko



CC-SDK

Dan Timoney

Epic#1: Controller to PNF exchange (Epic) STEP 37

Epic #1:

  1. Support NetConf, uses CDS component. W/F in SO. Extended with optional configuration step in SO uses CDS API. wi/ CDS to create blueprint ansible/netconf. CDS south-bound can use different protocols.
  2. Support ONAP communication back to the PNF (via Ansible/Netconf) see Step 37 on the PnP Wiki.
DCAE

Vijay Kumar

Epic #2: Adjust VES collector to SECCOM requirements



Epic #2:

  1. Secure VES collector - make sure client certificate authentication (together with Basic authentication) is default authentication method (according to SECCOM requirements)
  2. Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyDCAEGEN2-1775
DMaaP
Mandar Sawant


External API
Matthieu Geerebaert


MODELING

Hui Deng

Epic #2: Geolocation parameters

Epic #2:

  1. Geolocation information and standards alignment
  2. ETSI SOL001 Alignment
  3. A&AI Schema alignment
  4. Complex object updates

Multi-VIM /

Cloud

Bin Yang


OOFShankaranarayanan Puzhavakath Narayanan

POLICY
Pamela Dragosh



PORTAL
Manoop Talasila


SDN-C
Dan Timoney


SDC

Ofir Sonsino

Epic #6: CDS Integration with SDC (Low priority)

Epic #6: CDS integration with SDC (VF/PNF Resource artifact upload screens) (Best effort)

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDC-2575

SO

Seshu Kumar Mudiganti

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.

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2556

Need to sync on the VID implementation of 5G VID Instantiation/orchestration.
VCPE also wants to use these building blocks.

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-2339

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySO-1838

VID
ittay
Epic #3: SO Building BlocksNeed 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
Steven wright


VNF-SDK

victor gao



List of PTLs: Approved Projects

EPIC / REQ

The Plug and Play Epic for R6 Frankfurt is Jira REQ-134 :

...

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 Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
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

...

SO PNF PNP migration is being documented: https://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/PNF+PnP+workflow+migration+to+Building+Blocks

The JIRA to track progress: https://jira.onap.org/browse/SO-2556.

...

This link is about the current (Dublin + El Alto) implementation: https://wikilf-onap.onapatlassian.orgnet/wiki/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.

...

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





...