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 -
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-101
Please code-review (Alexis is helping us out) -Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key OOM-462 - Helm 2.7 upgrade from 2.3 reverted yesterday - 3 Log ELK containers back up for OOM consumers -
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key OOM-427 - Doc updates (R1 branch) -
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb 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
Notes
- New Work Items:
- Luke to work with doc team on high level what's new and MDC details as part of
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb 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 -
- 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
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)