Page MenuHomePhabricator

Close "gerrit" Cloud VPS project
Open, Needs TriagePublicAug 13 2019

Description

The gerrit project (wikitech, openstack-admin) seems to have been created years ago for Gerrit testing. Today Gerrit testing is primarily done in the git Cloud VPS project instead.

I propose that the currently empty gerrit project be closed and any members of the gerrit project who wish to continue to help with Gerrit testing join the git project.

Gerrit & Git project admins:

Userin Gerrit projectin Git project
@mmodell[x][x]
@akosiaris[x][]
@Catrope[x][]
@Dzahn[][x]
@Gilles[x][]
@hashar[x][x]
@Paladox[x][x]
@QChris[x][]
@thcipriani[x][x]
@Krenair[][x]
@Danny_B[][x]
@Luke081515[][x]
@Mc1arke[][x]
@valhallasw[][x]
@Reception123[][x]
@Reedy[][x]
@Zppix[][x]
@chasemp[][x]

Let's set an arbitrary date of 2019-08-12 for any of the folks listed as project admins to state why this is a horrible idea.

Details

Due Date
Aug 13 2019, 12:00 AM

Event Timeline

bd808 created this task.Aug 2 2019, 9:20 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 2 2019, 9:20 PM
bd808 set Due Date to Aug 12 2019, 12:00 AM.Aug 2 2019, 9:20 PM
Restricted Application changed the subtype of this task from "Task" to "Deadline". · View Herald TranscriptAug 2 2019, 9:20 PM
bd808 changed Due Date from Aug 12 2019, 12:00 AM to Aug 13 2019, 12:00 AM.Aug 2 2019, 9:21 PM
bd808 moved this task from Inbox to Discussion needed on the Cloud-VPS (Project-requests) board.
Dzahn added a comment.Aug 2 2019, 11:18 PM

Paladox used the git project only because of a quota limitation that meant he wasn't allowed to start another instance in the gerrit project.

I would suggest the other way around, use gerrit for gerrit as that's what it has been created for, check again how many instances are needed and how the quota settings are.

The "git" project was created for gitblit and testing rewrites afaict, and that doesn't exist anymore. So it would make more sense to me to get rid of that one.

Unless this means a lot of work.. but hopefully it doesn't because we just have to apply puppet roles and not too many live hacks?

It would be a lot of work to move from the git project (as i have a ci setup on gerrit-test) i also have jenkins-slave.

bd808 added a comment.Aug 2 2019, 11:37 PM

Paladox used the git project only because of a quota limitation that meant he wasn't allowed to start another instance in the gerrit project.

Interesting. Did we (cloud-services-team) block a quota increase request for that? Or was this a way to "borrow" quota from somewhere instead of asking?

I would suggest the other way around, use gerrit for gerrit as that's what it has been created for, check again how many instances are needed and how the quota settings are.
The "git" project was created for gitblit and testing rewrites afaict, and that doesn't exist anymore. So it would make more sense to me to get rid of that one.
Unless this means a lot of work.. but hopefully it doesn't because we just have to apply puppet roles and not too many live hacks?

I mostly would like to see unused projects gone and I don't care which one. :) Unused projects lead to the kind of confusion seen here where adminX in projectY spins up an instance unrelated to the project's goal "just to test something" and then it never goes away and nobody remembers why it is there and who 'owns' it. This quite often eventually leads to someone from the WMCS team spending a bunch of time to track down an owner when the instance gets busted somehow or its OS version needs to be replaced. If we were a for-profit hosting company we would just keep sending the bills and letting things ride until the checks stopped coming back, but in our gratis environment we need to purge the running but underutilized instances from the servers as often as we can to maintain capacity for active projects.

Dzahn added a comment.Aug 2 2019, 11:37 PM

Alright, i understand. While i still think it's a bit wrong to use the name "git" for something unrelated and it will make it hard to find. (searching for gerrit will show nothing); i also don't want to make you have to recreate CI from scratch. After all it's just a name.

But most important is we don't run into the quota issue again. If it's still close to "full" and one of the former gerrit-project users wants to test something and immediately runs into that after moving that would be unfortunate.

Dzahn added a comment.Aug 2 2019, 11:42 PM

I removed myself from the Gerrit project.

Dzahn updated the task description. (Show Details)Aug 2 2019, 11:43 PM
Paladox added a comment.EditedAug 2 2019, 11:55 PM

@bd808 it was a long while before i used this project (only using it earlier this year to test gerrit multi master setup), (i think the original intention was to move gerrit testing to that project (but didn't pan out as i never bothered to move gerrit-test3 to the gerrit project). The intention was never to go around quota restrictions (which i plan to ask for an increase if needed when i start re testing the multi master setup).

Though the project was created long before (so i'm not 100% sure if the original reason i gave above is correct).

+1 to what @Paladox stated, we do not need the gerrit project anymore and the dev environment is under the git project :-]

The arbitrary due date came and went with the main opposing feedback being the note from @Dzahn in T229703#5389161 that "git" does not mean the same thing as "gerrit" to him. He and others seem to agree that rebuilding the current setup into the gerrit project is unnecessary toil.