Notes

• JIRA board - https://jira.onap.org/secure/RapidBoard.jspa?rapidView=53&view=planning&selectedIssue=LOG-248&epics=visible
• RC2 pushed out 2 weeks from last thu.
• Meetings Past
  • Last friday - Log(ELK) security review - https://lists.onap.org/pipermail/onap-discuss/2018-May/009695.html
  • Last Friday - ELK performance review - 
  • Last Monday - Acumos Log Spec Sync (AT&T and Amdocs only - next one will be in public) 
• Meetings Future
  • Next Thu - ELK performance review 2
  • Next ? - ELK security review
• Patches Merged
  • Lukes Log4j Wrapper code
    • LOG-115 - Getting issue details... STATUS
    • https://gerrit.onap.org/r/#/c/46569/
• Patches Pending
  • Lukes Log4j Wrapper code
    • LOG-115 - Getting issue details... STATUS
    • https://gerrit.onap.org/r/#/c/48433/
• Critical JIRAs
• Scope Changes
  • Scope Change: POMBA architecture scope change review postponed until post 22 May (arch conference) - now 29th May
  • LOG-196 - Getting issue details... STATUS
    • https://lists.onap.org/pipermail/onap-discuss/2018-May/009660.html
    • Logging Scope Change for POMBA seed code
    • will likely be raised by Chris after  ONAPARC-153 - Getting issue details... STATUS
  • Scope Change: CD/deployment scripts templates (rancher, azure, cd) - moved from OOM-710 to  LOG-320 - Getting issue details... STATUS
    • merged - planning scope change review by Arch team 5 June
    • Healthcheck up to 41/43 https://lists.onap.org/pipermail/onap-discuss/2018-May/009814.html
    • both systems in sync

      • http://jenkins.onap.info/job/oom-cd-master/2971/consoleFull

      • https://jenkins.onap.org/view/External%20Labs/job/lab-tlab-beijing-oom-deploy/321/console

• Cross Team
  
  • CLAMP is running a full ELK stack - raised collaboration JIRA to move the stack to a common chart (we are on 5.5.0 they are one 5.5.9)
  • External ELK stack discussion Shishir Thakore  LOG-190 - Getting issue details... STATUS
  • Acumos integration Shishir Thakore and Michael O'Brien -  LOG-264 - Getting issue details... STATUS
• TODO:
  • ? June - 2nd log spec demo - arch review
  • Review service mesh log overlap
  • review MDC grouping
  • governance: Shishir Thakore Q: logging compliance - TSC requires 2 things - logs make it to the elk stack, and that the MDC format/req are in spec (need a junit? to point to or for the teams to run)
    • Lee Breslau and Cheuk Yiu Horace Ip - thank you very much
    • Mike to post wiki grid checklist from TSC for PTLs to fill out - eventual goal is an lf jenkins job - via ciman