Page MenuHomePhabricator

Request increased quota for gitlab-test Cloud VPS project: Extra floating IP, capacity for extra g3.cores4.ram8.disk20
Closed, ResolvedPublic

Description

Project Name: gitlab-test

Type of quota increase requested:

  • 1 additional floating IP
  • Enough capacity for an additional g3.cores4.ram8.disk20 instance

Reason: Contractors for the GitLab project need somewhere to test config management for installing GitLab omnibus packages. I've temporarily re-allocated capacity we were using for a job runner for that purpose, but we'd like to be able to retain the existing stable test instance as well as spinning up a job runner.

I imagine we can drop this down to 2 instances and 1 IP eventually, but the extra capacity will be helpful while we figure out installation process and configuration.

Thanks! Please let me know here if there are any questions, or I'm available on IRC.

Event Timeline

brennen renamed this task from Request increased quota for gitlab-test Cloud VPS project to Request increased quota for gitlab-test Cloud VPS project: Extra floating IP, capacity for extra g3.cores4.ram8.disk20.Mar 22 2021, 11:57 PM
brennen added a project: User-brennen.
brennen moved this task from Backlog to Needs/Waiting Review on the User-brennen board.

Could you please explain a bit what is the floating IP for? Other than that, LGTM.

Could you please explain a bit what is the floating IP for? Other than that, LGTM.

I'd like to offer the Speed & Function folks a target for Ansible where they can install GitLab, test it externally, etc. (Separate from the existing stable gitlab-test.)

(We can repurpose the existing one, if need be. Just a bit more convenient not to have to shuffle it between a couple of use cases.)

But ansible is ssh-based. Can't they use the existing SSH workflows? (i.e, shared bastion hosts for SSH).

We don't have problems with the floating IP quota, just making sure other options have been considered first.

I have played a little with ansible and cloud VPS too, the only option I configured (not sure if it was needed though, it has been some time) was, in the ansible.cfg file:

[ssh_connection]
ssh_args = -o ControlMaster=auto -o ControlPersist=30m

And have a properly configured ~/.ssh/config (something that allows ssh to connect without special options to the VMs).

After some discussion, I think we can probably get by with just the existing floating IP. The rationale in my mind was to be able to test a newly configured GitLab instance externally, potentially from third party tools like k6.io. But! It's only a few clicks in horizon to re-point things, and shouldn't be too much of a roadblock. We can revisit later if it does seem necessary.

Thanks!

Mentioned in SAL (#wikimedia-cloud) [2021-03-26T10:02:22Z] <dcaro> Increased quota +1 instance, +4 cores, +8G ram (T278197)

Added the quota, let me know if you need more or you end up needed that extra floating ip :)
I'll close the task, cheers!