PTL 2019-10-28

Owned by David McBride
Last updated: Apr 27, 2020 by cl664y@att.com
6 min read

Agenda

START RECORDING

Duration

Agenda Item

Requested byNotes / Links
1 hour

Cross-project discussions

Pamela Dragosh

New Policy API - SO/SDNC - OK?

LF IT Support

Jessica Gonzalez
  • Review unused Jenkins Jobs <Jess to add the list> CIMAN-339 - Getting issue details... STATUS
    • Two area affected: storage and builders
    • Task is to reduce costs
    • Teams running a combination of old and new jobs. Need to make sure that all old jobs are deprecated.
    • All changes to be documented in JIRA ^^

Testing Improvement

cl664y@att.com
  • ONAP "Use Case/Requirement" Integration Lead
  • these will be the people for each usecase/requirement that will be reporting to the integration team - usecase/requirement-by-usecase/requirement
  • Integration leads are listed on the Frankfurt Release Requirements wiki: Frankfurt Release Requirements
  • Integration leads will be reporting their test results on the Integration Weather Board for Frankfurt Release that will be created by the Integration Team

ACTION (Integration Team): Create Integration Weather Board for Frankfurt Release

CSIT Review

Morgan Richomme

Lasse Kaihlavirta

  • Currently few failing jobs - please direct attention to getting these tests functioning correctly.
  • Will continue to review here (ptl mtg)
  • Brian Freeman notes that the usecase master verify job has not run successfully for a month
  • Useless CSIT test elimination

ToolChain Improvement

cl664y@att.com
  • Impact Assessment on the tool-chain i.e. JJB jobs using some Python 2 scripts
  • David McBride notes that there is a milestone task to identify python in use


  • Request to add pylint as part of our toolchain to improve code quality. Pylint is a source-code, bug and quality checker for the Python programming language
  • No feedback from the PTL on the call so let's move to the implementation.
  • ACTION (LF IT): Share the roadmap of the pylint implementation

Other Improvement suggestion

Release Improvement

David McBride

Sofia Wallin

Any feedback regarding

#1 Frankfurt Documentation

not adding additional work , only creating greater visibility for progress tracking of deliverables
concerns expressed over low participation in docathons

Sofia Wallin will be providing a releasenote template. Currently there is a template that defines content but not style. 

#2 Release Planning Template

feedback has been minimal. Today is the deadline.

#3 Mx Milestone - Frankfurt Deliverables by Milestone


#4 Code Impact View per Component - Frankfurt Code Impact View per Component

  • Comment:  start earlier in the release cycle

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


Would you like to get the PTL agenda every Friday through "onap-release" mailing list?

No agenda email was requested by the PTLs - PTLs should look at the meeting page for the agendas

Subcommittee Updates for PTLs

Paweł Pawlak

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).

Seshu Kumar Mudiganti & Pamela Dragosh both note that a flat 5% effort will vary greatly between projects.

Vijay Kumar & Manoop Talasila note that older code is time consuming and they do not have available resources 

Rationale: 3 security maturity KPIs:

  • fixed OJSIs tickets
  • CII Badging
  • known vulnerabilities management

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

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

cl664y@att.comTSC 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

David McBride

Paweł Pawlak djhunt

Alla.Goldner

Stephen terrill

Hui Deng  Andy Mayer

Pamela Dragosh

El-Alto:

  • Follow-up on the remaining El Alto Sign-off conditions: Release note updates and Vulnerability tables
  • OOM Tagging

Frankfurt:

  • Collect questions/concerns from the teams
    • Any clarification required regarding Use Cases/Requirements
      • Security requirements demystification - Paweł Pawlak , Amy Zwarico 
      • S3P Frankfurt requirements - same as Dublin
      • Anything else? 
    • Any Resource gap identified
      • Call for Technical Support Expertise for the Documentation project
      • Call for Testers to validate Security requirements related to Portal SDK
    • Anything else?
5 minsIncoming Events

David McBride

ONAP/CNTT F2F Event in January 13-16th, 2020 - Prague - Registration is open: reg link
5 minsRemaining Action Items

David McBride

PTL Weekly ONAP12, Mon UTC 13:00

Zoom Chat Log 

06:06:09 From Catherine Lefèvre : Welcome back Kenny
06:06:13 From Pawel Pawlak (Orange) to Kenny Paul (LFN)(Privately) : hello Kenny, welcome back!
06:06:21 From Brian Freeman (AT&T) : did we talk about timezone change alread - ptl call disappeared from my calendar last week
06:06:45 From Chaker Al-Hakim to Kenny Paul (LFN)(Privately) : glad to have you back. I hope all is well
06:07:00 From Kenny Paul (LFN) : thanks everyone :-)
06:07:29 From Jimmy Forsyth (AT&T) : @Brian I heard Catherine say that the call is now locked to UTC so for those in US/Eastern the call will start at 8AM
06:08:41 From Brian Freeman (AT&T) : my calendar says PTL call is always at 9 AM Eastern even with DST off ?
06:09:02 From Brian Freeman (AT&T) : but it could also be outlook changing history
06:11:54 From Pamela Dragosh : I thought the TSC was the only call locked to UTC. But maybe I’m wrong. Perhaps PTL should also be locked if it isn't.
06:13:40 From Jimmy Forsyth (AT&T) : If lock this call at 13:00 UTC it moves to 5AM for those in PST, which is outside community guidelines
06:14:25 From Brian Freeman (AT&T) : I think that was why we left PTL call at 9 AM Easter for both DST and STD
06:15:12 From Pamela Dragosh : Ah makes sense
06:21:52 From Pamela Dragosh : The verify jobs should not be listed on that view.
06:26:32 From Brian Freeman (AT&T) : but if a verify never succeeded we have a problem - agree perhaps we need two views to help highlight bad jobs vs failed verify
06:28:26 From Pamela Dragosh : If a verify didn’t succeed, then someone just didn’t get their code right. But it never got merged. So how is that an issue?
06:28:41 From Pamela Dragosh : The “job” isn’t broken.
06:29:29 From Taka Cho : APPC csit has 3 failure CDT GUI testcase. I suspect its timing issue for selenium. Those 3 testcase was OK from yesterday's csit Jenkins job. I will check further,
06:31:42 From Dan Timoney : New third party library/FOSS identification probably makes more sense as part of M4 vs M1
06:33:32 From Catherine Lefèvre : @All- I guess we need to follow-up concerning the PTL call due to clock change
06:33:47 From Pamela Dragosh : Agree with Dan - how would you know what new libraries you are bringing in until you actually do the development.
06:34:44 From Catherine Lefèvre : @FOSS - it was part of M1 to capture as soon as possible the impacts of any seed code
06:35:03 From Catherine Lefèvre : then should be reconfirmed at M4
06:35:44 From Catherine Lefèvre : as an example Telstra has seed code already available for SDC
06:36:02 From Brian Freeman (AT&T) : Selenium is a pain so I can easily see that - let me know if need any help on the selenium
06:36:14 From Catherine Lefèvre : so knowing if there is any license/FOSS issue prior pushing the code will help Ofir to assess the risk of the seed code
06:36:37 From Brian Freeman (AT&T) : if a verify never succeeded over months its a problem
06:36:44 From Pamela Dragosh : No it isn’t Brian.
06:37:02 From Pamela Dragosh : The job may be just fine.
06:37:03 From Taka Cho : @Brian, thanks! CDT gui code did not change in the past few weeks.
06:37:48 From Brian Freeman (AT&T) : windriver infrastructure changes and robot selenium upgrades could cause a selenium test case to start failing - various timing issues
06:38:16 From Brian Freeman (AT&T) : so jenkins in lf could have the same behavior
06:39:19 From Taka Cho : ok i got it. which tenant in windriver for csit jobs. I can check further?
06:51:43 From Dan Timoney : Less email is always good ;-)
07:00:11 From Brian Freeman (AT&T) : @taka - I had to download the zip file to get the log.html to download/.open - looks like the page is not painting after the short sleep on a save etc
07:00:26 From Brian Freeman (AT&T) : 5 seconds is way too short
07:04:38 From Vijay Venkatesh Kumar (AT&T) : @David/Kenny - you have tagged the wrong user for DCAE update discussed for subcommittee update; my id is @Vijay Venkatesh Kumar. Just want to make sure you send the updates to right Vijay...;)
07:05:38 From Kenny Paul (LFN) : @Vijay sorry. fixed.
07:06:06 From Vijay Venkatesh Kumar (AT&T) : Thanks @Kenny
07:16:14 From Catherine Lefèvre : Early_Drop = 5.0.0 (full regression test, daily health checks) El Alto release = 5.1.0
07:17:25 From Catherine Lefèvre : https://docs.onap.org/en/elalto/release/index.html#release-notes
07:17:30 From Catherine Lefèvre : Release Version: 5.0.1
07:21:24 From Catherine Lefèvre : Sept 30th - Release Version: 5.0.1
07:21:52 From Catherine Lefèvre : Sep 23rd -Release Version: 5.0.1
07:22:07 From Catherine Lefèvre : Sep 15th -Release Version: 5.0.1
07:22:29 From Catherine Lefèvre : Sept 9th - -Release Version: 5.0.1
07:22:43 From Catherine Lefèvre : Aug 26th - -Release Version: 5.0.1
07:23:59 From Catherine Lefèvre : ====================
07:24:08 From Catherine Lefèvre : can we type the new version decision?
07:26:51 From Catherine Lefèvre : Team - I need to drop
07:27:07 From Catherine Lefèvre : @Mike/Jessica -let me know when the tagging is done

Action Items 

  • Morgan Richomme  create Frankfurt Weather Board
  • Jessica Gonzalez Share the roadmap of the pylint implementation
  • @PTLs provide comments o El Alto retrospective to the onap-release list by Nov. 15.