Content Comparison

...

• Backlog/Board https://jira.onap.org/secure/RapidBoard.jspa?rapidView=53&view=planning&selectedIssue=LOG-85
• appc meeting based on EELF - 
• Go over issue priority/assignment
• go over doc priorities
• Committer Review
• 1 - Jerome (Bell) - remove - can reapply at any time
• 2 - Daniel (Bell) - remove can reapply at any time
• 3 - Dave - write up profile (one of the spec originators and at all meetings/reviews) and present to TSC as new committer
• 4 - Michael - committer in prep of ptl
• 5 - verify Luke has all committer rights
• 6 - Mark - free up committer role for new committers
• 7 - invite new committers on onap-discuss - likely appc, policy, portal personnel (non-Amdocs, non-AT&T - for the 3+ company rule)
• review 

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

   and LOG-95
• Investigate Vitaly's SDC JIRA Vitaly E
• 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 - needs filtered logging (debug separate) for the elk stream - use ELK instead of tailing in this case (we need to involve the ops team and address any processing delay)
• 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 -

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-548

• Shay Takore (AT&T) wants to help us see  Joining the ONAP Technical Community
• continuedmove guidelines meeting up to 9am EDT - publish to onap-discuss