...
| Table of Contents | ||
|---|---|---|
|
Overview
| Logging | Logging | Project Name | Enter the name of the project |
|---|---|---|---|
| Target Release Name | Enter the name of the release you are targeting to deliverDublin | ||
| Project Lifecycle State | Either Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information | ||
| Participating Company List | the company participating in this release. At least 3-4 organizations, including an operator are recommended.Amdocs, AT&T, Bell |
Scope
What is this release trying to address?
Describe the problem being solved by this release
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
Minimum Viable Product
Logging related collection, shipping, indexing, storage, searching, display. And S3P performance, scaling, resiliency of the ELK stack and filebeat infrastructure.
Additional stretch goals is a pluggable common ELK chart.
Adjusting the POMBA audit API.
Use Cases
Log collection and triage of any ONAP supported use case transaction for vFW, vDNS, vVOLTE or vCPE
(POMBA) audit of any of the above use case transactions for the purposes of out of band model based audit.
Minimum Viable Product
ELK + Prometheus stack functions
POMBA stack functionsDescribe the MVP for this release.
Functionalities
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
...
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
| Jira | ||||||
|---|---|---|---|---|---|---|
|
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
...