Ericsson Architectural and Design related inquiry related to Prestudy business case build out.
GitLab team, please find below an inquiry from our team at Ericsson related to GitLab architecture and scale. Can you please provide a response back to this thread so that we can engage Ericsson via this issue to address their questions?
Thank you! AJ
Hello Adam,
To be able to proceed further with our GitLab pre-study, we have generated a list of our GitLab architecture questions and we did categorize them into 4 sections.
Can you go through those questions with GitLab architects and provide us with some answers.
Please, let us know if any meetings / demos are needed.
Regards, Joseph
1- Redundancy and High Availability:
-
What is the redundancy applied for DB ? Git repos ? frontend ?
-
Is there a multimaster and is it active/active or active/passive ? Geographical redundancy ?
-
Is it possible to perform transparent upgrades for major GitLab versions ?
2- Scalability:
-
Is there replication mechanism across hubs ? is there a READ only slave concept ?
-
Does GitLab support horizontal scaling (Cloud friendly)? Scaling up instance by adding more hardware ?
-
How many transactions per day a GitLab cluster can serve ?
3- Integration with Ericsson IT:
-
Can we use LDAP for authentication and provision users upon first login ? How these users are disabled upon leaving LDAP/company ?
-
What are the hardware requirements for Hosts (CPUs, RAM, SSD?), Storage (required NFS version ), Network (Access to NFS 10Gb required ?), OS (required packages and privileges e.g. root , OS limits e.g. max user processes, ..) ?
-
What are the software components requirements for GitLab installation / setup ? Keepalived/haproxy/apache ? go/ruby runtime libs/packages ?
-
Can we use DB hotel [DB Service provided by Ericsson IT] ? Or we have to use local Postgresql ?
-
Existing integration with external Issue Tracking Systems like RTC, JIRA , ?
-
Is there any built-in service level agreement measurement tool (server availability, response time, basic usage workflow time, ..) ?
4- GitLab Internals:
-
How Git Garbage Collection is working in GitLab ? Frequency ? What triggers GC for a repository ? Daily cron activity ?
-
How admin accounts work in GitLab ? separate admin account for all admins beside their accounts ? Or the same account can be used as admins ?
-
How efficient is the import/export project functionality to move projects from existing GitLab instances with different GitLab versions to new instance ?
-
Is there any Admins and monitoring dashboard in GitLab ?
-
Is there any throttling capability for aggressive usage patterns ?
Ericsson contacts:
-
Joseph Habib A joseph.a.habib@ericsson.com
-
David Bainbridge david.bainbridge@ericsson.com,
-
Bassem Rabil Guendy bassem.rabil.guendy@ericsson.com