Page Comparison

...

• 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/009659009660.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

• Lukes Log4j Wrapper code

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

  • Nice, Under review - runs well, merging live in the meeting, discuss next work
  • https://gerrit.onap.org/r/#/c/46569/
• Log(ELK) security review next friday - https://lists.onap.org/pipermail/onap-discuss/2018-May/009695.html
• JIRA board - https://jira.onap.org/secure/RapidBoard.jspa?rapidView=53&view=planning&selectedIssue=LOG-248&epics=visible
• RC2 in 2 days
• Acumos integration Shishir Thakore and Michael O'Brien - 

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

• External ELK stack discussion Shishir Thakore 

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

• 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

  • merging now - planning scope change review by Arch team 5 June
  • nexus3 triage last friday 2h - doubled speed by moving the outgoing route from Bell - 
  • Healthcheck up to 38/43 http://jenkins.onap.info/job/oom-cd-master/2945/consoleFull
• todo:
  • 29th may - 2nd log spec demo - arch review
  • acumos integration
  • elk security
  • elk external spec
  • Review service mesh log overlap
  • review MDC grouping
  • review Luke Parker 's slf4j patch - 
    • https://gerrit.onap.org/r/#/c/46569/
  • pomba 29th arch review
  • 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