/
LOG Meeting Minutes 2019-01-22
LOG Meeting Minutes 2019-01-22
Meeting at 1100 EST Tue - https://zoom.us/j/519971638
https://lists.onap.org/g/onap-discuss/topics
http://onap-integration.eastus.cloudapp.azure.com:3000/group/onap-integration
https://jira.onap.org/secure/RapidBoard.jspa?rapidView=143&view=planning.nodetail&epics=visible
Agenda
Attendees
Items
- get committed resources for the next 2 months M1 to RC0 - so we can state what is in and out of the Dublin release
9 weeks to april 4th- M2 - functionality freeze - 21 Feb
M4 - April 4th
I have taken the liberty of adding some names - feel free to add your availability or edit this section - we will paraphrase it in the M1 report - Logging Dublin M1 Release Planning - Michael O'Brien - 50% direct Logging work - really 40% dev/devops + 10% PTL/TSC/Project - the rest = related ONAP, CD, Doc, OOM, conference/customer,
- Prudence Au - doing half of the PTL work, template, meets, reviews - especially POMBA with James MacNider on reviews - representing on most Thu POMBA meets
- Avdhut Kholkar
- Luke Parker
- M2 - functionality freeze - 21 Feb
- Finalize Dublin scope for M1 in 2 days
Release Planning#DublinReleaseCalendar
Logging Dublin Scope - New work for dublin
- Review/consolidate JIRAs
- opentrace - will try to get in by april - an LF project
- priority list
- infrastructure - filebeat
- format - via library - portal/sdk - minimal retrofit for markers/mdcs
- all s3p - security, perf (aai-log-3**) - scaling - run with 1 logstash
- Logstash used to be a Daemonset - however the filebeat needs to a daemonset - instead of each sidecar - 1 container per vm - get story
- Additional tools - get POC for each - determine which goes to production level
PRI | Title | Responsible | Status OPEN DONE | In Dublin | Last Worked on | Start | Notes |
---|---|---|---|---|---|---|---|
Security Vulnerability template | IN | 20190122 | |||||
M1 template | IN PROGRESS | IN | 20190122 | ||||
ONS NA 2019 April Talk proposal | DONE | IN | 20190122 | ||||
Use manifest generation over raw oom values.yaml docker image tag names | IN PROGRESS | 20190117 | Team, In the TSC it was decided to treat the diff between oom and the manifest by always running the manifest generated yaml in your deployments – you will not need to do this for master work – just for Casablanca and RC0-2 work
Working out the details in https://jira.onap.org/browse/LOG-929 /michael | ||||
S3P Logging compliance TSC/PTL | IN | 20190115 | 20190114 | ||||
El-Alto 1.4 logging spec change - plan only todo merge with Dave's below | IN | 20190122 | |||||
Dublin Scope Planning |