OpenStack Lightspeed: Remove support for Venus

[umago]

Thic change removes the venus project from the list of OpenStack projects we build the upstream RAG from since the project is deprecated and RHOSO does not use nor ship it.

Summary by CodeRabbit

This PR updates the OpenShift CI configuration for building the OpenStack Lightspeed RAG content by removing the deprecated venus OpenStack project from the upstream projects list used for indexing.

What changes in practice

• The OS_PROJECTS list in ci-operator/config/openstack-lightspeed/rag-content/openstack-lightspeed-rag-content-main.yaml no longer includes venus.
• As a result, the RAG content builder/CI pipeline will stop pulling Venus documentation and will not include it in the generated RAG dataset.

Why it matters

• venus is deprecated and RHOSO (Red Hat OpenStack) does not use or ship it, so excluding it keeps the indexed content aligned with actively maintained, relevant OpenStack projects.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 73dd6e19-8672-4bc7-bda6-c3dd88bde36d

📥 Commits

Reviewing files that changed from the base of the PR and between 963bf72 and c289af4.

📒 Files selected for processing (1)

• ci-operator/config/openstack-lightspeed/rag-content/openstack-lightspeed-rag-content-main.yaml

✅ Files skipped from review due to trivial changes (1)

• ci-operator/config/openstack-lightspeed/rag-content/openstack-lightspeed-rag-content-main.yaml

---

Walkthrough

The venus entry is removed from the OS_PROJECTS whitespace-delimited list in the CI operator configuration file for openstack-lightspeed-rag-content-main, resulting in a one-line change.

Changes

OS_PROJECTS Configuration Update

Layer / File(s)	Summary
Remove venus from OS_PROJECTS ci-operator/config/openstack-lightspeed/rag-content/openstack-lightspeed-rag-content-main.yaml	Removes venus from the whitespace-delimited OS_PROJECTS list, leaving storlets vitrage zun at that position.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: removing Venus support from the OpenStack Lightspeed RAG configuration, which is the primary objective of this pull request.
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.
Stable And Deterministic Test Names	✅ Passed	PR only modifies a YAML configuration file, not Ginkgo test code; no test names are added or modified, making this check not applicable.
Test Structure And Quality	✅ Passed	PR modifies only a YAML configuration file (not test code). The Ginkgo test quality check is not applicable to YAML configuration changes.
Microshift Test Compatibility	✅ Passed	This PR modifies only a YAML configuration file (openstack-lightspeed-rag-content-main.yaml) and adds no Ginkgo e2e tests. The MicroShift compatibility check applies only to new e2e tests and is no...
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR only modifies YAML config (removing venus from OS_PROJECTS list). No new Ginkgo e2e tests are added, so SNO compatibility check is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	The PR modifies a CI/CD configuration file to remove a project entry from a build argument list. No deployment manifests, operator code, or scheduling constraints are introduced or modified.
Ote Binary Stdout Contract	✅ Passed	PR modifies only a YAML CI configuration file (no executable code, binaries, or main/test functions). OTE Binary Stdout Contract check is not applicable.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	No Ginkgo e2e tests are present in this PR. The change only modifies a YAML CI/CD configuration file to remove the venus project from the OS_PROJECTS list. The custom check is not applicable.
No-Weak-Crypto	✅ Passed	PR modifies only a YAML configuration file to remove a project name from a list. No cryptographic code, algorithms (MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB), or insecure comparisons are present.
Container-Privileges	✅ Passed	PR modifies only a CI-operator config file, removing 'venus' from OS_PROJECTS list. No privileged container settings (privileged, hostPID, hostNetwork, hostIPC, allowPrivilegeEscalation, SYS_ADMIN)...
No-Sensitive-Data-In-Logs	✅ Passed	The PR modifies only a YAML configuration file containing non-sensitive OpenStack project names. No logging code, passwords, tokens, API keys, PII, or sensitive data is present in the changes.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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 and usage tips.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: umago

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• ci-operator/config/openstack-lightspeed/rag-content/OWNERS [umago]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@umago: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-openstack-lightspeed-rag-content-main-images	openstack-lightspeed/rag-content	presubmit	Ci-operator config changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-ci]

@umago: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.