Page Comparison

...

• this week...
  • logging work
    • Dev environment back up - merging existing library - using vid-app-common as a template for usage of org.onap.portal.sdk
    • prepping for splitting repos - 1 per component - will need 8+
    • working with dmaap on charts and filebeat
    • pylog issues for vfc are transient LF issues - posting response
    • release notes
    • scorecard for S3P
    • questions on logging format onap-discuss including hv-ves I need to address https://lists.onap.org/g/onap-discuss/message/14997?p=,,,20,0,0,0::Created,,log,20,2,20,29162034
  • infrastructure work
    • CI/CD - going with Orange MQ robot for oom merges
    • PerformancePerf and mostly crashloop avoidance 
    • Deploy changes for RHEL7.6
    • Deploy order work
    • ARM A1 testing of new containers from dockerhub on AWS
    • Nodeports for dmaap
    • Datalake (now part of DCAE) does not yet affect us but it will - 
  • ONS April conference prep work
• last week....
• get committed resources for the next 2 months M2 to RC0 - so we can state what is in and out of the Dublin release
  9 weeks to april 4th
  
  • M2 - functionality freeze - 21 Feb
    M4 - April 4th 
    I have taken the liberty of adding some names - feel free to add your availability or edit this section - we will paraphrase it in the M1 report - Logging Dublin M1 Release Planning
  • Michael O'Brien - 50% direct Logging work - really 40% dev/devops + 10% PTL/TSC/Project - the rest = related ONAP, CD, Doc, OOM, conference/customer,
  • Prudence Au - doing half of the PTL work, template, meets, reviews - especially POMBA with James MacNider on reviews - representing on most Thu POMBA meets
  • Avdhut Kholkar - thank you for all the commit reviews
  • Luke Parker - co-PTL and reference code
• Meeting at 1200 EST today on ARM docker images (affecting LOG images as we need to get the ARM layer into the image - wrap the dockerhub versions)
  

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

• Stop using "latest" for any image - lock down the version tag for testing stability - see our use of busybox
  
  

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

• Good news: We passed M1 last Thu
• Dublin scope finalized for M1
  Release Planning#DublinReleaseCalendar
  Logging Dublin Scope
• New work for dublin
  • Assist in 5G edge work via OOM/AWS work - meet is at 1100 EST Wed with Ramki Krishnan's team
  • plus metric capture via Prometheus -

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

    
    

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

• Review/consolidate JIRAs
• opentrace - will try to get in by april - an LF project 
• priority list
  • infrastructure - filebeat sidecars (before DaemonSet refactor) - see Log Streaming Compliance and API
  • format - via library - portal/sdk - minimal retrofit for markers/mdcs - 

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

  • all s3p - security, perf (aai-log-3**) - scaling - run with 1 logstash
  • Logstash used to be a Daemonset  - however the filebeat needs to a daemonset - instead of each sidecar - 1 container per vm - get story
  • Additional tools - get POC for each - determine which goes to production level
    
    • prometheus - requires coordination with oom and multicloud
    • log checker - pending
    • opentracing - us - 

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

    • search guard - us

...