Versions Compared

Key

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

...

The INFO.yaml also provides history of changes made to the group like addition and removal of 

members with TSC or coordinator approval references depending on the project rules. 


In case of ONAP, new committer requests need to be approved by the coordinator:  infrastructure-coordinator@onap.org

More information in Technical Community Coordinators

If there is no response, it can be escalated to the TSC.


Every time there are changes to the team in general, the INFO.yaml must be kept updated by the tech team.

...

  1. We need to know the correct group name that owns appc repo
  2. Search for the "appc" project in  https://gerrit.onap.org/r/#/admin/projects/ 
  3. Go to the "Access" tab: https://gerrit.onap.org/r/#/admin/projects/appc,access
  4. Look at the "Owner" which matches "onap-gerrit-appc-committers" 

An example for a child repo:

  1. We need to know the correct group name that owns aai-common repo
  2. Search for the "aai-common" project in  https://gerrit.onap.org/r/#/admin/projects/ 
  3. Go to the "Access" tab: https://gerrit.onap.org/r/#/admin/projects/aai/aai-common,access
  4. Notice there is no "Owner" information which indicates is a project inheriting rights from another
  5. In this case, Rights Inherit From: aai
  6. Click on the link "aai" https://gerrit.onap.org/r/#/admin/projects/aai,access
  7. Find the "Owner": onap-gerrit-aai-committers

Inheritance is no longer supported in LDAP groups. We currently have 1 LDAP group mapped to 1 repo.

When to update INFO.yaml

The INFO.yaml file must exist on every single Gerrit repo. Even if the Gerrit repo is sharing permissions from a parent repo.

...

Only LF has permissions to view the actual LDAP groups. The teach teams can request this information to LF Releng members any time.


There is no automation behind updating Automation is now supported on INFO.yaml and the actual LDAP groupchanges. The changes still need to be performed by LF Releng to 

match what the INFO.yaml file describes. 

...

The process looks like this:

  • Tech team modifies/adds a new INFO.yaml file
  • Tech team gets the change merged in gerrit.onap.org
  • Automation will create a similar change in gerrit.linuxfoundation.org
  • The change will get merged too and perform the changes in LDAP directly with no manual intervention needed.


Tips on finding the right timezones

...