...

• 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 R2 Release Planning

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-109

• RI related

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-51

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-118

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-123

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-122

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-111

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-43

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-47

  
  
  ONAP Log Locations
  
  
• Audit related
• Logging Reference Implementation#DI3:20171231:Audit:MixedversionofEELFdependency

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-110

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-47

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-124

• LOG jiras in OOM tracking

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-101

• Doc related

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-91

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-98

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-105

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-97

• R1 carry over

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-102

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-63

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-84

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-99

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-87

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-85

   - 

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-258

   - 

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-292

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-65

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-64

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-324

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-428

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-445

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-500

• Secondary

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-94

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-48

   blocked by 

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-508

• 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
• Shay Takore (AT&T) wants to help us see  Joining the Community
• Committer Review
• template 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.
• 
  
  

Notes

• notes