Skip to content

Switch to upstream blazar - #2558

Open
Alex-Welsh wants to merge 2 commits into
stackhpc/2026.1from
blazar-upstream
Open

Switch to upstream blazar#2558
Alex-Welsh wants to merge 2 commits into
stackhpc/2026.1from
blazar-upstream

Conversation

@Alex-Welsh

Copy link
Copy Markdown
Member

Switches to upstream blazar instead of our stackhpc fork.

Also bumps our kolla/kolla-ansible pins and switches back to using tags. This should let them auto-update with our weekly syncs again

@Alex-Welsh
Alex-Welsh requested a review from a team as a code owner August 27, 2026 10:44
@github-actions github-actions Bot added the waiting-review PR is waiting for a review label Aug 27, 2026
@coderabbitai

coderabbitai Bot commented Aug 27, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 8a964a57-98e8-4e9f-89bd-749c3e411280

📥 Commits

Reviewing files that changed from the base of the PR and between 7fa8c88 and 4a828cc.

📒 Files selected for processing (3)
  • etc/kayobe/kolla-image-tags.yml
  • etc/kayobe/kolla.yml
  • etc/kayobe/stackhpc.yml
💤 Files with no reviewable changes (1)
  • etc/kayobe/kolla.yml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details
⏰ Context from checks skipped due to timeout. (3)
  • GitHub Check: Ansible 2.19 lint with Python 3.12
  • GitHub Check: Ansible 2.20 lint with Python 3.12
  • GitHub Check: stackhpc/check
🔇 Additional comments (2)
etc/kayobe/stackhpc.yml (1)

180-184: LGTM!

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

11-12: LGTM!


📝 Walkthrough

Switches from the StackHPC Blazar fork to upstream Blazar. Removes the fork source definition and adds the blazar image tag. Restores tag-based Kolla and Kolla-Ansible references to support automatic weekly synchronisations.

Walkthrough

The change pins Kolla and Kolla-Ansible to StackHPC release tags, removes the Blazar source override, and adds a Rocky 10 Blazar image tag.

Changes

Kolla configuration updates

Layer / File(s) Summary
Pin Kolla source versions
etc/kayobe/stackhpc.yml, etc/kayobe/kolla.yml
Kolla and Kolla-Ansible now use pinned StackHPC release tags. The temporary Blazar source override and related FIXME comments are removed.
Add Blazar image tag
etc/kayobe/kolla-image-tags.yml
The blazar service maps rocky-10 to image tag 2026.1-rocky-10-20260826T141623.

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

Merge Risk: ⚪ Minimal · up to 4a828

The PR switches to upstream Blazar and updates Kolla pins and image tagging behavior in localized configuration; no actionable merge-blocking risk remains after normal checks and review.

🚥 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. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)


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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

waiting-review PR is waiting for a review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant