Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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
  • RI related
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-51
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-118
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-123
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-122
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-111
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-43
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-47


    ONAP Log Locations

  • Audit related
  • Logging Reference Implementation#DI3:20171231:Audit:MixedversionofEELFdependency
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-110
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-47
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-124
  • LOG jiras in OOM tracking
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-101
  • Doc related
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-91
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-98
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-105
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-97
  • R1 carry over
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-102
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-63
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-84
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-99
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-87
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-85
  • Secondary
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-94
  • Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyLOG-48
     blocked by 
    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyOOM-508
  • 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 
  • 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


...