...
The content of this template is expected to be fill out for M1 Release Planning Milestone .20180613- due 27 June via Release Planning
20180620_ still filling out - Michael O'Brien
...
| Table of Contents | ||
|---|---|---|
|
Overview
| Project Name | Enter the name of the projectLogging | Logging |
|---|---|---|
| Target Release Name | Enter the name of the release you are targeting to deliverCasablanca | |
| 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?
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.
Adding the POMBA audit seed code.
Use Cases
Describe the Log collection and triage of any ONAP supported use case this release is targeted for (better if reference to customer 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
Describe the MVP for this release.ELK stack functions
POMBA stack functions
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.
...