Skip to content

Increase dal10 PowerVS quota slices from 1 to 4#79037

Open
Neha-dot-Yadav wants to merge 1 commit intoopenshift:mainfrom
Neha-dot-Yadav:powervs-increase-dal10-slice
Open

Increase dal10 PowerVS quota slices from 1 to 4#79037
Neha-dot-Yadav wants to merge 1 commit intoopenshift:mainfrom
Neha-dot-Yadav:powervs-increase-dal10-slice

Conversation

@Neha-dot-Yadav
Copy link
Copy Markdown
Contributor

@Neha-dot-Yadav Neha-dot-Yadav commented May 8, 2026

This PR increases the dal10 PowerVS lease capacity from 1 to 4 quota slices to support more parallel CI jobs.

Summary

This PR increases the OpenShift CI infrastructure's PowerVS quota capacity in the DAL10 region from 1 to 4 parallel quota slices, enabling more concurrent CI jobs to run on the PowerVS platform.

Changes

Infrastructure Impact: The change enables the Prow CI system to provision up to 4 simultaneous PowerVS instances in the DAL10 region instead of the previous single instance. This directly increases parallelization capacity for CI jobs that require PowerVS infrastructure.

Modified Components:

  1. Boskos resource pool configuration (_boskos.yaml): The powervs-3-quota-slice resource now defines 4 named quota slices (dal10-powervs-3-quota-slice-0 through -3) instead of a single dal10 entry, allowing the Prow scheduler to allocate up to 4 independent quota leases.

  2. Boskos generator script (generate-boskos.py): Updated to programmatically generate the 4 quota-slice entries, ensuring consistency between the generated and source configurations.

  3. PowerVS IPI deployment script (ipi-conf-powervs-commands.sh): Extended to recognize and properly route all 4 new DAL10 quota-slice identifiers to their respective PowerVS service instance credentials and regional settings (PowerVS region: dal, zone: dal10, VPC region: us-south).

This change maintains backward compatibility while expanding the infrastructure's capacity to run more parallel CI workflows in the PowerVS environment.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 8, 2026

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: 636fbb67-cfe3-4aec-9403-15ef64cd1838

📥 Commits

Reviewing files that changed from the base of the PR and between 88e6273 and 95cdb9c.

📒 Files selected for processing (3)
  • ci-operator/step-registry/ipi/conf/powervs/ipi-conf-powervs-commands.sh
  • core-services/prow/02_config/_boskos.yaml
  • core-services/prow/02_config/generate-boskos.py

Walkthrough

PowerVS deployment infrastructure is extended to support four DAL10 quota slice variants. The Boskos configuration now defines four slice-specific resources, the Python generator creates their names, and the deployment script handles their slice-specific prefixes and service instance mappings.

Changes

PowerVS DAL10 Quota Slices Extension

Layer / File(s) Summary
Generator Logic
core-services/prow/02_config/generate-boskos.py
Generator initializes powervs-3-quota-slice as empty and populates it with a loop creating four dal10-powervs-3-quota-slice-{0..3} entries.
Configuration Definition
core-services/prow/02_config/_boskos.yaml
powervs-3-quota-slice resource names field replaces single dal10 with four slice-qualified names: dal10-powervs-3-quota-slice-0, -1, -2, -3.
Deployment Script Integration
ci-operator/step-registry/ipi/conf/powervs/ipi-conf-powervs-commands.sh
Script adds handling for four new LEASED_RESOURCE slice values, deriving CLUSTER_NAME with slice-specific prefixes and mapping each to its corresponding POWERVS_SERVICE_INSTANCE_ID_DAL10-{slice} secret and region settings.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Increase dal10 PowerVS quota slices from 1 to 4' accurately reflects the main change across all modified files: the PowerVS quota slice configuration is expanded from a single dal10 slice to four slice-qualified identifiers.
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 contains no Ginkgo test definitions. Changes are infrastructure configuration only - PowerVS deployment script, YAML, and Boskos generator. Check not applicable.
Test Structure And Quality ✅ Passed No Ginkgo test files present in this PR. Modifies shell scripts, YAML config, and Python scripts for PowerVS quota configuration. Check not applicable.
Microshift Test Compatibility ✅ Passed No Ginkgo e2e tests were added. Changes are infrastructure/configuration only (shell, YAML, Python scripts for PowerVS quota slices). Check not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR contains no new Ginkgo e2e tests. Changes are limited to CI infrastructure/configuration files (shell script, YAML, Python). SNO compatibility check is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed No deployment manifests or scheduling constraints found. Changes are resource capacity management for PowerVS quota slices with no pod affinity, topology spread, or node selection constraints.
Ote Binary Stdout Contract ✅ Passed Check not applicable: PR modifies only shell script, YAML config, and Python generator - no OTE binaries or Go test code present.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This PR contains no Ginkgo e2e tests. Changes are to infrastructure files only: PowerVS deployment script, Boskos config YAML, and Python generator. The check applies only to new Ginkgo e2e tests.

✏️ 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

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

@openshift-ci openshift-ci Bot requested review from prb112 and smg247 May 8, 2026 09:51
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 8, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Neha-dot-Yadav
Once this PR has been reviewed and has the lgtm label, please assign tvardema, wking for approval. For more information see the Code Review Process.

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

Details Needs approval from an approver in each of these files:

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

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 8, 2026

@Neha-dot-Yadav: 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.

@Neha-dot-Yadav
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-multiarch-main-nightly-4.22-ocp-e2e-ovn-powervs-capi-multi-p-p

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@Neha-dot-Yadav: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant