Versions Compared

Key

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


Thx

Use Case Name

TopicDescriptionItem
REQ Jira
Requirement Jira

REQ-321 CMPv2 Enhancements for R7

REQ-321 is for DCAE project, to integrate with AAF/CertService components created during the ONAP/Frankfurt release.

Actually, we don`t expect to do changes in AAF/CertService to support that requirement, worst case we might find a bug in the AAF/CertService implementation, which would have to be fixed.

There is a potential dependency -> if we find bugs in CertService. If we do so, we`d be able to fix them without touching the rest of AAF code, as CertService is completely independent from other components of AAF (it simply lives in AAF project, but it could live anywhere else too).

We can do relevant documentation/release note changes for AAF/CertService, if any bugs will be found and fixed.


Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-321

M4 status:

  • Moving CMPv2 from DCAE AAF to OOM repo ongoing
  • DCAE platform (BP-generator + K8s plugin) work done
  • New CMPv2 tools (truststore merger) implementation done
  • New CMPv2 tools (keystore copier) implementation ongoing
  • DCAE components (VES + HV-VES) integration with CMPv2 ongoing – blocked by bug https://jira.onap.org/browse/AAF-1121
    • Bug resolution ongoing
  • DCAE components (DFC + RestConf) integration with CMPv2 moved to Honolulu release

Cert Service client part of OOM project

NRM = closer to K8S vuln. changes in VES collector. Performance Tests.


Architecture Sub-committee Jira tracker

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyONAPARC-575

NON FUNCTIONAL REQUIREMENT CONTRIBUTION

COMPONENTU/C STORY JIRANFR JIRACOMPANYDESCRIPTION
DCAE

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-2250

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-351

Nokia
  • Java 11 update: Inventory API
  • Java 11 update: runTime API





BUSINESS DRIVER

This section describes Business Drivers needs.

...

PROJECTPTLUser Story / EpicRequirement
A&AI


AAFNo active PTL

CMPv2 CertService small enhancements (configurable artifacts output type) and introduction of new API to update certificates (best effort)

Actually, we don`t expect to do changes in AAF/CertService to support that requirement, worst case we might find a bug in the AAF/CertService implementation, which would have to be fixed.

There is a potential dependency -> if we find bugs in CertService. If we do so, we`d be able to fix them without touching the rest of AAF code, as CertService is completely independent from other components of AAF (it simply lives in AAF project, but it could live anywhere else too).

We can do relevant documentation/release note changes for AAF/CertService, if any bugs will be found and fixed.


APPC


CLAMP

CC-SDK (incl. CDS)

DCAE

Integration of DCAE collectors with certificates from CMPv2 server to protect external communication - details DCAE CertService integration;

Certificate from CMPv2 server exposed to xNFs


DMaaP



External API

MODELING

Multi-VIM /

Cloud



OOF

POLICY

PORTAL

SDN-C

SDC

SO

VID

VNFRQTS

VNF-SDK

List of PTLs:Approved Projects

*Each Requirement should be tracked by its own User Story in JIRA 

...