Versions Compared

Old Version 18

changes.mady.by.user Benjamin Cheung

Saved on

compared with

New Version 19

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)

Epic #1:

  1. Support NetConf
  2. Support of Parameter x
DCAE

Vijay Venkatesh Kumar



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



SO

Seshu Kumar Mudiganti

Epic #3: SO Building Blocks.

Refactor PBMN workflow. Clean up.

Migrate existing workflows to existing building blocks.

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

VID
Ittay Stern


VNFRQTS
Steven Wright


VNF-SDK
Weitao Gao


CDS

Yuriy Malakov



...

PnP DUBLIN WORK ITEM

DESCRIPTION

SO1: Building Blocks

Refactor PBMN 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. VCPE also wants to use these building blocks.

 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. 

DEVELOPMENT STATUS:


SO3: SO support for already existing PNF A&AI entries

[SO] Support of SO for an already existing PNF (active) A&AI Entry

(use case with a deleted & recreated service or instantiating 2nd service using the same PNF)
Within ONAP/Beijing - In Step #19B SO would exit and service creation would continue

DEVELOPMENT STATUS:

In ONAP/Casablanca this was updated, and irrespective of AAI entry existence for a PNF instance, the workflow execution always waits to receive a PNF registration event.

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

This is not planned to be changed in ONAP/Dublin release.

SO-future: Controller to NF Association


[SDC/SO] The PNF controller caused quite a stir in Casablanca, the tension between Design/Platform Model vs Run-Time/Deployment Model. As a result the SO controller design was sub-optimal and should be addressed in Dublin.

...