LOG Meeting Minutes 2018-11-13
Notes
RC2 next week
CLM work increased over the last week due to new SEC vulnerabilities in spring libs
https://jenkins.onap.org/view/logging-analytics/job/logging-analytics-maven-clm-master/21/
will need to look at selected versions of spring boot 2.x
trying to get access to CLM reports and wiki for contributors -
Updated spring boot to 1.5.17 and spring to 5.1.2 (from previously ok 5.0.9)
Raised/fixed oparent issue blocking some 5.1.2 - waiting for oparent 1.2.2 release
Releasing updates to logging and pomba artifacts with @James MacNider and @Prudence Au
Adding casablanca build jenkins jobs
Running CD build meet on friday with LF (Jessica) - TSC-25: Task Force to implement CD (Continuous Deployment)Closed
TODO (adjust formatting)
Finalize dublin scope
Rreturn to clean up of JIRA board for both logging and oom (elk common charts)
revisit poc code to prep for refocus on portal/sdk
revisit/write up Dublin logging specification - in concert with portal based implementation focus
The OOM Kubernetes stack was upgraded on the 29th - Rancher 1.6.22, Kubernetes 1.11.2 from 1.10.3 - will send out onap-discuss upgrade mail
paste prometheus dashboard initiative that includes logging - from OOM
Q) verify arch coverage of our scope (montreal 30th and ?)
spec discussion (continue with eelf, add marker/mdc gradually - need to implement 1.2.2 in dublin, 1.4.0 will be for the E release)
Dublin discussion
with @Dave Williamson and Sanjay Agraharam - Dave has been with the project since the beginning - before ONAP 1.0 in May 2017 and Sanjay and his team have been critical since Jan 8 2018
Lean towards a core spec - with extensions for acumos/ecomp - 1 or more baseline components done
security- need to revisit searchguard - LOG-494: Use Search Guard Community Edition for TLS REST encryptionClosed
6.x upgrade issue
revistit aai/logstash issue - 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
Dave's cluster check for - LOG-666: S3P: validate kubernetes pod/container/clusterVM name reflected in clientIPAddress/serverFQDN during cluster failoverClosed
fix up the 2 libraries for the 29 field spec