/
LOG Meeting Minutes 2019-01-29

LOG Meeting Minutes 2019-01-29

Meeting at 1100 EST Tue - https://zoom.us/j/519971638

regular zoom has error "meeting in progress" - use my zoom for today https://zoom.us/j/7939937123

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

Attendees 


Luke Parker

Cheuk Yiu Horace Ip

Michael O'Brien

Prudence Au

Dave Williamson

Sanjay Agraharam

Lorraine A. Welch

Items

  • get committed resources for the next 2 months M2 to RC0 - so we can state what is in and out of the Dublin release
    9 weeks to april 4th
    • M2 - functionality freeze - 21 Feb
      M4 - April 4th 
      I have taken the liberty of adding some names - feel free to add your availability or edit this section - we will paraphrase it in the M1 report - Logging Dublin M1 Release Planning
    • Michael O'Brien - 50% direct Logging work - really 40% dev/devops + 10% PTL/TSC/Project - the rest = related ONAP, CD, Doc, OOM, conference/customer,
    • Prudence Au - doing half of the PTL work, template, meets, reviews - especially POMBA with James MacNider on reviews - representing on most Thu POMBA meets
    • Avdhut Kholkar - thank you for all the commit reviews
    • Luke Parker - co-PTL and reference code
  • Meeting at 1200 EST today on ARM docker images (affecting LOG images as we need to get the ARM layer into the image - wrap the dockerhub versions)
    LOG-331 - Getting issue details... STATUS
  • Stop using "latest" for any image - lock down the version tag for testing stability - see our use of busybox

    LOG-949 - Getting issue details... STATUS
  • Good news: We passed M1 last Thu
  • Dublin scope finalized for M1
    Release Planning#DublinReleaseCalendar
    Logging Dublin Scope
  • New work for dublin
    • Assist in 5G edge work via OOM/AWS work - meet is at 1100 EST Wed with Ramki Krishnan's team
    • plus metric capture via Prometheus - LOG-911 - Getting issue details... STATUS
      LOG-707 - Getting issue details... STATUS
  • Review/consolidate JIRAs
  • opentrace - will try to get in by april - an LF project 
  • priority list
    • infrastructure - filebeat sidecars (before DaemonSet refactor) - see Log Streaming Compliance and API
    • format - via library - portal/sdk - minimal retrofit for markers/mdcs -  LOG-600 - Getting issue details... STATUS
    • all s3p - security, perf (aai-log-3**) - scaling - run with 1 logstash
    • Logstash used to be a Daemonset  - however the filebeat needs to a daemonset - instead of each sidecar - 1 container per vm - get story
    • Additional tools - get POC for each - determine which goes to production level
      • prometheus - requires coordination with oom and multicloud
      • log checker - pending
      • opentracing - us -  LOG-104 - Getting issue details... STATUS
      • search guard - us


PRITitleResponsible

Status

OPEN

DONE

In DublinLast Worked onStartNotes

Security Vulnerability templateOngoingIN
20190122

M1 template

DONE

IN2019012