Page Comparison

...

• JIRA board - https://jira.onap.org/secure/RapidBoard.jspa?rapidView=53&view=planning&selectedIssue=LOG-248&epics=visible
• RC2 pushed out to 2 days from now.
• Casablanca scope discussion start
  • Normal ONAP TSC/Project pull for capabilities up to Beijing release
  • Acumos logging spec review for Tue 29 May – cross ONAP (Casablanca focus)
    1. https://jira.onap.org/browse/LOG-416
  • Logging performance (Beijing focus)
    1. https://jira.onap.org/browse/LOG-258
    2. https://jira.onap.org/browse/LOG-376
  • Logging security (Casablanca focus)
    1. https://jira.onap.org/browse/LOG-409
  • Logging externalization (Casablanca focus)
    1. https://jira.onap.org/browse/LOG-190
• Meetings Past
  • Last 2nd friday - Log(ELK) security review - https://lists.onap.org/pipermail/onap-discuss/2018-May/009695.html
    • Minutes on 

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

  • Last 2nd Friday - ELK performance review - was private - all onap and acumos meetings should be posted to onap-discuss
  • Last 2nd Monday - Acumos Log Spec Sync (AT&T and Amdocs only - next one will be in public) 
    • Notes off 

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

    • sync logging specs when the acumos side becomes public - 

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

  • Last Thu - ELK performance hands on 2 - https://lists.onap.org/pipermail/onap-discuss/2018-May/009822.html
  • Last Fri - ELK security review 2 - https://lists.onap.org/pipermail/onap-discuss/2018-May/009833.html - not enough traffic to verify
  • Today - Arch subcommittee review of POMBA
• Meetings Future
  • follow up - ELK performance hands on 3 - To book
  • follow up - ELK security review 2 - To book with AAF - friday
• 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

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

    • https://gerrit.onap.org/r/#/c/48433/
    Logstash daemonset

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

    • https://gerrit.onap.org/r/#/c/48139/
• Patches Pending - https://gerrit.onap.org/r/#/q/status:open+project:+logging-analytics. 
  
  • elasticsearch/kibana readiness/liveness adjustment to allow startup timing

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

• Critical JIRAs

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

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

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

    • Logging Pair Wise Testing for Beijing Release - needs more "component logs make to ELK" testing

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

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

• Scope Changes
  • Scope Change: POMBA architecture scope change review postponed until post 22 May (arch conference) - now 29th May

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

    • 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 

      Jira Legacy
      server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key ONAPARC-153

  • Scope Change: integration with acumos logging
    • TBD
  • Scope Change: CD/deployment scripts templates (rancher, azure, cd) - moved from OOM-710 to 

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

    • 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

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

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

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

  • External ELK stack discussion Shishir Thakore 

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

  • Acumos integration Shishir Thakore and Michael O'Brien - 

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

    • https://jira.acumos.org/browse/ACUMOS-710
      
• TODO:
  • ? June - 2nd log spec demo - arch review
  • Review service mesh log overlap
  • review MDC grouping
  • Provide MDC documentation for Acumos in ONAP - expand our doc
  • 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