Title | Responsible | | Last Discussed | Start | Notes |
---|
Logging compliance TSC/PTL | |
| 20190115 | 20190114 | PTL 2019-01-14 discussed at last PTL meet with djhunt
|
Dublin Scope Planning
| | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 20190108 |
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-707 |
---|
|
Logging Dublin M1 Release Planning |
restart log4j format example | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 201901115 | 20190115 | https://gerrit.onap.org/r/#/c/62405/ for Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-630 |
---|
|
|
Work with portal/sdk library | Michael O'Brien | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 20190115 | 20190115 |
|
New Committers |
|
| 20190115 |
| We have room for 2-5 committers and will be reviewing the list Logging Enhancements Project Proposal#KeyProjectFacts add your details to Logging Committer Promotion Requests
|
OPNFV/ONAP Paris |
| | 20190108 |
| https://ddfplugfest19.sched.com/ Tue-Thu Clover Gambia on prior https://zoom.us/j/115579117 - 7 hours ahead https://ddfplugfest19.sched.com/event/K1Gy/opnfv-clover-utilizing-cloud-native-technologies-for-nfv |
Security badging | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
|
|
|
|
Security Vulnerabilities | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
|
|
|
|
Secure https endpoints | | |
|
|
|
LOG Formats/Files |
| Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
|
|
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-178 |
---|
|
|
Format compliance - working with AAI team | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 20190108 | 20181101 | (+) 20190109 from aai team https://wiki.onap.org/display/DW/2019-01-17+AAI+Developers+Meeting+Open+Agenda "hector has discovered that the stress test jar (liveness probe?) in aai-cassandra is hammering the cpu/ram/hd on the vm that aai is on - this breaks the etcd cluster (not the latency/network issues we suspected that may cause pod rescheduling) "
#6 on 2018-12-20 AAI Developers Meeting around Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-376 |
---|
|
Discussion with @Sanjay Agraharam and [~pau2882] on checking how cassandra is running on the vm and if debug levels are on should be verified use labelling to split aai-cs and ls - no DaemonSet Michael O'Brien to reduce core count for ls to 1 from 3 Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-915 |
---|
|
edited 2019-01-10 AAI Developers Meeting for the 10th |
AAI team - 2 types of logging AOP/non-AOP | | |
| 20181101 | #22 on 2018-12-20 AAI Developers Meeting |
Logging requests from Vendors |
| |
|
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-877 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-876 |
---|
|
#15,19 and 37 on SP priorities for Dublin |
LOG Streaming compliance |
| Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
|
|
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-487 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-487 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-852 |
---|
|
and PTL 2019-01-14 |
|
|
| 20190108 |
| discuss tick/tock logging spec behaviour - cassablanca implemented in dublin, dublin implemented in elalto |
Log Checker | |
| 20190109 |
| MIke to review with Horace |
Search Guard | | | 20180109 |
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-494 |
---|
|
|
spec changes for Dublin | |
| 20190109 | 20190109 | Dublin spec changes for Elalto environment name release name check mail for reply Michael O'Brien Prudence Au proposal of renaming the log file name itself for the release ie: 3.0.0-ONAP - will discuss later for next week
|
Cluster logging behaviour | |
|
|
| server name in clustered environments - I will add the details and the Jira right after this meet
|
LOG ELK stack indexing/dashboards |
| |
|
|
|
Casablanca 3.0.1 work until 10th Jan | |
|
|
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-913 |
---|
|
|
LOG openlab tenant devops cluster creation/testing | |
|
|
| We have 2 clusters a 1+4 and 1+13 used for testing deployments and running the vFW Logging DevOps Infrastructure |
Wiki edits, RTD review | | |
|
| Requiring Updates, Merges or Marked Deprecated |
Metric Streaming and Prometheus | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 20181207 |
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-911 |
---|
|
- experimental chart on http://secure.solar:30000/graph Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-773 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-861 |
---|
|
work with Vaibhav Chopra Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | OOM-1504 |
---|
|
|
Finish SO filebeat additions | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 20181207 |
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | SO-1110 |
---|
|
|
Finish LOG common charts | | | 20181207 |
| James MacNider - bring in Prianka's common eLK charts and use them in Clamp, LOG, SDC, POMBA https://gerrit.onap.org/r/#/c/64767/ Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | OOM-1276 |
---|
|
|
Team Members Thank you and review |
| |
|
| |
Review last 4 weeks since LOG Meeting Minutes 2018-12-05 |
| Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
|
|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | TSC-79 |
---|
|
https://lists.onap.org/g/onap-discuss/topic/onap_helpdesk_65866/28800220?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,28800220 https://wiki.onap.org/display/DW/Cloud+Native+Deployment#CloudNativeDeployment-NexusProxy
|
TSC/PTL meet actions |
| Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
|
|
| |
OOM transfer chart ownership to teams LOG is part of poc | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 20190107 |
| Starting - will have a training session - will send out any meetings to onap-discuss We may have the same symlink repo folder like we do for doc Last discussed TSC 20180109 |
OOM Deployment priority base platform includes LOG | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 20181207 |
| Q2) priority of system level containers like the ELK stack - OOM has a common services JIRA - DMaaP, AAF - TODO get JIRA - make sure log is in this! There is a cd.sh retrofit that sequences the pods in order for deployment stability - this will be phased out when tiered deployment comes in Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-898 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-326 |
---|
|
https://gerrit.onap.org/r/#/c/75422/ via ONAP Development#WorkingwithJSONPath Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | DCAEGEN2-1067 |
---|
|
|
k8s manifest or oom values.yaml for docker tags - truth | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 20190107 |
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | TSC-86 |
---|
|
|
Nexus3 routing slowdown | | | 20181222 |
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | TSC-79 |
---|
|
20181217-22 Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-898 |
---|
|
|
LOG compliance diagram/exercise | Michael O'Brien @Sanjay Agraharam | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 20181205 |
| Log Streaming Compliance and API Sanjay - diagram FB must be split between using AOP and AOP+spec compliant - only this one should be green |
|
|
|
|
|
|
Ongoing |
|
|
|
|
|
CI/CD pipeline TSC poc | | Status |
---|
colour | Yellow |
---|
title | In Progress |
---|
|
| 20180107 |
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | TSC-25 |
---|
|
LOG is part of this poc https://lists.onap.org/g/onap-discuss/topic/cd_task_force_tsc_25_meetings/29001640?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,20,29001640 |