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

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
Jira Legacy
server System Jira
serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
key OOM-819

requires an epic to scope external logging providers outside of kubernetes -
Jira Legacy
server System Jira
serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
key LOG-190
OOM still needs our help changing the ELK config - Borislav Glozman has it
Jira Legacy
server System Jira
serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
key OOM-740
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)

Versions Compared