...
PROJECT | PTL | User Story / Epic | Requirement |
A&AI | |||
AAF | Epic #4 Secure PnP | Epic #4:
| |
APPC | |||
CLAMP | |||
CC-SDK | Epic#1: Controller to PNF exchange (Epic) STEP 37 | Epic #1:
| |
DCAE | Epic #4 Secure PnP | Epic #4:
| |
DMaaP | |||
External API | |||
MODELING | Epic #2: Geolocation parameters | Epic #2:
| |
Multi-VIM / Cloud | |||
OOF | Shankaranarayanan Puzhavakath Narayanan | ||
POLICY | |||
PORTAL | |||
SDN-C | |||
SDC | |||
SO | 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 | |||
VNFRQTS | |||
VNF-SDK | |||
CDS |
List of PTLs:Approved Projects
AAF
PnP Frankfurt Work Item | Description |
---|---|
Secure pnfRegistration | Introduction of Secure Communications with CMPv2. 3GPP PnP operator certificate (to DCAE) before it sends pnfRegistration event. Not on DCAE-side. Setup ONAP system have to have root CA, CA chain from the CAs that issue NF certificates. you get DCAE component Certificate signed by local AAF/CA. DCAE doesn't use AAF directly, DCAE component uses its own init container to get certs. NetConf over TLS will use CMPv2. External border components (DCAE, Controllers) need real certificates, which they don't have right now. This will be developed in R6. ONAP platform Containers / Prepare system to upload certificates manually. Need automatic way to get operator certificates through CMPv2 client. Plug-in to AAF to get certificates, how are these distributed to other ONAP components. Need trust chain. Can't do this manually with 100s of instances. Don't have a factory certificate w/ inherent identifier. PNFs scope. DCAE components need to get operator certificates. COMPONENTS: DCAE, AAF. |
SO IMPACTS
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) 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.
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. |
...