New Major Distro Release Procedure

This page will cover all the components of the Upstream testing process that need to be modified in order to start building packages for and testing new major Linux distribution versions.

1. ceph-cm-ansible
   1. Add the distro to Cobbler
      1. You will likely need to provision a machine with Cobbler and tweak the packages that get installed in the kickstart
         1. If you haven't already, put set-next-server-local.sh in place on your workstation.
         2. See set-next-server
   2. Create the roles/testnode/vars/distro_majorversion.yml file
      1. See https://github.com/ceph/ceph-cm-ansible/blob/master/roles/testnode/vars/ubuntu_18.yml for an example.
   3. Create the roles/testnode/templates/ssh/sshd_config_distro_majorversion.yml file
   4. You will also likely need to tweak the packages in this file as package names change or get deprecated
2. FOG
   1. Capture new OS image(s)
3. teuthology
   1. Add to the distro map
4. Prado [DEPRECATED] only needs modifying if you're adding a new distro entirely
5. Shaman
   1. Add the new distro to the appropriate codename maps here
   2. Redeploy
6. Chacra
   1. Add the new distro here
   2. here too
   3. Redeploy
7. Mita [DEPRECATED]
   1. If necessary, add the distro to prod_nodes.py
      1. If you're adding a new distro entirely, you'll also need to add the Openstack image to the appropriate region.
   2. Redeploy
8. To test actual builds on the new distro:
   1. Reimage a Jenkins builder with the new distro and connect it to Jenkins with labels that will prevent it from picking up jobs from the queue. (e.g., installed-os-noble x86_64 noble gigantic adami)
   2. In ceph-build.git, cp -r the ceph-dev and ceph-dev-build job configs to a new temporary directory (e.g., cp -r ceph-dev ceph-dev-noble)
      1. Rename the jobs in each job yml to something like 'ceph-dev-noble' and 'ceph-dev-build-noble'
      2. Add the new distro name in the appropriate spots (e.g., noble goes above or below jammy)
      3. Add your new job names under copyartifact in ceph-dev-setup/config/definitions/ceph-dev-setup.yml so your temp jobs can copy artifacts from ceph-dev-setup.
   3. for job in ceph-dev-noble/config/definitions/ceph-dev.yml ceph-dev-build-noble/config/definitions/ceph-dev-build.yml ceph-dev-setup/config/definitions/ceph-dev-setup.yml; do jenkins-jobs –conf ~/.jenkins_jobs_jenkins.ceph.com.ini update $job; done
   4. Go to your job in Jenkins (e.g., https://jenkins.ceph.com/job/ceph-dev-noble) and start a new build of the main branch
9. Jenkins Job Configs: See https://github.com/ceph/ceph-build/pull/1022 as an example. It is not all encompassing! I missed a few spots in that PR.
   1. Don't forget build_utils.sh
10. If necessary, create a new vagrant repo
    1. Download the latest vagrant version from https://releases.hashicorp.com/vagrant/
    2. Using Ubuntu Jammy as an example:

       wget https://releases.hashicorp.com/vagrant/2.2.19/vagrant_2.2.19_x86_64.deb
       ls vagrant_2.2.19_x86_64.deb | chacractl binary create vagrant/latest/HEAD/ubuntu/jammy/x86_64

11. Once you have a successful Ceph build and repo for this new OS version, change the default in ceph.git like this and this.
12. Also in teuthology like this.