PTL 2019-11-04

Agenda

START RECORDING

Duration

Agenda Item

Requested byNotes / Links
1 hour

Cross-project discussions

New Policy API 

LF IT Support

Jessica Gonzalez
  • roadmap for pylint implementation
    • Try to align pylint for all the projects
    • It has been prototyped by several projects
    • Not blocking the code but it provides information to the PTLs regarding the quality of submitted code
    • It will be part of the Jenkins verify jobs
    • ACTION: pylint will be implemented in all the projects as an informational tool (similar to checkstyle for JAVA) for the PTLs/Committers about the quality of submitted code.It will be part of the verify Jenkins job but it will not return verify -1 by default except if PTL will raise the request to block the code. No action for the TSC.
  • IT-18078 integration/xtesting
    • Jessica says e-mail sent to TSC mailing list. Waiting for TSC approval.
    • ACTION: Kenny to review issue and determine need for TSC vote.
  • Issue (IT-18144) with the Frankfurt Maturity Matrix - Frankfurt Release Platform Maturity
  • When trying to update then getting the following message

I have tried to create v1 to fix the issue but the problem re-occurred.

ACTIONS:

#1 Seshu will create a ticket to fix v1 Platform Maturity - done IT-18144

#2 Jess will fix the current wiki page which is a current blocker for PTLs to complete their M1

#3 Jess will send a notice to onap-release, onap-tsc mailing list to provide guidelines in order to avoid this behavior in the future (not discard update?)

  • ONAP JIRA issue - RELENG-2517 -ONAP JIRA has invalid resolution type resulting in confusing behavior

       Old issue - maybe let's remind the ONAP Community about this limitation?

  • IT-17739/RELENG-2422 - new open ticket to address the template changes for docker tagging. Its pending on LF update.

Testing Environment

Testing Improvement

  • Currently few failing jobs - please direct attention to getting these tests functioning correctly.
  • Will continue to review here (ptl mtg)
  • Useless CSIT test elimination
  • ACTION: Morgan will send a notice to the PTLs to remind to review their CSIT jobs - if no action then clean-ups will be performed on Dec 3rd, 2019 - after the final review on PTL call (12/2)

ToolChain Improvement

  • El-Alto Retrospective - please submit your feedback by Nov 15th - these will be reviewed during the PTL Call on 11/18.
  • Release Note Template

Other Improvement suggestion

S3P Security maturity update proposal: Add at least 2 sections: vulnerabilities remediation  (OJSIs management + known vulnerabilities) and increased tests code coverage (example could be increase by 5% for each project).

Known vulnerabilities management - PLEASE complete your analysis, respond to comments for El Alto release. Table

Current OJSI performance Analysis

Still 38 OJSI tickets related to HTTP open while we expose only ~20 HTTP ports. We can close almost half as soon as we get the commit hash-id

Worst performing projects
  • CLI
    • 4 OJSI tickets open
    • 1 ticket with CVE
    • No activity at all
  • Logging
    • 9 OJSI tickets open
    • 1 ticekt with CVE
    • Very limited activity
  • MSB
    • 11 OJSI tickets open
    • 1 ticekt with CVE
    • No activity at all
Could be improved
  • APPC
  • DMAAP
  • INT
  • SDNC
  • SO
Please follow them
  • CLAMP
    • Average response time ~1 day
    • More advanced fixes provided in less than a month
  • Policy
    • Prompt response
    • Following the procedure
    • No open issues.
  • Portal
    • Recognition for the hard work
    • Not everything fixed yet but good progress made

OOM Helm charts password removal

Heads-up: Information (not the code) requested by the SECCOM must be provided as part of the Frankfurt release. Otherwise the component and its associated use cases/requirements will be descoped from the ONAP Frankfurt release. SECCOM will provide a proposal to the TSC on 10/31.

Sharing Best Practices

TSC El-Alto Demo Contest - DEMOS - R5 El-Alto Demos
  • Submission open till Nov. 8th, 2019
  • EAUG/TSC review/vote: from Nov. 11th to Dec 4th, 2019
IF TIME ALLOWS ....
20 minRelease status

Incoming EventsKenny Paul
  • PTL call is now planned @3pm CET, 9am EST, 6am PST, 8am CST, 10pm China Time, 7.30pm Indian Time
  • ONAP/CNTT F2F Event in January 13-16th, 2020 - Prague - Registration https://events19.linuxfoundation.org/events/lf-networking-ddf-plugfest-2020/
  • ONAP 2 day event before or after ONES North America (April 20&21) - Los Angeles (TBC)
  • ONAP DDF planned in June - under planning
  • ONAP 2 day event before or after ONS North Europe - Antwerp (TBC)
  • Survey coming from LFN for Dec OR Jan for steady-state full DDF meetings to all LFN communities & locations
10 minsRemaining Action ItemsPTL Weekly ONAP12, Mon UTC 13:00

Zoom Chat Log 

06:04:27 From Kenny Paul (LFN) : working on my audio
06:18:01 From Eric Debeau : Example of pylint configuration in multicloud: https://git.onap.org/multicloud/openstack/tree/ocata/tox.ini
06:19:07 From Morgan (Orange) : and in integration https://git.onap.org/testsuite/python-testing-utils/tree/robotframework-onap/tox.ini
06:21:43 From Pamela Dragosh : -1 to blocking code
06:22:21 From Sai Seshu : -1 many false positive 
06:22:29 From Sai Seshu : Need to provide explanation 
06:25:06 From Tony Hansen : flake8 incorporates pyflakes and pep8 together and is a reasonable addition to pylint
06:27:20 From Pamela Dragosh : David - forgot to mention at the beginning. But due to DST a lot of team meetings moved up an 1 hour. Some now fall at 5am PST. Can/Should they be updated?
06:31:59 From Jimmy Forsyth (AT&T) : Adding to Pam’s question, I am trying to update the calendar in groups.io per the wiki (https://lf-onap.atlassian.net/wiki/display/DW/Calendar+and+Bridge+FAQ#CalendarandBridgeFAQ-HowdoIchangeameeting?) and I am getting “sorry, that group does not exist” when I click on my meeting.
06:35:17 From Pamela Dragosh : Kenny - you can add me as a moderator for snap-discuss.
06:39:57 From Catherine Lefèvre : Team - just FYI- I am attending the SPC meeting in 20 mins, representing TAC team on behalf of Jason
06:40:07 From Kenny Paul (LFN) : @jimmy looking -
@pam thank you
06:42:00 From Taka Cho : One more very tiny issue I found for updating wiki: when I was trying to update wiki page with an "emoji". I got "wiki has communication error with server". when I took out emoji, the server communication error was gone and wiki can be updated...
06:44:41 From Sai Seshu : @pam I'm finding difficult to open up the support Linux page... Can you please help to raise the ticket for the page
06:45:00 From Vijay Venkatesh Kumar (AT&T) : IT-17739/RELENG-2422 opened to address the template changes for docker tagging. Its pending on LF update.
06:47:35 From Jessica W - LF : @Vijay.. Tony and Chris commented on RELENG-2422..can you please comment back?
06:49:08 From Catherine Lefèvre : @Jess, Vijay - I have added to the PTL wiki page so we do not forget it
06:49:23 From Pamela Dragosh : @sesh - IT-18144
06:49:33 From Catherine Lefèvre : thanks seshu
06:49:48 From Sai Seshu : @thanks pam
06:49:48 From Catherine Lefèvre : i guess it is to cover paltform maturity wiki
06:50:01 From Sai Seshu : Yes
06:50:30 From Catherine Lefèvre : thanks pam
06:51:06 From Vijay Venkatesh Kumar (AT&T) : @Jess - yes,  Tommy and Chris were clarifying the original ask for LF; this is still pending action though.
06:54:38 From Catherine Lefèvre : @Kenny, what's the e-mail subject regarding IT-18078 e-mail sent to the T
06:54:46 From Catherine Lefèvre : sc - can't find it - thanks
07:00:55 From Catherine Lefèvre : @Team - leaving the call - if any question then raise them to David - i will follow-up later with him - mailbox pretty full so response can be delayed - sorry
07:24:21 From Manoop Talasila - AT&T : I have to drop for another meeting. Thanks.

Action Items 

  • Kenny Paul determine whether TSC vote is required for IT-18078. See email sent to TSC mailing list.
  • Morgan Richomme send email notification to list to warn community about Dec 3 deletion of disabled Jenkins jobs
  • Krzysztof Opasiak setup separate meetings with MSB, Logging, and CLI projects (In that order) to discuss security maturity and open OJSI tickets.