1 hour

Cross-project discussions

@cl664y@att.com

OOM/Integration/SECCOM: List of CI enforcements to be discussed on 7/20 with the PTLs including timeline/incremental implementation and graceful period

#1 Establish the list of enforcements planned for Guilin through the OOM gating 

• REQ-361 Automated certifications retrieval including HTTPs enablement

• REQ-362 All containers must run as non root

• REQ-373 Python 3.8 support - required notification from the PTLs when the migration will be finalized before being enforced

• REQ 351 Java Language support (v11) - required notification from the PTLs when the migration will be finalized before being enforced

#2 When these enforcements will be activated? As soon as the project team will report development completion for their project based on their associated Guilin commitments; no later than M4 Guilin (Code completion) - Guilin Impact View per Component

#3 Can we establish a graceful period so PTLs can communicate to their projects team?

ACTION (David) - Notify the PTLs via onap-release 

ACTION (OOM/LF IT) - Check the feasibility to have these enforcements as part of the verify job.

LF IT Support

@cl664y@att.com

@Jessica Gonzalez

• Remaining open actions regarding "PTL Toolchain" improvements

  • New Repo creation (Jessica) - enhance https://lf-onap.atlassian.net/wiki/display/DW/Self+Repo+Creation+via+INFO.yaml with the latest proposal

  • Issue Template: OOM, Integration – these projects require a customized JIRA Issue template – they will work with David, Jessica based on their needs

  • Simplify CI errors - 

    -Jessica will investigate and will come back about the possibilities - https://plugins.jenkins.io/build-failure-analyzer/ plug-in

    -Dan T to provide additional information to Jessica (archive item) 

-LF IT will investigate to get an alias covering CI_Management to cover LF staff. If there is a request to add ONAP Community Member then Policy to be reviewed including the impacts

• Integration_committers:

• #1 Align on the alias i.e. <project name>_<repo>_committers where <repo> is optional

    integration_committers

    aaf_authz_committers

    etc ….

       PTL can create/manage the list manually as a first step

  #2 LF IT will investigate if we could potentially automate the creation of the alias based on the information found in INFO.yaml

  #3 LF IT will investigate to add “https://gerrit.googlesource.com/plugins/reviewers/”plug-in per repo considering the alias

  #4 LF IT will investigate to get an alias covering CI_Management to cover LF staff

• Allow group members

  • Check the logic-is it possible based on info from LDAP?

    • you can see the name the name of the LDAP group by looking at the access tab in gerrit

•  

  By default the INFO.yaml should be at the root repo.

  If a project needs to have different rights per repo then the INFO.yaml inside the sub-repositories to be considered

•  Put relevant files in the repo - Assess with LF IT how we can automate the docker tag versioning, similar to Tizen project

======== Next Steps: LF IT will present their findings after confirmation of TSC vote about Short Term Path - Completion TSC vote by 7/21 =======================

• Jenkins Build Failure Analyzer Plugin Jenkins -> Configuring Jenkins Job Failure Analyzer

  • Permissions to edit causes through support.linuxfoundation.org 

Testing Environment

Testing Improvement

CSIT Review

ToolChain Improvement

Documentation

Other Improvement suggestion

"30 mins practice" concept 

Subcommittee Updates for PTLs

Sharing Best Practices

IF TIME ALLOWS ....

15 mins

Release status

• https://lf-onap.atlassian.net/browse/REQ-396 

  • https://lists.onap.org/g/onap-tsc/message/6773

• El Alto Maintenance

  • Candidate Issues

  • Branch verification?

  • Container status?

  • Release note update?

• Frankfurt Maintenance

  • Candidate Issues

  • Integration Dashboard

  • Container status?

  • Release note update?

• Guilin

  • Guilin Impact View per Component

  • Review M2 tasks

5 mins

Upcoming Events

• Open Networking & Edge Summit North America 2020  September 28 & 29, 2020 (Virtual Event is now confirmed)

  • https://lists.onap.org/g/onap-tsc/message/6513

  • ONAP TSC Abstract “ONAP and Cloud Native” was approved.

10 mins

Remaining Action Items