<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Dec 13, 2021 at 5:12 AM Cédric Jeanneret <<a href="mailto:cjeanner@redhat.com">cjeanner@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 12/13/21 10:52, Chandan Kumar wrote:<br>
> Hello,<br>
> <br>
> The tripleo-ci team is working on drafting the plans for bootstrapping<br>
> tripleo stable/wallaby branch on CentOS Stream 9.<br>
> <br>
> During adding the support of CentOS Stream 9 for tripleo master, we have added<br>
> lots of patches for example:<br>
> * tripleo-common:<br>
> <a href="https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%2522%29+status:merged+project:openstack/tripleo-common" rel="noreferrer" target="_blank">https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%2522%29+status:merged+project:openstack/tripleo-common</a><br>
> * tripleo-heat-templates:<br>
> <a href="https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%2522%29+status:merged+project:openstack/tripleo-heat-templates" rel="noreferrer" target="_blank">https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%2522%29+status:merged+project:openstack/tripleo-heat-templates</a><br>
> * <a href="https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%2522%29+status:merged+project:openstack/tripleo-ansible" rel="noreferrer" target="_blank">https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%2522%29+status:merged+project:openstack/tripleo-ansible</a><br>
> <br>
> Backporting these patches in chains for stable/wallaby, will create<br>
> lots of merge conflicts (few of them are big changes) and might get<br>
> messy.<br>
> RDO wallaby DLRN builder bootstrap has also started.<br>
> <br>
> In order to avoid that, we are coming with following plan:<br>
> - Pick the major change and backport that one and add all the<br>
> remaining changes in that itself (not a clean backport):<br>
> <a href="https://review.opendev.org/c/openstack/tripleo-common/+/821511" rel="noreferrer" target="_blank">https://review.opendev.org/c/openstack/tripleo-common/+/821511</a><br>
> - Make sure these backported changes passed on CentOS-8 CI jobs<br>
> - Once the RDO CS9 wallaby packages are available, Start bootstrapping<br>
> the container and Image build job on CS9 via testproject.<br>
> <br>
> Let us know your thoughts around this.<br>
<br>
Hey Chandan,<br>
<br>
As discussed before: I'm all for this solution. There are multiple <br>
advantages, among them: less CI hassle, less conflicts, faster merges.<br></blockquote><div><br></div><div>+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.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Cheers,<br>
<br>
C.<br>
<br>
> <br>
> Thanks,<br>
> <br>
> Chandan Kumar<br>
> <br>
> <br>
<br>
-- <br>
Cédric Jeanneret (He/Him/His)<br>
Sr. Software Engineer - OpenStack Platform<br>
Deployment Framework TC<br>
Red Hat EMEA<br>
<a href="https://www.redhat.com/" rel="noreferrer" target="_blank">https://www.redhat.com/</a><br>
</blockquote></div></div>