Notes

Deliver python library (Thank you Liang Ke and   MULTICLOUD-151 - Logging Enablement IN PROGRESS  in the logging repo via the Multicloud team (ramki krishnan and Shankar Satyanarayanan interested)

Sonar must be above 50%, and address CLM

From Gildas summary

For Licensing and Vulnerability, you should ensure there is no Critical “Security” nor “License” issue.

Current report is available at https://nexus-iq.wl.linuxfoundation.org/assets/index.html#/reports/logging-analytics/d39f5b74afc8499787bc3e2864758524 and can be accessed from Jenkins/CLM tab search for “logging-analytics-maven-clm-master”.

For your convenience I have attached the report.

I think you can also update M3 template at https://wiki.onap.org/display/DW/Logging+Beijing+-+M3+API+Freeze+Milestone+Checklist and answer Yes to the first question (Has the Project team reviewed the APIs with the Architecture Committee (ARC)?

As you now filled out the M3 template, I will bring this to TSC on Thursday for review.


  • No labels

2 Comments

  1. Shishir Thakore Q: diff eelf and ecomp guidelines - need difference meeting

    Will take most of the meeting on the 20th do discuss this - all teams


    EELF 1.2 questions FQDN - why do we need these fields if they are not specified in the required field column

    Trevor Plestid Discussion invocationID should be sufficient for getting the caller  - can it cover off partnerName? - which is better for sequence diagram generation


  2. We need to look at and fix the issue in  OOM-324 - Getting issue details... STATUS