LOG M1 Beijing Release Planning
WIP: DRAFT PROPOSAL FOR COMMENTS
The content of this template is expected to be fill out for M1 Release Planning Milestone.
follow
Platform Maturity Requirements (aka Carrier Grade)
fill Beijing Release Platform Maturity
Info
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
Use the Wiki to document the release plan. Don't provide PowerPoint.
Use as much diagrams and flow charts as you need, directly in the wiki, to convey your message.
Overview
Project Name | Enter the name of the project |
|---|---|
Target Release Name | Beijing |
Project Lifecycle State | Incubation |
Participating Company | Amdocs, AT&T, Bell |
Scope
What is this release trying to address?
Provide an ELK implementation for ONAP as described on https://kubernetes.io/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana/
https://lf-onap.atlassian.net/browse/LOG-89
https://lf-onap.atlassian.net/browse/LOG-95
Use Cases
Use Case: Residential Broadband vCPE (Approved)
Minimum Viable Product
The MVP for Amsterdam will:
Functionalities
Epics
Stories
Longer term roadmap
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
Deliverable Name | Deliverable Description |
|---|---|
Revised logging guidelines | Updates to What's New - ONAP Application Logging Guidelines reflecting new conventions and requirements. |
Logging provider configuration defaults | Regularized configuration locations, simplifying deployment and customization. |
Logging provider output defaults | Regularized output locations, simplifying deployment and customization, and the shipping and indexing of logs. |
Logging provider migration | Optional standardization of logger providers, including upgrading from EOL Log4j 1.X. |
Updated logging provider configuration(s) | Updated, standardized configurations for all logging providers and ONAP components - specific to OOM in the OOM repo. |
Filebeat configuration | Reference configuration for Elastic Stack Filebeat shipping. |
Logstash configuration | Reference configuration for Elastic Stack Logstash indexing. |
Elasticsearch configuration | Reference configuration for Elastic Stack Elasticsearch. |
Kibana configuration | Reference configuration for Elastic Stack's Kibana Discover UI. |
Elastic Stack deployment | Automated OOM deployment of an Elastic Stack reference configuration, providing ONAP with an OOTB analytics platform. |
Documentation | Other documentation supporting analytics configuration. |
Sub-Components
none
Reviewing from Jason's presentation TSC 20170104 - OSX - works fine
We can follow the level 1 and desired level 2 as guidelines on our overall requirements for M1 in Beijing - which align with the work started in Amsterdam.
TSC 2018-01-04
Req 1 - single logging system across ONAP
Req 2 - Transaction tracing across ONAP components
Contributions
AT&T feedback on carrier grade requirements (Lee Breslau) @Lee Breslau
•Transaction tracing is more important than the ability to instantiate in less than an hour
•Suggested revision of levels:
•0 – All ONAP components use a single logging system
•1 – Transaction tracing across components; Instantiation in less than 4 hours; Ability to independently upgrade a single component
•2 – Instantiation in less than 1 hour