Agenda

Backlog/Board https://jira.onap.org/secure/RapidBoard.jspa?rapidView=53&view=planning&selectedIssue=LOG-85
Review work in progress
Review work to be assigned
Beijing related
LOG M1 Beijing Release Planning
OOM-109 - Getting issue details... STATUS
RI related - include Vitaly Emporopulo
LOG-51 - Getting issue details... STATUS
LOG-118 - Getting issue details... STATUS
LOG-123 - Getting issue details... STATUS
LOG-122 - Getting issue details... STATUS
LOG-111 - Getting issue details... STATUS
LOG-43 - Getting issue details... STATUS
LOG-47 - Getting issue details... STATUS
Add JIRA on python inclusion in transactions

ONAP Log Locations
Audit related
Logging Reference Implementation#DI3:20171231:Audit:MixedversionofEELFdependency
LOG-110 - Getting issue details... STATUS
LOG-47 - Getting issue details... STATUS
LOG-124 - Getting issue details... STATUS
LOG jiras in OOM tracking
LOG-101 - Getting issue details... STATUS
Doc related
LOG-91 - Getting issue details... STATUS
LOG-98 - Getting issue details... STATUS
LOG-105 - Getting issue details... STATUS
LOG-97 - Getting issue details... STATUS
R1 carry over
LOG-102 - Getting issue details... STATUS
LOG-63 - Getting issue details... STATUS
LOG-84 - Getting issue details... STATUS
LOG-99 - Getting issue details... STATUS
LOG-87 - Getting issue details... STATUS
LOG-85 - Getting issue details... STATUS - OOM-258 - Getting issue details... STATUS - OOM-292 - Getting issue details... STATUS
LOG-65 - Getting issue details... STATUS
LOG-64 - Getting issue details... STATUS
OOM-324 - Getting issue details... STATUS
OOM-428 - Getting issue details... STATUS
OOM-445 - Getting issue details... STATUS
OOM-500 - Getting issue details... STATUS
Secondary
LOG-94 - Getting issue details... STATUS
LOG-48 - Getting issue details... STATUS blocked by OOM-508 - Getting issue details... STATUS

Open tracing - look into the API - with the other teams
logging and config in general should be driven by the teams themselves in OOM - we provide the initial template
Brian Freeman discussions about logging at the F2F
spec work needs to be finished
OOM coordination - starting with AAI config - include the logging config - raise a logging epic - raise a JIRA on fixing the chef issue introduced by the git pull in the container - AAI-548 - Add the cassandra environment files IN PROGRESS
Shishir Thakore (AT&T) wants to help us see Joining the Community
Committer Review
template Luke Parker - Committer Promotion Request for [Logging-Analytics]
1 - Jerome Doucerain (Bell) - remove - can reapply at any time
2 - Daniel Milani (Bell) - remove can reapply at any time
3 - Mark Pond - free up committer role for new committers
4 - Dave Williamson - write up profile (one of the spec originators and at all meetings/reviews) and present to TSC as new committer
5 - Michael O'Brien - committer in prep of ptl
6 - verify Luke Parker has all committer rights
7 - invite new committers on onap-discuss - likely appc, policy, portal personnel (non-Amdocs, non-AT&T - for the 3+ company rule)
move guidelines meeting up to 9am EDT - publish to onap-discuss
answer several questions from APPC about logging guidelines
appc meeting based on EELF - Wed - Michael O'Brien
TSC asked if HEAT can be deprecated - OOM only - one of the issues will be no required ELK stack in HEAT.