...
The content of this template is expected to be fill out for M1 Release Planning Milestone .
| Info | ||
|---|---|---|
| ||
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki. |
- due 27 June via Release Planning
| 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.
...
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
Spec level integration with Acumos to allow cross platform transaction triage.
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
https://jira.acumos.org/browse/ACUMOS-710
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
Release Components Name
Components Name | Components Repository name | Maven Group ID | Maven Artifact ID | Java package name | Components Description |
|---|---|---|---|---|---|
Components Name | Components Repository name | Maven Group ID | Maven Artifact ID | Java package name | Components Description |
| logging-analytics | logging-analytics | org.onap.logging-analytics | logging-analytics | org.onap.logging | A reference analytics pipeline configuration |
| pomba-context-aggregator | logging-analytics/pomba/pomba-context-aggregator | org.onap.pomba | pomba-context-aggregator | org.onap.pomba.context.aggregator | Orchestrates calls to various context builders and aggregates data from various data sources into one single payload |
| pomba-aai-context-builder | logging-analytics/pomba/pomba-aai-context-builder | org.onap.pomba | pomba-aai-context-builder | org.onap.pomba.contextbuilder.aai | AAI Context builder. Interacts with A&AI and transforms A&AI data into common model structure |
| pomba-sdc-context-builder | logging-analytics/pomba/pomba-sdc-context-builder | org.onap.pomba | pomba-sdc-context-builder | org.onap.pomba.contextbuilder.sdc | SDC Context builder. Interacts with SDC and transforms SDC TOSCA CSAR into common model structure |
| pomba-sdnc-context-builder | logging-analytics/pomba/pomba-sdnc-context-builder | org.onap.pomba | pomba-sdnc-context-builder | org.onap.pomba.contextbuilder.sdnc | SDN-C Context Builder. Interacts with SDN-C and transforms SDN-C data into common model structure |
| pomba-network-discovery-context-builder | logging-analytics/pomba/pomba-network-discovery-context-builder | org.onap.pomba | pomba-network-discovery-context-builder | org.onap.pomba.contextbuilder.networkdiscovery | Network Discovery Context Builder. Interacts with Network discovery component and transforms its data into common model structure |
| pomba-audit-common | logging-analytics/pomba/pomba-audit-common | org.onap.pomba | pomba-audit-common | org.onap.pomba.common.audit | POJO project. Holds POMBA common model POJO representation |
Resources committed to the Releaseb
Architecture
High level architecture diagram
...
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Performance | 1 | 2 | address logstash and elasticsearch scaling
|
| ||||||||||||||||
| Stability | 2 | 3 |
|
| ||||||||||||||||
| Resiliency | 2 | 2 |
|
| ||||||||||||||||
| Security | 1 | 2 |
|
| ||||||||||||||||
| Scalability | 1 | 1 |
|
| ||||||||||||||||
| Manageability | 1 | 2 |
| |||||||||||||||||
| Usability | 1 | 2 |
|
...
List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | |
|---|---|---|---|---|---|
| To fill out | High level description of the APIPOMBA Audit Inititiation | API to inititiate POMBA Audit | Date for which the API is reviewed and agreed | To fill outLink toward the detailed API description | |
| POMBA Context Builders | API that must be supported by all Context Builders | POMBA Context Builder Swagger |
Third Party Products Dependencies
Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).
| Name | Description | Version |
|---|---|---|
| To fill out | To fill out | To fill out |
...
| ElasticSearch | ES is part of the ELK stack | 5.5.0 - will upgrade to 5.6.0 |
| Logstash | LS is part of the ELK stack | 5.5.0 - will upgrade to 5.6.0 |
| Kibana | KB is part of the ELK stack | 5.5.0 - will upgrade to 5.6.0 |
Testing and Integration Plans
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| To fill out | To fill out | To fill out |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...