High Level
Features
see ONAP Application Logging Specification - Post Dublin
Follows deprecated - Logging Casablanca Scope
Key words are: out of the box, reuse components, iterative changes - not major spec changes.
There is one primary use case and one enabler use case
UC1: Provide for transaction tracing via search or dashboard for distributed transactions across ONAP components - enabled by the logs shipped to the ELK stack - in real time. (the ELK stack is there - we just need to adjust log content - amount and format)
UC2: Provide for UC1 tracing via standardized logs - ideally via marker/mdc (label/key:value pair) markup |
Logging Alignment before enhancement
Plan is to take the portal/sdk library - align the rest of onap to this library and then add marker/mdc (labels and key/value pair) support as required in phase 2
Work will include 1) verify pipeline 2) verify logback format
Open Standards
Look at a standard that will allow us to use standard parsing libraries all the way to eventual AI/ML by adopting a standard like open tracing.
Security
REST and HTTPS security
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-494 |
---|
|
Infrastructure Improvements
including filebeat sidecar anti-pattern/replacement, elk stack upgrade, deployment template, library language scope (python, swift...)
HELM Hooks for Configuration
https://github.com/helm/helm/blob/master/docs/charts_hooks.md
Monitoring
Investigate out of the box prometheus monitoring
S3P
backup/restore, security, log format monitoring, elk dashboards
3rd party consumption alignment
Lower in priority will be to align onap with requirements of Acumos and ECOMP for example - the focus will be on alignment of ONAP components only - to the primary goal of providing a transaction tracing system via the ELK stack.
Dublin Alignment
Release 4 (Dublin) Service Providers (EUAG) Requirements / Proposals
SP priorities for Dublin
Deployment Model
In progress - was a one time casablanca static dashboard - will do an automated one with the Bell, Orange and Samsung guys
Image Added
Epics
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-707 |
---|
|
Priority | Feature | Owner | Status | % complete | EPIC | Notes |
---|
0 |
---|
commit | bugs |
|
| 60% | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-1110 |
---|
|
|
|
| 6.3 upgrade |
|
| 0% | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-653 |
---|
|
| Acumos and Clamp driven - need plugin/module support in 6.3 |
1 | | verify new filebeat version works verify indexes need upgrade strategy for future - index migration |
commit | schema |
|
| 50% | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-630 |
---|
|
|
|
commit | search guard |
|
|
| Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-494 |
---|
|
| 20181113 added to scope in LOG Meeting Minutes 2018-11-13 |
stretch | format standards for tracing |
|
|
| Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-104 |
---|
|
|
|
stretch | analytics |
|
|
| Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-500 |
---|
|
| Artificial Intelligence and Deep Learning |
| shipping infrastructure | | starting | | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-487 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-852 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | SO-1110 |
---|
|
| Verify infrastructure part 2 - add infrastructure to new pods |
| log level management |
|
|
| Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-800 |
---|
|
| |
| Content | |
| 10% | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-178 |
---|
|
| Verify log content |
| Library | | 20180809 |
submitted |
| Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG- |
---|
|
|
115log4j library | Portal has a library in SDK that is already used by AAI, SDC move up |
| Security | |
|
| Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-409 |
---|
|
|
2 |
|
|
| | in progress | 30% | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-95 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-118 |
---|
|
|
aop AOP wrapper of log4j library in LOG-115 |
3 |
| Deployment | | Prototype done need to retrofit |
| Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-560 |
---|
|
|
|
Stretch |
| | Not started |
| Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-480 |
---|
|
| log testing tool |
4 |
|
|
|
|
| Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-190 |
---|
|
| Pluggable devops |
5Stretch |
| | feasibility tested | 10% | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-380 |
---|
|
| expand on filebeat DaemonSet |
6 |
|
| |
|
| Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-169 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-180 |
---|
|
| Filebeat alternatives fluentd |
7 |
|
| |
|
| Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-407 |
---|
|
| debug for devs |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | | submitted | 90% | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-115 |
---|
|
| SLF4J demo library |
El-alto | CLAMP and VES alignment with Logging ELK |
|
|
| Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-956 |
---|
|
|
|
Q: Tony Hansen Q about library support beyond java like Python, - heads up to MultiVim team when the spec (29 fields is approved by the arch meet next week) - to realign
Q: need a way to combine the 3 users of python and their separate libraries
Notes
Architecture revisit - should we adjust our ELK stack to use for example fluentd, or add prometheus
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | LOG-773 |
---|
|