Page MenuHomePhabricator

Quota increase request for project wlm-it-visual
Closed, ResolvedPublic

Assigned To
Authored By
Ferdi2005
May 31 2026, 9:51 AM
Referenced Files
F87993980: image.png
Jun 11 2026, 4:50 PM
F87993701: image.png
Jun 11 2026, 4:50 PM
F87993596: image.png
Jun 11 2026, 4:50 PM

Description

Quota increase requested for project wlm-it-visual. OpenStack Browser

ResourceCurrent limitIncreaseNew limitΔ%
vCPUs24+2448+100.0%
RAM (MiB)49152+3276881920+67.0%
Volume Storage (GB)130+20150+15.0%

Reason: We are currently serving 10+ countries in the WLM app and we are going to split the VM with backend api management and the VM for job management, thus we need more resources to accomodate the growing demand of countries to join our app. Furthermore, we'll use the remaining quota to set up a staging environment in order to test changes.

NOTE for clinic duty: Before fulfilling this request, ask a different Cloud admin to leave a +1 comment in this task. See Projects lifecycle: Requests.

Cookbook command:

cookbook wmcs.openstack.quota_increase --cluster-name eqiad1 --project wlm-it-visual --cores 24 --ram 32768 --gigabytes 20

Event Timeline

Hello!

I have a couple questions:

  • how much of the requested space will be freed up again after you finish the transition?
  • are your existing hosts really using all the provisioned RAM? (I know that CPU usage tends to be bursty but maybe you have an idea of that too.)
Volans triaged this task as Medium priority.Jun 11 2026, 4:42 PM

@Andrew current RAM usage for the two VMs

image.png (3,138×1,378 px, 253 KB)

image.png (3,144×1,362 px, 315 KB)

and CPU usage for the wlmitvisual01 instance (the other one is negligible, but might be because not yet fully setup):

image.png (3,138×1,378 px, 397 KB)

@Ferdi2005 is my understanding correct that some of the current workload of wlmitvisual01 will go into the new wlm-job host? Because if that's the case it doesn't seem you need all that additional resources, but I might be missing some context. In particular if the same pre-existing load will be split, CPU seems already largely unused and the RAM too seems to not require particular increases if part of the used RAM from the old host goes to the new job host.

I'd also take the opportunity to remind you that wlmitvisual01 instance is still a Debian Bullseye that will be EOL at the end of August, make sure to upgrade/migrate it soon to a more recent version ;)

Yes, the workload will be split in two machines, but the workload will likely increase given that we are going to support more and more countries in the following months. We also need some additional resources (double what's currently used) to set up the staging environment, so the resource usage will double. Most of the usage happens in september-october but the syncing work is always active. If you think that a minor quota is fine, we can try working with that and increase it in case of need. Thank you @Volans

Mentioned in SAL (#wikimedia-cloud-feed) [2026-06-15T17:19:58Z] <volans@cloudcumin1001> START - Cookbook wmcs.openstack.quota_increase by 24 cores, 20 gigabytes, 32768 ram (T427731)

Mentioned in SAL (#wikimedia-cloud-feed) [2026-06-15T17:20:06Z] <volans@cloudcumin1001> END (PASS) - Cookbook wmcs.openstack.quota_increase (exit_code=0) by 24 cores, 20 gigabytes, 32768 ram (T427731)

Volans claimed this task.

Limit increased. Just a few suggestions:

  1. Try to not create a full-size stating environment, it can surely have much less resources and still be a good staging environment.
  2. Once the new setup is complete and the new countries are added, re-evaluate the actual usage resources so to be able to free some if not needed.