Notes

The regular zoom is in use - likely the openstack summit - https://zoom.us/j/519971638

Use my personal one for this one today - zoom.us/j/7939937123

• 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
    • Minutes on  LOG-409 - Getting issue details... STATUS
  • Last Friday - ELK performance review - was private - all onap and acumos meetings should be posted to onap-discuss
  • Last Monday - Acumos Log Spec Sync (AT&T and Amdocs only - next one will be in public) 
    • Notes off  LOG-264 - Getting issue details... STATUS
    • sync logging specs when the acumos side becomes public -  LOG-416 - Getting issue details... STATUS
• Meetings Future
  • Next Thu - ELK performance hands on 2 - https://lists.onap.org/pipermail/onap-discuss/2018-May/009822.html
  • Next Fri - ELK security review 2 - https://lists.onap.org/pipermail/onap-discuss/2018-May/009833.html
  • Next Tue - Arch subcommittee review of POMBA
• Patches Merged - https://gerrit.onap.org/r/#/q/status:merged+project:+logging-analytics, https://gerrit.onap.org/r/#/q/status:merged+project:+oom
  • Log4j Wrapper code
    • LOG-115 - Getting issue details... STATUS
    • https://gerrit.onap.org/r/#/c/46569/
  • Logstash container clustering - replicaSet to 3 (temp until DaemonSet is merged below)
    • LOG-376 - Getting issue details... STATUS
    • https://gerrit.onap.org/r/#/c/47941/
• Patches Pending - https://gerrit.onap.org/r/#/q/status:open+project:+logging-analytics. 
  • Log4j Wrapper code
    • LOG-115 - Getting issue details... STATUS
    • https://gerrit.onap.org/r/#/c/48433/
  • Logstash daemonset
    • LOG-181 - Getting issue details... STATUS
    • https://gerrit.onap.org/r/#/c/48139/
  • elasticsearch/kibana readiness/liveness adjustment to allow startup timing
    • LOG-256 - Getting issue details... STATUS
• Critical JIRAs
  • LOG-258 - Getting issue details... STATUS
  • LOG-409 - Getting issue details... STATUS
  • LOG-230 - Getting issue details... STATUS
    • Logging Pair Wise Testing for Beijing Release - needs more "component logs make to ELK" testing
  • LOG-245 - Getting issue details... STATUS
  • LOG-399 - Getting issue details... STATUS
• 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: integration with acumos logging
    • TBD
  • 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
  
  • Collaborate with the AAF project on securing our 3 ELK ports
    • LOG-409 - Getting issue details... STATUS
    • security meet: just before this one at 10 EDT GMT-5 on Tue
  • 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)
    • LOG-415 - Getting issue details... STATUS
  • 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
    • https://jira.acumos.org/browse/ACUMOS-710
      
• 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