Agenda

• Backlog/Board https://jira.onap.org/secure/RapidBoard.jspa?rapidView=53&view=planning&selectedIssue=LOG-85

• Guidelines exposure on onap-discuss need examples

• JIRA work on OOM for LOG -LOG-101: OOM Logging fixes tracking EpicClosed
  Please code-review (Alexis is helping us out) - OOM-462: Adjust mso artifacts to latest (Amsterdam)Closed

• Helm 2.7 upgrade from 2.3 reverted yesterday - 3 Log ELK containers back up for OOM consumers - OOM-427: log containers fail to create since 20171213 - using tpl template function on helm 2.3 not 2.6Closed

• Doc updates (R1 branch) -
  
  LOG-107: Add wiki detailing diff between original PDF logging guidelines and current R2 wiki pageClosed

• R1 vFW triage (all hands on) at 1200EDT daily until 6 Dec Kubecon and 11 Dec ONAP F2F - for OOM and HEAT
  Please join the call:  and contribute anything vFirewall related or stabilizing the R1 branch for OOM or HEAT
  Vetted vFirewall Demo - Full draft how-to for F2F and ReadTheDocs

Notes

• New Work Items:

• Luke to work with doc team on high level what's new and MDC details as part of LOG-107: Add wiki detailing diff between original PDF logging guidelines and current R2 wiki pageClosed

• Check on closing sprint - michael

• version using branch on our RTD - michael

• Filebeat easier in HEAT because all work is in integration team - michael (get epic)

  • Discuss how to get http request/session key:value pairs all the way down to the DAO layer - REST API should handle this - verify the code abstraction from example JAX-RS 1/2
    (No manditory adoption: servlet filter - maybe no - give the projects an RI on a single project and reference this 

  • Need to audit all the project - unavoidable to enumerate what API is used for HTTP REST access - in the terms of plugging in our requestID passing

  • need to look at the code - 

need to review - and prioritize and merge with OOM R2 release - for resiliency (how is logging part of this) 
- OOM for Production-Grade Deployments for example clustering persistence LOG M1 (Beijing) Candidates - for example how do we handle the distributed FS on a distributed ELK stack
both ELK infrastructure and a scaled SDNC cluster (a filebeat per instance and its PV)