Versions Compared

Key

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

...

PROJECTPTLUser Story / EpicRequirement
A&AI


AAF

APPC


CLAMP

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

Epic #1:

  1. Support NetConfSupport of Parameter x, 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.
  3. (Might be all fully working - might no new development)
DCAE



DMaaP

External API

MODELINGEpic #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



OOFShankaranarayanan Puzhavakath Narayanan

POLICY



PORTAL

SDN-C

SDC

SOEpic #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

VNFRQTS

VNF-SDK

CDS

...

DUBLIN ITEMDESCRIPTION
Model

[Modeling] GeoLocation alignment in Modeling with RFC6225 RFC 6225 and the PNFD, A&AI schema, and SDC AID Data model.

(Sept 5) "Place" object (off of the Root) platform ONAP info-model. GB922 Location standards

Latitude/ Longitude / Altitude (RFC 6225) > GP922 > ONAP > Complex & Place object.

LOW PRIORITY (Nice to have)

...