| PROJECT | PTL | User Story / Epic | Requirement |
| A&AI | |
|
|
| AAF | | Epic #4 Secure PnP Functionality will be developed in separate release requirement | Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | REQ-140 |
|---|
|
| Epic #4: - Implementation (or use of) CMPv2 Client implementation so that ONAP platform components can get operator certificates.
- 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.
- (Might be all fully working - might no new development)
|
| DCAE | | Epic #4 Secure PnP
Epic #5: Refactor Tests for DCAE-SDK DMaaP-Client | Epic #4: - CMPv2 for operator certificate enrollment for VES Collector to correctly handle pnfRegistration event.
Epic #5: Refactor Tests for DCAE-SDK DMaaP-Client | Jira |
|---|
| server | ONAP JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | DCAEGEN2-1773 |
|---|
|
|
| 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 | |
|
|
| 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. | Jira |
|---|
| server | ONAP JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | SO-2339 |
|---|
|
| 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 | Need to sync on the VID implementation of 5G VID Instantiation/orchestration. VCPE also wants to use these building blocks. |
| VNFRQTS | |
|
|
| VNF-SDK | |
|
|
| CDS | Yuriy Malakov | Epic #6: CDS Integration with SDC | Epic #6: CDS integration with SDC (VF/PNF Resource artifact upload screens) | 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 |
|---|
|
|
