...
- Post 1.1 Logging Guidelines to onap-discuss for discussion and exposure (all that this involves including adding the ONAP RI - heat VM first
in addition to existing ELK stack on OOM)Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-45 - 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
...
- Discussed...18 min
- documentation - work with Matthew - wait for finalized content
- For the wiki 1.1 spec - determine the diff from the original pdf attachment spec - before sending to the community. - for next meeting (for on existing and proposed versions) -
- discussed code work going into logging and oom repos primarily around duplicated config in the reference log repo and the oom implementation repo - verifying each ONAP components' logs are getting exposed outside its container for both filebeat and /dockerdata-nfs mounts (non-ELK)
- discussed need for heat work when pushing the guidelines
Actions
- todoas above
Attendees - 11
...