...
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:// |
|---|
net/wiki/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. |
|---|
M3 acceptance - Logging Beijing - M3 API Freeze Milestone Checklist- Luke helping ESR project with filebeat to kibana connectivity
- Multicloud commits for python logging - Liang, Alexis, Avdhut
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key MULTICLOUD-151 - Jenkins/sonar config for dual java/python nature of repo - https://gerrit.onap.org/r/#/c/33363/
- Logging format questions from Liang
- Start architecture review for Cassablanca
- Discussion in Arch meet about fluentd (Parvis Yegani) - fluent-bit - look at https://github.com/fluent/fluent-bit
- Fluend is in the list of alternatives including using a DeamonSet
Jira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key LOG-169 - Luke to enter templating epic for Cassablanca - will also put any files into https://git.onap.org/logging-analytics/tree/reference
- Mike to scope cassablanca epics for arch meeting next week