Michael presenting at ONS LA - available - https://onsna18.sched.com/event/Dm4T/onap-continuous-deployment-on-oom-kubernetes-via-aws-michael-obrien-amdocs

Yesterday's guidelines review had 15 people but not quorum - we will do another one

ONAP Application Logging Guidelines v1.2 (Beijing)

Notes

• M4 artifacts due today for Thu
  
  Logging Beijing - M4 Security/Vulnerability Threat Template
  Logging Beijing - M4 Deliverable for Code Freeze Milestone Checklist Template

• license

• sonar

• test code

• The JIRA to expose the logstash nodeport OOM-819: expose log/logstash 5044 as nodeport for external log producers outside of the kubernetes clusterClosed
  requires an epic to scope external logging providers outside of kubernetes - LOG-190: Provide for pluggable/external (not in the kubernetes namespace) log traffic into the ELK logstash containerClosed

• OOM still needs our help changing the ELK config - @Borislav Glozman has it OOM-740: Add Standardized Configuration to LOGClosed

• Verify that logstash config in /dockerdata is being picked up inside the container - it is not - TODO add a JIRA on oom after we verify this

• Neal to work with Shishir on OOM-819

• Shishir / Sanjay needs the name changed - Change to "specification" - good point to state that they are required

• Nail down absolutely required MDCS (the rest should be derived - timestamp for example)

• Meet again on finalizing the beijing spec next week 

• Rae: sequence generation requires partner field - will discuss rename

• work in the Casablanca spec from now on ONAP Application Logging Specification v1.2 (Casablanca)