Agenda
- Documentation discussion (we are the only project in ONAP that is conditional based on our documentation state - the nature of open source is just-in-time and incremental - therefore the logging guide "as-is" must be submitted - we can edit it continuously however until the Nov 9th deadline for the Nov 15 go/no-go of the R1 release.
RC0 (Oct 12) complete development guides
RC1 (Oct 26) Resolve doc issues
RC2 (Nov 9) Gain final approval from Doc. Team - Discuss EPICs for R1 and R2 -
- Review JIRA Board, backlog
- log https://jira.onap.org/secure/RapidBoard.jspa?rapidView=53&view=planning&selectedIssue=LOG-64
- oom https://jira.onap.org/secure/RapidBoard.jspa?rapidView=41&view=detail&selectedIssue=OOM-297
- log https://gerrit.onap.org/r/#/q/status:merged+project:logging-analytics
- oom https://gerrit.onap.org/r/#/q/status:open+project:+oom
- Review last meeting actions
- Assign work items
Minutes
- Discussed...1
- vote on ways to edit the guidelines next meet
- vote meeting agenda flow - guide first, JIRA second ?
- onap config is split - oom is working merging heat and oom
- (oom config in oom project, heat it is in each project distributed across components)
- discuss (raise epic) combining config - or raise a hierarchy (oparent?) - default version with specific overrides if required per project
- need to discuss eelf consistency and MDC details for next meeting
- LOG-85 discuss external mounts for /dockerdata-nfs shares and how to get it to work with emptyDir()
- upfront arch discussion on implementation changes in the JIRA architecture page for epics in R2
- small demo of functionality - proposals
- f2f - discussions of logging exposure in the talks/hands-on/discussion-panels
- vFirewall integration testing (daily) - always asking for logs in HEAT testing - we could address this in R2 either either through HEAT ELK or when OOM gets consumed in R2
- 2 logging related NPE bugs - we can fix these as well - we have 2 weeks
Actions
- as above
Comparison of line formats:
Before:
11/08-02:11:28.213|org.onap.example.component1.subcomponent1.LogbackTest|b88319fb-966e-4eb9-ad7f-a604da21c55a||main|||INFO||||||here's an info it has newlines and tabs
After
org.onap.example.component1.subcomponent1.LogbackTest 2017-11-07T15:11:28.213Z INFO here's an info\nit has newlines\tand tabs key1=value1, key2=value2 with space, RequestId=b88319fb-966e-4eb9-ad7f-a604da21c55a, key5=value5"with"quotes, key6=value5>with<chevrons, key3=value3\nwith\nnewlines, key4=value4\twith\ttabs main
Attendees - nn
...