[tripleo] Initial plans around stable/wallaby branch on CentOS Stream 9
Hello,
The tripleo-ci team is working on drafting the plans for bootstrapping tripleo stable/wallaby branch on CentOS Stream 9.
During adding the support of CentOS Stream 9 for tripleo master, we have added lots of patches for example: * tripleo-common: https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%2522... * tripleo-heat-templates: https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%2522... * https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%2522...
Backporting these patches in chains for stable/wallaby, will create lots of merge conflicts (few of them are big changes) and might get messy. RDO wallaby DLRN builder bootstrap has also started.
In order to avoid that, we are coming with following plan: - Pick the major change and backport that one and add all the remaining changes in that itself (not a clean backport): https://review.opendev.org/c/openstack/tripleo-common/+/821511 - Make sure these backported changes passed on CentOS-8 CI jobs - Once the RDO CS9 wallaby packages are available, Start bootstrapping the container and Image build job on CS9 via testproject.
Let us know your thoughts around this.
Thanks,
Chandan Kumar
On 12/13/21 10:52, Chandan Kumar wrote:
Hello,
The tripleo-ci team is working on drafting the plans for bootstrapping tripleo stable/wallaby branch on CentOS Stream 9.
During adding the support of CentOS Stream 9 for tripleo master, we have added lots of patches for example:
- tripleo-common:
https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%2522...
- tripleo-heat-templates:
https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%2522...
Backporting these patches in chains for stable/wallaby, will create lots of merge conflicts (few of them are big changes) and might get messy. RDO wallaby DLRN builder bootstrap has also started.
In order to avoid that, we are coming with following plan:
- Pick the major change and backport that one and add all the
remaining changes in that itself (not a clean backport): https://review.opendev.org/c/openstack/tripleo-common/+/821511
- Make sure these backported changes passed on CentOS-8 CI jobs
- Once the RDO CS9 wallaby packages are available, Start bootstrapping
the container and Image build job on CS9 via testproject.
Let us know your thoughts around this.
Hey Chandan,
As discussed before: I'm all for this solution. There are multiple advantages, among them: less CI hassle, less conflicts, faster merges.
Cheers,
C.
Thanks,
Chandan Kumar
On Mon, Dec 13, 2021 at 5:12 AM Cédric Jeanneret cjeanner@redhat.com wrote:
On 12/13/21 10:52, Chandan Kumar wrote:
Hello,
The tripleo-ci team is working on drafting the plans for bootstrapping tripleo stable/wallaby branch on CentOS Stream 9.
During adding the support of CentOS Stream 9 for tripleo master, we have
added
lots of patches for example:
- tripleo-common:
https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%2522...
- tripleo-heat-templates:
https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%2522...
https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%2522...
Backporting these patches in chains for stable/wallaby, will create lots of merge conflicts (few of them are big changes) and might get messy. RDO wallaby DLRN builder bootstrap has also started.
In order to avoid that, we are coming with following plan:
- Pick the major change and backport that one and add all the
remaining changes in that itself (not a clean backport): https://review.opendev.org/c/openstack/tripleo-common/+/821511
- Make sure these backported changes passed on CentOS-8 CI jobs
- Once the RDO CS9 wallaby packages are available, Start bootstrapping
the container and Image build job on CS9 via testproject.
Let us know your thoughts around this.
Hey Chandan,
As discussed before: I'm all for this solution. There are multiple advantages, among them: less CI hassle, less conflicts, faster merges.
+1 to this approach. We looked at backporting patch by patch and it was much more complicated due to the same files changed in multiple patches.
Cheers,
C.
Thanks,
Chandan Kumar
-- Cédric Jeanneret (He/Him/His) Sr. Software Engineer - OpenStack Platform Deployment Framework TC Red Hat EMEA https://www.redhat.com/
Hello,
On Mon, Dec 13, 2021 at 4:59 PM Ronelle Landy rlandy@redhat.com wrote:
Below are the two patches which need review. * https://review.opendev.org/c/openstack/tripleo-ansible/+/821663 * https://review.opendev.org/c/openstack/tripleo-common/+/821511
For tripleo-heat-templates and python-tripleoclient all the cs9 patches are backported to stable/wallaby branch. I will look into other projects which need backport.
Thanks,
Chandan Kumar
participants (3)
-
Chandan Kumar
-
Cédric Jeanneret
-
Ronelle Landy