Page MenuHomePhabricator

Request increased quota for devtools Cloud VPS project
Closed, ResolvedPublic

Description

Project Name: devtools

Type of quota increase requested: 4 more VCPUS (16 -> 20), 8GB more RAM (32 -> 40), floating IPs (1 -> 2)

Reason: gitlab is being introduced and needs a staging/testing setup. There is an existing gitlab-test project with an existing instance that we will completely delete in return. So in the grand scheme of things we are just moving resources around. We think it makes sense to have the gitlab instance in the same exiting project for gerrit and phabricator. The previous setup was used by contractors and used ansible. We are now using puppet and are replacing the old setup. This is T297411.

We want one permanent instance gitlab-stage-1001 and additionally we want to be able to spin up temp. instances that are used for one thing and then removed again. We are asking for 3 more instances just so that users don't conflict with each other but we are not planning to permanently run 4 instances.

And then the reason this is maxed out currently is also that we also have 2 instances related to doc.wikimedia.org, doc (strech) and doc1002 (buster) in there. Those were created quite some time ago by myself and @hashar for T247653. But this project is currently stalled on the releng side. I am not sure whether we can/should delete those, probably not until that is done but when they were originally created we did not expect them to become permanent.

doc is also releng related but not sure it's a "devtool" so yea.. should not block gitlab but the easiest would be if you just give us the quota now to unblock us.

Hope this makes some sense, cheers and thanks!

Event Timeline

oh yea, one more reason is also that we will want to test whether gitlab-runner (as opposed to gitlab-server) will work on bullseye for T297659. So multiple things here at once.

You can see quota vs usage at https://openstack-browser.toolforge.org/project/devtools and also on the "Overview" tab for your project in Horizon. The project is currently maxed on RAM and CPU with one instance available. To make a meaningful quota bump you need to be more specific about the cumulative CPU and RAM needed for "one permanent instance gitlab-stage-1001 and additionally we want to be able to spin up temp. instances that are used for one thing and then removed again".

OK, thanks bd808! Will do and come back to this.

Dzahn changed the task status from Open to In Progress.Jan 19 2022, 7:23 PM
Dzahn moved this task from Inbox to Discussion needed on the Cloud-VPS (Quota-requests) board.

Mentioned in SAL (#wikimedia-cloud) [2022-01-21T21:57:23Z] <mutante> - deleted instances "doc" and "doc1002" to make room for gitlab instance T299561 - T297411

I deleted the 2 doc* instances after checking in with hashar. We agreed they can be recreated (elsewhere) if/when needed.

Now we have room for one gitlab-prod instance with 2 CPUs and 4GB RAM. So that is unblocked but we'll be full again right away.

For 2 more flexible/temp instances would like to change the request to:

instance_count: can stay 8 as it is

vCPUS: asking to raise from 16 to 20

RAM: asking to raise from 32 to 40

Dzahn changed the task status from In Progress to Open.Jan 21 2022, 10:09 PM
Dzahn removed Dzahn as the assignee of this task.
Dzahn updated the task description. (Show Details)
Dzahn moved this task from Discussion needed to Inbox on the Cloud-VPS (Quota-requests) board.
Dzahn triaged this task as Medium priority.Jan 21 2022, 10:22 PM

We also need one additional floating IP in the devtools project. So the total request would be:

instance_count: can stay 8 as it is

vCPUS: asking to raise from 16 to 20

RAM: asking to raise from 32 to 40

Floating IP: asking to raise from 1 to 2

Mentioned in SAL (#wikimedia-cloud) [2022-01-26T15:56:40Z] <arturo> bump quota, RAM from 32 to 40, cores from 16 to 20 (T299561)

aborrero subscribed.

hey, could you please elaborate a bit more on why you need the additional floating IP?

hey, could you please elaborate a bit more on why you need the additional floating IP?

Hi,

Production GitLab uses two interfaces (mostly to separate the management SSH daemon from the application SSH daemon). We would like to have a production-like test environment in WMCS an recreate this setup as close as possible. So we need a public address where we can reach the machine over SSH and https. If there is some other way instead of a floating IP for a second addresses please let me know.

gitlab is copying the setup of gerrit and phabricator, which also have both a server and service IP (gerrit.wm.org / gerrit1001.wm.org (phabricator.wm.org / git-ssh.wm.org) and as Jelto says to have a production-like test environment we also want to copy that in cloud (and we did previously, that's why we already had 1 floating IP here, technically we would need one for phab as well, but we'll shut down git-ssh.wm.org)

Mentioned in SAL (#wikimedia-cloud) [2022-01-26T17:26:14Z] <arturo> bump quota, floating IP from 1 to 2 (T299561)

aborrero claimed this task.
aborrero moved this task from Discussion needed to Approved on the Cloud-VPS (Quota-requests) board.