- Zoom bridge: https://zoom.us/j/283628617?pwd=aWM3WjliUkFtcGFPUEdEMStIRll1UT09 passcode: 241308
- PTL Recordings
- Antitrust Policy Notice
We will start our meetings by mentioning the project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.
Agenda
START RECORDING
| Duration | Agenda Item | Requested by | Notes / Links | ||||||
|---|---|---|---|---|---|---|---|---|---|
| 1 hour | Cross-project discussions | Lasse Kaihlavirta - Guidelines update for SNAPSHOT/STAGING redesign for Honolulu | Docker Image Build Guidelines (proposal for Honolulu) Independent Versioning and Release Process (proposal for Honolulu) | ||||||
LF IT Support | |||||||||
| Testing Environment | |||||||||
Testing Improvement | |||||||||
CSIT Review | |||||||||
ToolChain Improvement | |||||||||
| Documentation | |||||||||
Other Improvement suggestion | |||||||||
Subcommittee Updates for PTLs | SECCOM: presentation of Best Practices (new code only) SECCOM plans to propose as Best Practices (global requirements)
| ||||||||
| PTL Update | DmaaP | Thank you Mandar Sawantfor your great leadership as DMaaP PTL Welcome Fiachra Corcoran, our new DMaaP PTL | |||||||
Sharing Best Practices | |||||||||
| IF TIME ALLOWS .... | |||||||||
| 15 mins | Release status | Guilin - Congratulations Team - Guilin is now Signed-Off !!! Final steps before Guilin Marketing Launch:
Guilin Maintenance
Honolulu Release
Krzysztof Opasiak says that PTLs need to agree on global requirements before they are voted on by the TSC. Need to clarify what PTL "agreement" means, since the PTLs are not a voting body. Amy Zwarico asserts that long standing SECCOM requirements (e.g., Java 11, Python 3) should be approved as Global Requirements without first being Best Practice, since they have previously been approved by the TSC and have been requirements for some time. cl664y@att.com is concerned that Best Practice and Global Requirements won't be implemented unless we continue with the practice implemented in Guilin of a "tax" on companies wishing to implement new features. This worked well in Guilin to get NFRs implemented. Can we incorporate this into the new release process? | |||||||
| 5 mins | Upcoming Events | Linux Foundation Training "Cyber Monday" Sale Ends Dec 8.
LFN Developer & Testing Forum - Feb 1 - 4, 2021.
NO PTL Call on 12/21, 12/28? No objections to canceling meeting on 12/21 and 12/28. NO TSC Call on 12/24 and 12/31 | |||||||
| 10 mins | Remaining Action Items | ||||||||
...
06:25:26 From Kenny PAUL (LFN) : https://lf-releng-docs.readthedocs.io/en/latest/environment-overview.html
06:48:20 From Morgan Richomme : https://logs.onap.org/onap-integration/weekly/onap_weekly_pod4_master/11-08-2020_06-11/security/versions/versions.log
06:49:47 From Christophe CLOSSET (AT&T) : Lots of Filebeat containers still onboarding python 2
06:50:25 From Krzysztof Opasiak : and it's impossible to fix it beacuse even newest filebeat image contains python2
06:50:30 From Catherine Lefevre : i do not think we wilbased on new release cadences, l do not thin there is any GR in Honolulu - Best practices should be firs agreed by the PTLs
06:51:16 From Catherine Lefevre : Based on the new release cadence, I do not think there will be any GR, First PTLs need to agree on best practices
06:51:23 From Christophe CLOSSET (AT&T) : Wasn’t filbeat used for the logging project ? Maybe we can just remove them now…
06:52:07 From Krzysztof Opasiak : @Catherine. Yes but best pracitce may be apporved any time not just at milestone so if TSC would approve this as BP then at milestone it may vote to have this as GR
06:53:02 From Morgan Richomme : https://git.onap.org/integration/seccom/tree/recommended_versions.yaml
06:54:46 From Catherine Lefevre : ok -i thought that TSC only approves GR, not best practice
06:55:08 From Catherine Lefevre : so we need to update definition if TSC also needs to approve Best practices
06:55:24 From Krzysztof Opasiak : They approve them but not at milestone
06:55:26 From Dan TIMONEY (AT&T) : The onap/integration-python image currently installs python 3.8 I believe
06:55:51 From Catherine Lefevre : hum - well at M1 they need to approve
06:56:08 From Dan TIMONEY (AT&T) : $ docker run -ti --entrypoint=s3.onap.org:10001/onap/integration-python
/app $ python --version
Python 3.8.2
06:56:17 From Krzysztof Opasiak : GR yes but BP may be approved even this Thursday if TSC would like to do so
06:56:38 From Krzysztof Opasiak : basically at any point someone may propose a new best practice as it's only for a new code
06:56:44 From Catherine Lefevre : well it is not the current definition
06:57:02 From Krzysztof Opasiak : oh ok where we made the mistake? Could you share the link>
06:57:17 From Catherine Lefevre : currently best practices should be reviewed by PTLs and then it is up to them to decide if. they will do or not
06:57:46 From Krzysztof Opasiak : That's for GR
06:58:06 From Catherine Lefevre : sure - i can not post link for the moment, i am connected with my iPad
06:58:28 From Krzysztof Opasiak : for Best Practices we shoudl focuse only on technical aspect. Is it a good change from technical perspecive and the right thing to do or not
06:58:38 From Catherine Lefevre : but see the definition on the Honolulu requirements and Honolulu impact component
06:59:00 From Morgan Richomme : https://git.onap.org/integration/seccom/tree/recommended_versions.yaml?h=guilin
06:59:08 From Kenny PAUL (LFN) : need to drop to start the LFN SPC meeting.
06:59:09 From Catherine Lefevre : i also do not recall BP to be approved by TSC on the release cadence wiki
06:59:09 From Morgan Richomme : https://git.onap.org/integration/seccom/tree/recommended_versions.yaml?h=honolulu
06:59:29 From Catherine Lefevre : currently there is nothing for the TSC to approve
06:59:53 From Krzysztof Opasiak : https://wiki.onap.org/display/DW/Final+Proposal+Details
07:00:04 From Catherine Lefevre : also it you think that TSC can approve any BP then when is it applicable since it has a strong show stopper for PTLs if they do not meet BP and GRs
07:00:08 From Morgan Richomme : @catherine, I got some feedback from the stability tests
07:00:10 From Krzysztof Opasiak : this is the wiki page I put together some time ago and there are:
07:00:18 From Catherine Lefevre : so it would not be unfair to approve BP at M$
07:00:20 From Catherine Lefevre : M4
07:01:05 From Krzysztof Opasiak : "Anyone in the community can propose a new best practice at any time."
07:01:13 From Dan TIMONEY (AT&T) : Sorry need to drop for another call
07:01:28 From Krzysztof Opasiak : "The BP has been socialized with required parties and now it is ready to be voted by the TSC"
07:02:00 From Catherine Lefevre : yes socialized but what’s the feeedback
07:02:21 From Amy Zwarico (AT&T) : https://wiki.onap.org/display/DW/Database%2C+Java%2C+Python%2C+Docker%2C+Kubernetes%2C+and+Image+Versions
07:03:10 From Amy Zwarico (AT&T) : Python version for Honolulu: 3.9
07:15:20 From Morgan Richomme : I need to drop to another meeting, I will share by mail
07:24:15 From Krzysztof Opasiak : BP must be followed by the new code
07:24:23 From Krzysztof Opasiak : GR must be followed by everything
07:24:40 From Krzysztof Opasiak : BP MAY be followed by legacy code
07:25:36 From Christophe CLOSSET (AT&T) : ********* Best Practice: Design pattern recognized by the community. Must be followed by the new code. The best practice owners to present their best practice to the PTLs and then to the TSC to review/to approve as best practice.
07:26:06 From Christophe CLOSSET (AT&T) : ********* Global requirement: Best Practice that must be applied to whole code base during a particular release (formely called TSC MUST HAVE). The best practice owners to present their approved best practices to the TSC to review/to approve as GR.
07:27:01 From Krzysztof Opasiak : +1
07:29:56 From Jim HAHN (AT&T) : Seems like move from BP to GR should require review by PTLs, too
07:30:12 From Krzysztof Opasiak : +1 to Jim
07:30:29 From Krzysztof Opasiak : Fully agree. The flow should be:
07:30:35 From Krzysztof Opasiak : 1) Introduce as BP to PLT
07:30:50 From Krzysztof Opasiak : 2) Get it approved by TSC (with PTL agreement)
07:31:15 From sunder tattavarada : I'm sorry; need to drop for another call.
07:31:21 From Krzysztof Opasiak : 3) Propose it to become GR (at least 2 weeks prior to M1 to allow PTLs review)
07:31:37 From Dan TIMONEY (AT&T) : Sorry, need to drop
07:31:45 From Krzysztof Opasiak : 4) Make TSC vote on proposed GR at M1
07:38:56 From Catherine Lefevre : thanks Krzysztof - i have updated Honolulu release reps and impact view per component - let me know if not
07:39:33 From Catherine Lefevre : reps -> reps
07:41:39 From Krzysztof Opasiak : sorry I need to drop
07:48:07 From Toine SIEBELINK (EST) : HAVE TO DROP
07:48:18 From Toine SIEBELINK (EST) : (apologies for Caps Lock)
07:49:27 From Sylvain Desbureaux (Orange) : OOM-2621 ?
07:49:37 From Vijay Venkatesh Kumar (AT&T) To David McBride(privately) : OOM-2641
07:50:04 From Vijay Venkatesh Kumar (AT&T) : OOM-2641
Action Items
- Type your task here, using "@" to assign to a user and "//" to select a due date