/
LOG Meeting Minutes 2019-01-08

LOG Meeting Minutes 2019-01-08

https://lists.onap.org/g/onap-discuss/topics

http://onap-integration.eastus.cloudapp.azure.com:3000/group/onap-integration

https://jira.onap.org/secure/RapidBoard.jspa?rapidView=143&view=planning.nodetail&epics=visible

Agenda

Table in the format of the AAI team 2018-11-29 AAI Developers Meeting that is working well

Anyone can add agenda items to the top of the list.

Attendees



Title

Responsible

Status

status:Open

status:Done

Last Discussed

Start

Notes

Title

Responsible

Status

status:Open

status:Done

Last Discussed

Start

Notes

Dublin Scope Planning



@Michael O'Brien

status:In Progress

20190108



https://lf-onap.atlassian.net/browse/LOG-707

OPNFV/ONAP Paris









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

@Michael O'Brien

status:In Progress







Security Vulnerabilities

@Michael O'Brien

@Prudence Au

status:In Progress







Secure https endpoints



status:Open







LOG Formats/Files



status:In Progress





https://lf-onap.atlassian.net/browse/LOG-178

Format compliance - working with AAI team

@Michael O'Brien

status:In Progress

20190108

20181101

(+) 20190109
from aai team
https://lf-onap.atlassian.net/wiki/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 LOG-376: Logstash full saturation of 8 cores with AAI deployed on one of the quad 8 vCore vms for 30 logs/sec - up replicaSet 1 to 3 or use DaemonSetClosed

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

https://lf-onap.atlassian.net/browse/LOG-915

edited 2019-01-10 AAI Developers Meeting

for the 10th

AAI team - 2 types of logging AOP/non-AOP



status:Open



20181101

#22 on 2018-12-20 AAI Developers Meeting

Logging requests from Vendors



status:Open





https://lf-onap.atlassian.net/browse/LOG-877

https://lf-onap.atlassian.net/browse/LOG-876

#15,19 and 37 on SP priorities for Dublin

LOG Streaming compliance



status:In Progress





https://lf-onap.atlassian.net/browse/LOG-487

https://lf-onap.atlassian.net/browse/LOG-487

https://lf-onap.atlassian.net/browse/LOG-852









20190108



discuss tick/tock logging spec behaviour - cassablanca implemented in dublin, dublin implemented in elalto

Log Checker

@Cheuk Yiu Horace Ip

@Lee Breslau



20190109



MIke to review with Horace

Search Guard

@Michael O'Brien

status:Open

20180109



https://lf-onap.atlassian.net/browse/LOG-494

spec changes for Dublin

@Dave Williamson



201901115

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

@Dave Williamson

@Michael O'Brien

@Prudence Au



20190115



server name in clustered environments - I will add the details and the Jira right after this meet

see details on serverFQDN in

https://lf-onap.atlassian.net/browse/LOG-666

No cluster failover use case yet - just verifying static cluster fields - most fields are from the cloudify controller which is out of band of the the kubernetes cluster "ServerFQDN": "10.42.156.239", "host": "deployment-handler", "componentName": "deployment-handler", "RemoteHost": "10.42.0.1",", "ServerIPAddress": "10.42.156.239",

filter out DCAE

LOG ELK stack indexing/dashboards



status:Open







Casablanca 3.0.1 work until 10th Jan

@Michael O'Brien







https://lf-onap.atlassian.net/browse/LOG-913

LOG openlab tenant devops

cluster creation/testing

@Michael O'Brien







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

@Michael O'Brien

status:Open





Requiring Updates, Merges or Marked Deprecated

Metric Streaming and Prometheus

@Michael O'Brien

@Vaibhav Chopra

status:In Progress

20181207



https://lf-onap.atlassian.net/browse/LOG-911 - experimental chart on http://secure.solar:30000/graph

LOG-773: Prometheus integration with the Logging ELK stack for OPSClosed

https://lf-onap.atlassian.net/browse/LOG-861

work with @Vaibhav Chopra

https://lf-onap.atlassian.net/browse/OOM-1504

Finish SO filebeat additions

@Michael O'Brien

status:In Progress

20181207



https://lf-onap.atlassian.net/browse/SO-1110

Finish LOG common charts

@Michael O'Brien

status:Open

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/

https://lf-onap.atlassian.net/browse/OOM-1276

Team Members Thank you and review



status:Open





  • @Shane Daniel to be removed - moved on to AI work - thanks for everything done for the logging and oom projects

  • @Lee Breslau

  • @Luke Parker 

  • @Michael O'Brien 

  • @Dave Williamson 

  • @Sanjay Agraharam

  • @Lorraine A. Welch 

  • @James MacNider 

  • @Prudence Au 

  • @Anthony Manuel 

  • @Cheuk Yiu Horace Ip 

Review last 4 weeks since 

LOG Meeting Minutes 2018-12-05



status:In Progress







TSC/PTL meet actions



status:In Progress





OOM transfer chart ownership to teams
LOG is part of poc

@Michael O'Brien

@Mike Elliott

status: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

OOM Deployment priority
base platform includes LOG

@Michael O'Brien

@Mike Elliott

status: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

https://lf-onap.atlassian.net/browse/LOG-898

https://lf-onap.atlassian.net/browse/LOG-326

https://gerrit.onap.org/r/#/c/75422/ via ONAP Development#WorkingwithJSONPath

https://lf-onap.atlassian.net/browse/DCAEGEN2-1067



k8s manifest or oom values.yaml
for docker tags - truth

@Michael O'Brien

status:In Progress

20190107



https://lf-onap.atlassian.net/browse/TSC-86

Nexus3 routing slowdown

@Michael O'Brien

status:Done

20181222



https://lf-onap.atlassian.net/browse/TSC-79

20181217-22

LOG compliance diagram/exercise

@Michael O'Brien

@Sanjay Agraharam

status: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

@Michael O'Brien

status:In Progress

20180107



https://lf-onap.atlassian.net/browse/TSC-25

LOG is part of this poc



Notes