Opened 6 weeks ago

Last modified 5 weeks ago

#32730 new defect

Status of dip.torproject.org and migration from ansible to the omnibus package

Reported by: hiro Owned by: tor-gitadm
Priority: Medium Milestone:
Component: Internal Services/Service - git Version:
Severity: Normal Keywords: gitlab
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by hiro)

Our gitlab instance has been having a weird issue for quite a while now where merge requests throw a 503 error (https://trac.torproject.org/projects/tor/ticket/32197).

There is consensus between the gitlab admins and the sysadmin team to move from the ansible deployment to a omnibus package installation.

Steps required to do this are the following:

[ ] - Create a new machine like gitlab-01 with the omnibus package installed
[ ] - Migrate data from gitlab-01 to the new machine
[ ] - Decommission gitlab-01

Child Tickets

TicketStatusOwnerSummaryComponent
#32197newtor-gitadmGitlab throwing 503 when creating a Merge Request from a forked repositoryInternal Services/Service - git
#32949assignedhiroMigrate dip from gitlab-01 to gitlab-02Internal Services/Service - git

Change History (3)

comment:1 Changed 6 weeks ago by hiro

Description: modified (diff)

comment:2 Changed 6 weeks ago by hiro

Anarcat and I have looked at loads for gitlab-01 and tried to estimate what might be required by dip once we are in production.

At the moment dip is using around 6GB (?) allocated and about 4GB is already taken.
We see 7-8% I/O wait is pretty big and 20% CPU usage. We can estimate that it will need approx 8GB while we are still in testing and maybe even 12/16GB once we go in production.

Moving forward because gitlab will be replacing multiple service our final setup might be different that just running "a trac replacement". In fact we are replacing multiple services with just gitlab (trac, gitweb, git-rw ... ).

For the time being we believe we might place this VM into our ganeti cluster, but moving forward we might consider doing a better estimation of load needed as we might have to run different machines for different gitlab services.

comment:3 Changed 5 weeks ago by anarcat

Keywords: gitlab added
Note: See TracTickets for help on using tickets.