Thx
Use Case Name
| Topic | Description | Item | ||||||||
| REQ 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. |
M4 status:
| ||||||||
Cert Service client part of OOM project NRM = closer to K8S vuln. changes in VES collector. Performance Tests. | ||||||||||
| Architecture Sub-committee Jira |
| tracker |
|
NON FUNCTIONAL REQUIREMENT CONTRIBUTION
| COMPONENT | U/C STORY JIRA | NFR JIRA | COMPANY | DESCRIPTION | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| DCAE |
|
|
| Nokia |
| ||
BUSINESS DRIVER
This section describes Business Drivers needs.
...
Organization Mgmt, Sales Strategies - (It is suggested that you use the following wording): There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. (This would typically describe the "WHO", but because use cases are all deployed with ONAP itself, these two areas come with the actual ONAP deployment and uses the organizational management and sales strategies of a particular service provider's ONAP deployment)
Development Status
| PROJECT | PTL | User Story / Epic | Requirement |
| A&AI | |||
| AAF | No 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
...
Use Case Functional Definitions
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 | A list of conditions that are assumed to be true before the Use Case is invoked Includes description of Information Consumed | ||
Triggers / Begins when | Describes the trigger for beginning the Use Case | ||
Preconditions | CMPv2 integration switched on:
| ||
Triggers / Begins when | DCAE 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 | ||
| |||
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 | ||
Related Use Cases | List of the Use Cases referenced by this Use Case | ||
Assumptions | Describes any assumptions that are made for this use case | ||
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 |
Testing
Current Status
Testing Blockers
- High visibility bugs
- Other issues for testing that should be seen at a summary level
- Where possible, always include JIRA links
...