Agenda

• address backlog of LOG Meeting Minutes 2018-11-13

• Committer/PTL votes

  • PTL role is up for election - any committer can run - details on last election - I will post a page for Dublin for next week
    
    

    • Logging Committer Promotion Requests

  • Committer list review

    • Lee (LOG)

    • Avdhut (LOG)

    • Luke (LOG)

    • Michael (LOG/POMBA)

    • Prudence (LOG/POMBA)

    • Geora (POMBA)

    • Shane has left ONAP (pomba)

    • room for 2-4 more committers (Logging - Lorraine, Dave, Sanjay? and Pomba - Pierre?)

• Resource commitments

  • Architecture/requirements - covered

  • Devops (build, jobs, s3p - R3 Logging Security/Vulnerability Threat Template and https://jenkins.onap.org/view/logging-analytics/job/logging-analytics-maven-clm-master/)

    • LOG-666: S3P: validate kubernetes pod/container/clusterVM name reflected in clientIPAddress/serverFQDN during cluster failoverClosed

  • Implementation

  • project overhead (builds/deploy/jobs/security)

  • create 6+ new repos for python and java reference implementations

    • LOG-871: New logging-analytics/reference repos for 1:1 repo:artifact releasesClosed

    • LOG-860: Lower logstash replicaSet from 5 to 3 and set to 1 in dev.yamlClosed

• Overall Dublin plan - Logging Dublin Scope

  • LOG-870: Dublin Release PlanningClosed

  • Infrastructure

    • Log streaming adjustments (see Log Streaming Compliance and API)

      • with

      • partial

      • without

    • Security

      • Security (REST and HTTPS transport)

        • Definitely need to use search guard LOG-494: Use Search Guard Community Edition for TLS REST encryptionClosed

      • Vulnerability/PEN testing

  • Log format/schema adherence

    • We have a good spec from Casablanca - we will be implementing this in Dublin - see Active Logging Specifications

    • ecomp to onap

    • openo to onap

    • new components

  • Use cases

    • ops

    • transaction tracing (passing, failure of VNF deployment for example)

  • Log library use (optional)

    • As we know - each pod will need to deliver logs in one of at least 3 ways, manually, non-AOP library (like AAI), AOP library (like portal/sdk, or our reference)

    • retrofit/augment our example to use portal, adjust the library if required, support adoption onap wide
      
      
      

• TODO

Notes