Versions Compared

Old Version 6

changes.mady.by.user cl664y@att.com

Saved on

compared with

New Version Current

changes.mady.by.user Pawel Baniewski

Saved on

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

James Forsyth



AAFNo active PTL

CMPv2 CertService small enhancements (

CMPv2 over HTTPS support;

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

Takamune Cho



CLAMP

Gervais-Martial Ngueko



CC-SDK (incl. CDS)

Dan Timoney



DCAE

Vijay Kumar

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
Mandar Sawant



External API

Adrian OSullivan



MODELING

Hui Deng



Multi-VIM /

Cloud

Bin Yang


OOF

Shankaranarayanan Puzhavakath Narayanan



POLICY
Pamela Dragosh


PORTAL
Manoop Talasila


SDN-C
Dan Timoney


SDC

Ofir Sonsino



SO

Seshu Kumar Mudiganti



VID
ittay


VNFRQTS

Trevor Lovett



VNF-SDK
victor gao


List of PTLs:Approved Projects

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

...

Use Case Functional Definitions

A list of conditions that are assumed to be true before the Use Case is invoked

Includes description of Information Consumed

Use Case Title

Title of the Use CaseCertificate Management Protocol (CMPv2) in Guilin release

Actors (and System Components)

The list of Actors and System Components that participate in the Use Case

Description

Short overview of the Use CaseDCAE collectors, AAF CertService (CMPv2), CMPv2 server

Description

Protect traffic between Network Functions and DCAE collectors by using certificate from CMPv2 server

Points of Contact

Authors and maintainers of the Use Case.

Use Case Lead, Key Use Case members and code contributors.

Preconditions

Pawel Baniewski

Bogumil Zebek

Kornel Janiak

damian.nowak

Preconditions

CMPv2 integration switched on:

  • AAF CertService deployed by OOM installation
  • CMPv2 server present (can be a testing one – EJBCA)

Triggers / Begins when

Describes the trigger for beginning the Use CaseDCAE collector startup


Steps / Flows (success)

Describes the sequence of steps and interactions that occur during the Use Case (may include: description, data exchanges, functionality, state changes)

Interaction diagrams may be included or referenced

Post-conditions

The expected results of the execution of the Use Case

Includes description of Information Produced

  1. DCAE collector startup
  2. Call to AAF CertService to enroll certificate from CMPv2 server
  3. Certificate from CMPv2 server taken into use by DCAE collector

Post-conditions

DCAE collector presents certificate acquired from CMPv2 server when Network Functions are communicating with it

Alternate / Exception Paths

Description of any exceptions or special process that could occur during Use Case (question)

Related Use Cases

List of the Use Cases referenced by this Use Case (question)

Assumptions

Describes any assumptions that are made for this use case (question)

Tools / References / Artifacts

List of any tools or reference material associated with this Use Case as well as any JIRA trace-ability.

List of any associated diagrams or modelling artifacts associated with the Use Case (question)

Testing

Current Status

  1. Testing Blockers

  2. High visibility bugs
  3. Other issues for testing that should be seen at a summary level
  4. Where possible, always include JIRA links

...