Versions Compared

Old Version 13

changes.mady.by.user cl664y@att.com

Saved on

compared with

New Version 14

changes.mady.by.user Kenny Paul

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Duration

Agenda Item

Requested byNotes / Links
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

-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


  •  Jessica Gonzalez send an email to release list that summarizes the specific = naming conventions conventions & job failure analyzer  



  • 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 =======================


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 minsRelease status


  • Jira Legacy
    showSummaryfalse
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyREQ-396
     
5 minsUpcoming Events


10 minsRemaining Action Items



...