...
- 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 nodeport
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key OOM-819
requires an epic to scope external logging providers outside of kubernetes -Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-190 - OOM still needs our help changing the ELK config - Borislav Glozman has it
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb 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)