...
| PROJECT | PTL | User Story / Epic | Requirement |
| A&AI | |
|
|
| AAF | | Epic #4 Secure PnP (just a dependency) Functionality will be developed in separate release requirement | Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | REQ-140 |
|---|
|
| Epic #4: - CMPv2 Client implementation so that ONAP platform components can get operator certificates.
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | AAF-994 |
|---|
|
- Ensure AAF provides interface allowing DCAE to deploy extra client certificate for external communication
| APPC | | CLAMP | |
| CC-SDK | | Epic#1: Controller to PNF exchange (Epic) STEP 37 | Epic #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.
- Support ONAP communication back to the PNF (via Ansible/Netconf) see Step 37 on the PnP Wiki.
|
|
|
| APPC | |
|
|
| CLAMP | |
|
|
| CC-SDK | | Epic#1: Controller to PNF exchange (Epic) STEP 37 | Epic #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.
- Support ONAP communication back to the PNF (via Ansible/Netconf) see Step 37 on the PnP Wiki.
|
| DCAE | | Epic #2: Adjust VES collector to SECCOM requirements
| Epic #2: - Secure VES collector - make sure client certificate authentication (together with Basic authentication) is default authentication method (according to SECCOM requirements)
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | DCAEGEN2-1775 |
|---|
|
|
| DMaaP | |
|
|
| External API | |
|
|
| MODELING | | Epic #2: Geolocation parameters | Epic #2: - Geolocation information and standards alignment
- ETSI SOL001 Alignment
- A&AI Schema alignment
- Complex object updates
|
Multi-VIM / Cloud | |
|
|
| OOF | Shankaranarayanan Puzhavakath Narayanan |
|
|
| POLICY | | |
|
| PORTAL | |
|
|
| SDN-C | |
|
|
| SDC | | Epic #6: CDS Integration with SDC (Low priority) | Epic #6: CDS integration with SDC (VF/PNF Resource artifact upload screens) (Best effort | DCAE | | ____________________________ Epic #2: Adjust VES collector to SECCOM requirements Epic #1: - CMPv2 for operator certificate enrollment for VES Collector to correctly handle pnfRegistration event.
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | DCAEGEN2-1794 |
|---|
|
_________________________________ Epic #2: Secure VES collector - make sure client certificate authentication (together with Basic authentication) is default authentication method (according to SECCOM requirements |
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | DCAEGEN2-1775 |
|---|
DMaaP | | External API | | | MODELING | | Epic #2: Geolocation parameters | Epic #2: - Geolocation information and standards alignment
- ETSI SOL001 Alignment
- A&AI Schema alignment
- Complex object updates
|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | SDC-2575 |
|---|
|
|
| SO | | 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 |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | SO-2556 |
|---|
|
Need to sync on the VID implementation of 5G VID Instantiation/orchestration.
VCPE also wants to use these building blocks. | Jira |
|---|
| server | ONAP JIRA |
|---|
| columns | key, |
|---|
|
| Multi-VIM / Cloud | | OOF | Shankaranarayanan Puzhavakath Narayanan | POLICY | | PORTAL | | SDN-C | | SDC | | Epic #6: CDS Integration with SDC (Low priority) | Epic #6: CDS integration with SDC (VF/PNF Resource artifact upload screens) (Best effort) | Jira |
|---|
| server | ONAP JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | SDC-2575 |
|---|
|
| SO | | Jira |
|---|
| server | ONAP JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | SO-1838 |
|---|
|
|
| VID | | Epic #3: SO Building Blocks.E#3a: | Change Need 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 |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | SO-2556 |
|---|
|
Need to sync on the VID implementation of 5G VID Instantiation/orchestration.
VCPE also wants to use these building blocks. | Jira |
|---|
| server | 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 | |
|
|
| VNF-SDK | |
|
|
List of PTLs: Approved Projects
EPIC / REQ
The Plug and Play Epic for R6 Frankfurt is Jira REQ-134 :
| Jira |
|---|
| server | ONAP JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key |
|---|
|
...
...
...
DCAE
| Frankfurt Work Item | DESCRIPTION |
|---|
| 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) |
| server | ONAP JIRA |
|---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | | serverId | 425b2b0a-557c-3c0c-b515 |
|---|
|
|
-579789cceedb| key | SO-1838 |
|---|
| VID | | Epic #3: SO Building Blocks | Need 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 | | VNF-SDK | | List of PTLs: Approved Projects
EPIC / REQ
The Plug and Play Epic for R6 Frankfurt is Jira REQ-134 :
| Jira |
|---|
| server | ONAP JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | REQ-134 |
|---|
|
DCAE
...
DCAE1: Secure PnP
...
CMPv2 for operator certificate enrollment for VES Collector to correctly handle pnfRegistration event.
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | DCAEGEN2-1794 |
|---|
|
| -579789cceedb | | key | DCAEGEN2-1775 |
|---|
|
|
...
Secure VES collector - make sure client certificate authentication (together with Basic authentication) is default authentication method (according to SECCOM requirements)
| Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | DCAEGEN2-1775 |
|---|
|
AAF
| 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
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 |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | SO-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. DEVELOPMENT STATUS: Stretch goal in Frankfurt release. |
...
| Presentation | File |
|---|
Presentation for Epic #4: Secure Communication between xNFs & ONAPSecure Communication between xNFs & ONAP | | View file |
|---|
| name | 2019-09-24 ONAP_Secure_Communication_PNF_PnP_R6.pptx |
|---|
| height | 250 |
|---|
|
|
Slides for SO work
(Generic SO BBs for PNFs) | | 2019-09-24 ONAP_Secure_Communication_PNF_PnP_R6.pptx | | PNF PnP as Building Blocks-v24-20191203_115837.pdf | | height | 250 |
|---|
|
|
|
| height | 250 |
|---|
Slides for SO work
(Generic SO BBs for PNFs) | | View file |
|---|
| name | PNF PnP as Building Blocks-v24-20191203_115837.pdfSO - deploying custom BPMN workflows (with code).pptx |
|---|
| height | 250 |
|---|
|
|
|
|
MEETINGS & RECORDINGS
...
