Page MenuHomePhabricator

Grant zuul project access to `fast-iops` volume type and `4xiops` instance flavor
Closed, ResolvedPublic

Description

Project Name: zuul
Type of quota increase requested: volume type, instance flavor
Amount to increase:

  • fast-iops volume type
  • g4.cores8.ram32.disk20.4xiops instance flavor

Reason: Many CI workloads are disk I/O bound. We need to be sure our Magnum cluster handle perform similarly to the existing integration project instances before migrating. We hope to follow the same path as T406271 enabled.

Details

Related Changes in GitLab:
TitleReferenceAuthorSource BranchDest Branch
flavors: add zuul to g4.cores8.ram32.disk20.4xiopsrepos/cloud/cloud-vps/tofu-infra!279volansT409365main
Customize query in GitLab

Event Timeline

Volans triaged this task as Medium priority.Nov 6 2025, 10:37 AM
Volans moved this task from Inbox to Discussion needed on the Cloud-VPS (Quota-requests) board.

If I'm not mistaken the above patch should gran the usage of the requested instance type. I'm not sure if there is a separate setting for the fast-iops bit or it's included in that configuration.

not sure if there is a separate setting for the fast-iops bit

My understanding is that volume types are only relevant for additional volumes (created with "Volumes" in Horizon, or with the volumes API), whereas the attributes of the root volumes of instances (including the IOPS limits) are controlled by the flavor. @Andrew is that correct?

not sure if there is a separate setting for the fast-iops bit

My understanding is that volume types are only relevant for additional volumes (created with "Volumes" in Horizon, or with the volumes API), whereas the attributes of the root volumes of instances (including the IOPS limits) are controlled by the flavor. @Andrew is that correct?

Correct. Flavor determines the performance limits for root volumes and volume type controls the limits for cinder volumes.

@bd808 do you also need high-iops Cinder volumes, or the root volumes are enough?

@bd808 do you also need high-iops Cinder volumes, or the root volumes are enough?

Yes, this project will need high iops volumes. The Magnum k8s setup uses volumes for storage on all nodes which probably makes the high iops volumes more important than the instance flavors.

Mentioned in SAL (#wikimedia-cloud-feed) [2025-11-14T15:09:32Z] <fnegri@cloudcumin1001> START - Cookbook wmcs.openstack.tofu running tofu plan for main branch (T409365)

Mentioned in SAL (#wikimedia-cloud-feed) [2025-11-14T15:10:58Z] <fnegri@cloudcumin1001> END (FAIL) - Cookbook wmcs.openstack.tofu (exit_code=99) running tofu plan for main branch (T409365)

Mentioned in SAL (#wikimedia-cloud-feed) [2025-11-14T15:12:48Z] <fnegri@cloudcumin1001> END (PASS) - Cookbook wmcs.openstack.tofu (exit_code=0) running tofu plan for https://gitlab.wikimedia.org/repos/cloud/cloud-vps/tofu-infra/-/merge_requests/279 (T409365)

Mentioned in SAL (#wikimedia-cloud-feed) [2025-11-14T15:13:53Z] <fnegri@cloudcumin1001> END (PASS) - Cookbook wmcs.openstack.tofu (exit_code=0) running tofu plan for https://gitlab.wikimedia.org/repos/cloud/cloud-vps/tofu-infra/-/merge_requests/279 (T409365)

Mentioned in SAL (#wikimedia-cloud) [2025-11-14T15:53:30Z] <dhinus> allow access to cinder volume type "high-iops" T409365

Mentioned in SAL (#wikimedia-cloud-feed) [2025-11-17T10:25:13Z] <fnegri@cloudcumin1001> START - Cookbook wmcs.openstack.tofu running tofu plan for main branch (T409365)

Mentioned in SAL (#wikimedia-cloud-feed) [2025-11-17T10:26:38Z] <fnegri@cloudcumin1001> END (FAIL) - Cookbook wmcs.openstack.tofu (exit_code=99) running tofu plan for main branch (T409365)

Mentioned in SAL (#wikimedia-cloud-feed) [2025-11-17T10:27:42Z] <fnegri@cloudcumin1001> START - Cookbook wmcs.openstack.tofu running tofu plan+apply for main branch (T409365)

  • high-iops volume type
  • g4.cores8.ram32.disk20.4xiops instance flavor

Mentioned in SAL (#wikimedia-cloud-feed) [2025-11-17T10:30:37Z] <fnegri@cloudcumin1001> END (FAIL) - Cookbook wmcs.openstack.tofu (exit_code=99) running tofu plan+apply for main branch (T409365)

END (FAIL) - Cookbook wmcs.openstack.tofu (exit_code=99)

This has no impact on this task, the change was applied successfully in eqiad1. The error is tracked in T410265: [tofu-infra] "tofu plan" failing in codfw.