Getting packages ready for new OpenStack releases

When a new OpenStack release is delivered upstream, there is a set of steps that must be performed in RDO to build and publish new packages both in RDO CloudSIG and RDO Trunk repos.

1. RDO infrastructure preparation

Some weeks before a new OpenStack release is published, some changes in RDO tools and infrastructure are needed to get the delivery pipeline ready. These tasks are mostly done by RDO core members, for example:

  • Adding a new DLRN builder following stable/ branch.
  • Creating CI jobs for new branches.
  • Including new release in automation bots.
  • etc…

Once these tasks are done, it will be announced in rdo mailing lists so that package maintainers can start carrying out the next steps.

2. Update package distgits.

Around RC1 time (check upstream schedule), package maintainers should send required reviews to rpm-master branch to adjust distgits contents to the changes occurred during the cycle. This typically includes updating minimal versions for existing dependencies, removing not longer used requirements, etc… Note that rdopkg reqcheck command can be used to check changes in dependencies.

3. Create new branch <release>-rdo in distgits.

Once the distgits content is ready for the new release, package maintainers must request a new branch <release>-rdo for their packages. This can be done by sending a review to the corresponding package resource in gerrit configuration following next steps:

  1. Clone config project:

     git clone
  2. RDO gerrit config project contains a resource file for each managed package. Look for the one containing the package where the new branch is needed:

     cd config/resources
     grep <project name>-distgit *


     $ grep novaclient-distgit *
     openstack-novaclient.yaml:    openstack-novaclient-distgit:
     openstack-novaclient.yaml:    openstack/novaclient-distgit:
     openstack-novaclient.yaml:      acl: openstack-novaclient-distgit
  3. Edit the yaml file. Look for <project name>-distgit under repos section. If it doesn't have a branches sub-section, add it. Inside branches add a new line with the branch name:

     <release>-rdo: <commit id for last commit in rpm-master in the project distgit>

    The commit id of the last commit in the project distgit must be specified as it will be used as starting point for the new branch. For example:

         acl: openstack-novaclient
         description: Mirror of upstream novaclient (mirror + patches)
         acl: openstack-novaclient-distgit
         description: Packaging of upstream novaclient
           pike-rdo: 71fafbb21c2dc8dd518a0c3d5f635b6b04100661
           queens-rdo: c2e115b3283fd776cabaf68d0eb7940030fc1821
           rocky-rdo: c0663f17adf0bc05999d8b2caabbe9270af93c27
           stein-rdo: 9d0b15be17c3aaf39dccd5a0ab8fe01801d6484d
  4. Commit the change and send the review using commands:

     git commit -a -m "Create new branch <release>-rdo"
     git review

    An example of a new branch request can be found here

4. Request new builds for CloudSIG repos.

After new branches are created in distgits and upstream projects have pushed tags for new RC or final releases (depending on the release model adopted for each upstream project), new builds are created using Centos Build System by sending a review to the <release>-rdo branch as shown in this doc. Note that RDO uses a bot to propose reviews for new releases automatically in most cases, however it's recomended that package maintainers pay some attention on this process and send a review if reviews have not been created on time.

5. Pin branchless projects in rdoinfo.

According to stable policies, RDO Trunk repos shouldn't follow master branch after GA. By default, DLRN builders are configured to use stable/<release> branches for non-master releases. However, some projects packaged in RDO don't create stable branches upstream or use different ones. For example, some independent projects create a branch for each supported major package version instead of OpenStack release. For those cases, packages should be pinned to a specific git tag, commit or branch. This is done by sending a review to rdoinfo project using source-branch parameter for the release tag as in this example.