WIP: kolla build repo config

[Alex-Welsh]

Creating this PR for discussion only right now.

The way kolla configures package repos has changed a lot in the latest release and I need to work out the best way to do it. That might require some changes to kayobe or kolla iself to expose the right variables and make this easier than it has been in previous releases.

[gemini-code-assist]

Code Review

This pull request removes support for Rocky 9 and introduces repository configurations and definitions for Rocky 10 and Ubuntu Noble across several files, including kolla-build.conf, repos.yaml, and stackhpc.yml. Feedback on these changes includes updating an outdated comment in kolla-build.conf that still references Rocky 9, removing repository definitions for CentOS Stream 10 and EL10 since they are not yet officially supported, and converting a multi-line gpgkey string in repos.yaml to a single-line format to avoid potential parsing errors.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[Alex-Welsh]

So there's basically three parts to this:

1. Third party repos in repos.yaml - These are the easy ones, I think they should template out fine. It is basically a copy of the repos.yaml upstream, but with our repo URLs thrown in there.
2. Base Rocky Repos - The docs say you can include your own *.repo files using rpm_setup_config but also say that the repo file must be configured in kolla/docker/base (or as a url). Looking at how kolla does this, I don't think the jinja templating in the repo file I added will work, so probably needs a patch to Kayobe to fix. I don't see another way to override base repos.
3. Base Ubuntu Repos - Same as Rocky basically. Docs say you can override them. It doesn't say it has to be anywhere specific, but I don't think the jinja template will work. Probably needs another Kayobe patch. Again, don't see another way to override base repos.

@mnasiadka am I correct on points 2 and 3? Need check I haven't missed an obvious way to do this

[mnasiadka]

So there's basically three parts to this:

1. Third party repos in repos.yaml - These are the easy ones, I think they should template out fine. It is basically a copy of the repos.yaml upstream, but with our repo URLs thrown in there.
2. Base Rocky Repos - The docs say you can include your own *.repo files using rpm_setup_config but also say that the repo file must be configured in kolla/docker/base (or as a url). Looking at how kolla does this, I don't think the jinja templating in the repo file I added will work, so probably needs a patch to Kayobe to fix. I don't see another way to override base repos.
3. Base Ubuntu Repos - Same as Rocky basically. Docs say you can override them. It doesn't say it has to be anywhere specific, but I don't think the jinja template will work. Probably needs another Kayobe patch. Again, don't see another way to override base repos.

@mnasiadka am I correct on points 2 and 3? Need check I haven't missed an obvious way to do this

Basically 1 is correct, 2 and 3 can stay as a template override - we didn't get to support overriding this in repos.yaml (but that's somewhere deep on my list)

[Alex-Welsh]

So there's basically three parts to this:

1. Third party repos in repos.yaml - These are the easy ones, I think they should template out fine. It is basically a copy of the repos.yaml upstream, but with our repo URLs thrown in there.
2. Base Rocky Repos - The docs say you can include your own *.repo files using rpm_setup_config but also say that the repo file must be configured in kolla/docker/base (or as a url). Looking at how kolla does this, I don't think the jinja templating in the repo file I added will work, so probably needs a patch to Kayobe to fix. I don't see another way to override base repos.
3. Base Ubuntu Repos - Same as Rocky basically. Docs say you can override them. It doesn't say it has to be anywhere specific, but I don't think the jinja template will work. Probably needs another Kayobe patch. Again, don't see another way to override base repos.

@mnasiadka am I correct on points 2 and 3? Need check I haven't missed an obvious way to do this

Basically 1 is correct, 2 and 3 can stay as a template override - we didn't get to support overriding this in repos.yaml (but that's somewhere deep on my list)

I'd really like to kill the grim sed templating we have right now. Is there a WIP patch I can pick up?

[mnasiadka]

So there's basically three parts to this:

1. Third party repos in repos.yaml - These are the easy ones, I think they should template out fine. It is basically a copy of the repos.yaml upstream, but with our repo URLs thrown in there.
2. Base Rocky Repos - The docs say you can include your own *.repo files using rpm_setup_config but also say that the repo file must be configured in kolla/docker/base (or as a url). Looking at how kolla does this, I don't think the jinja templating in the repo file I added will work, so probably needs a patch to Kayobe to fix. I don't see another way to override base repos.
3. Base Ubuntu Repos - Same as Rocky basically. Docs say you can override them. It doesn't say it has to be anywhere specific, but I don't think the jinja template will work. Probably needs another Kayobe patch. Again, don't see another way to override base repos.

@mnasiadka am I correct on points 2 and 3? Need check I haven't missed an obvious way to do this

Basically 1 is correct, 2 and 3 can stay as a template override - we didn't get to support overriding this in repos.yaml (but that's somewhere deep on my list)

I'd really like to kill the grim sed templating we have right now. Is there a WIP patch I can pick up?

I did a refreshed version of the patches in this stack: https://review.opendev.org/c/openstack/kolla/+/993407