...

• 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 -

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-101

  
  Please code-review (Alexis is helping us out) - 

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-462

• Helm 2.7 upgrade from 2.3 reverted yesterday - 3 Log ELK containers back up for OOM consumers - 

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-427

• Doc updates (R1 branch) -
  
  

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-107

• 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
• yy

Notes

• New Work Items:
• Luke to work with doc team on high level what's new and MDC details as part of 

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-107

• 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 - 
• z