Agenda
- F2F
- Talk with Jack Murray AT&T
- Discuss Logging with OPEN-O team
- Luke' 1.2 guidelines - ONAP Application Logging Guidelines v1.2 (Beijing)
- Check out whats new section and get one context up for next week
- Reach out and list potential new contributors from other projects that have shown interest before/after F2F
- A lot of the work is actually in OOM - we are leveraging the team there as we adjust and fix logging issues there
- /dockerdata-nfs issues with exposed logging config - change in the works by team Deep in OOM - to start
- removing the tarball in the config pod - see Mandeep Kinda of OOM andJira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key OOM-406 Ashutosh Mishra
- https://gerrit.onap.org/r/#/c/24893/
- see OOM work tracking in
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-101 - When tpl issues in the helm 2.5+ upgrade is solved we will migrate to config maps
- Input into OOM Requirements for Component Teams
- Logging config rolled into OOM requirements? - OOM needs to let the teams know of their config sections in config/init/docker/src - for now until OOM-406
- TSC agenda item (PTL coordinators meeting as well) - flag configuration to all PTL's - 2 step guidelines first, config changes second - mike
- Pick key projects to help drive the rest of the community - AAI first ? J. Forsythe - mike