Switch to upstream blazar

[Alex-Welsh]

Switches from stackhpc/master in our Blazar fork to upstream 2025.1.
Our "master" fork was created around 2024.2, but was never updated since then.
It had a few customisations for coral credits which are now no longer in use, so we can go back to tracking upstream.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 51468deb-45ee-448c-a845-6d3a87ef695a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Walkthrough

Switches Blazar container builds from the StackHPC master fork to upstream 2025.1. Removes the obsolete blazar-base custom source and Coral Credits customisation. Adds 2025.1 image tags for Rocky 9, Rocky 10, and Ubuntu Noble.

Walkthrough

Blazar now uses upstream container images dated 20260730T151535 for Rocky 9, Rocky 10, and Ubuntu Noble. The custom StackHPC source entry was removed, and release notes document the change.

Changes

Blazar upstream images

Layer / File(s)	Summary
Configure Blazar image sources and tags etc/kayobe/kolla.yml, etc/kayobe/kolla-image-tags.yml, releasenotes/notes/...yaml	The custom blazar-base StackHPC source was removed. Image tags were added for Rocky 9, Rocky 10, and Ubuntu Noble. Release notes document the upstream source and Coral Credits changes.

Estimated code review effort: 1 (Trivial) | ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 2

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 77952196-b336-4081-adc8-724dd1da6906

📥 Commits

Reviewing files that changed from the base of the PR and between 2a59fbb and 4aed8e4.

📒 Files selected for processing (3)

• etc/kayobe/kolla-image-tags.yml
• etc/kayobe/kolla.yml
• releasenotes/notes/build-blazar-from-upstream-fd5fc48f9bd677e0.yaml

💤 Files with no reviewable changes (1)

• etc/kayobe/kolla.yml

📜 Review details

⏰ Context from checks skipped due to timeout. (6)

• GitHub Check: stackhpc/check
• GitHub Check: Tox docs with Python 3.12
• GitHub Check: Ansible 2.18 lint with Python 3.12
• GitHub Check: Tox pep8 with Python 3.12
• GitHub Check: Tox releasenotes with Python 3.12
• GitHub Check: Ansible 2.17 lint with Python 3.10

🔇 Additional comments (1)

etc/kayobe/kolla-image-tags.yml (1)

10-13: 🗄️ Data Integrity & Integration

Confirm the three Blazar image tags before merge.

The registry requires authentication. Confirm that each tag exists in stackhpc-dev for blazar-api and blazar-manager, and that each image contains the intended upstream Blazar source.