...
- catching flight 1 hour after meeting start -
I will try to get through security to run the meeting - go over infrastructure current state and changes for dublin
- last week review LOG Meeting Minutes 2018-11-27 - RC2
- Log Streaming Infrastructure diagram - one possible prototype for a live dashboard - we will go through the sections in zoom mode
- This diagram is required for general logging kubernetes discussion, which pods are streaming logs or not, which containers use an AOP, callable or no logging library - all to help triage what we will be working on in casablanca
- Capture any changes to the Casablanca spec to be implemented in Dublin Active Logging Specifications - in the Dublin spec to be implemented in E* ONAP Application Logging Specification - Post Dublin
- Review new JIRA board
- Review additions to dublin scope -
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-707 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-876 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-877 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key TSC-70 Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-889
- casablanca released on friday 30 Nov 2018 - we are now free to work exclusively on dublin
- Release Planning#DublinReleasePlanning
- This is the schedule for the MR - we are not required to be in the 3.0.1 release as we have no highest defects currently - the 4.0 M1 milestone is around mid Jan
- We are not in the 3.0.1 MR release - just Dublin
- I will be at a customer site next meeting LOG Meeting Minutes 2018-12-11 - no meeting - customer demos and devops - and vF2F but I will have status that I will post there
- meeting in 2 weeks is normal - LOG Meeting Minutes 2018-12-18
- I will implement the meeting format that James Forsyth of AAI uses - an ongoing grid with dates for "last discussed" column - where we can keep on all issues
- 2018-11-29 AAI Developers Meeting
- for example we have cross development issues
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-1810
...