You are browsing a read-only backup copy of Wikitech. The live site can be found at wikitech.wikimedia.org

GitLab: Difference between revisions

From Wikitech-static
Jump to navigation Jump to search
imported>Majavah
m (Majavah moved page Gitlab to GitLab)
 
imported>Brennen Bearnes
(link out to mw:GitLab for how to get a repo.)
(15 intermediate revisions by 6 users not shown)
Line 1: Line 1:
Stand-in page for the SRE GitLab documentation expected in FY 21/22
{{Sidebar
| style = background: white; padding:10px; padding-{{dir|{{pagelang}}|left|right}}:13px; margin:{{dir|{{pagelang}}|5px 12px 5px 0|5px 0 5px 12px}}; width: 350px;
| name = GitLab
| title = GitLab
| image = [[File:Gitlab-logo.svg.svg|center|250px]]
| headingstyle = font-size: 130%; padding: .5em;
| contentstyle = text-align: {{dir|{{pagelang}}|right|left}}; font-size: 14px; padding: .5em; line-height: 1.5;
| abovestyle = text-align: {{dir|{{pagelang}}|right|left}};
| content1 =
{{Special:PrefixIndex/{{FULLPAGENAME}}/ |hideredirects=1 |stripprefix=1}}
* External resources:
** [[mw:GitLab]] - User documentation
** [https://gitlab.wikimedia.org/ Production GitLab]
** [https://docs.gitlab.com Upstream GitLab docs]
** [https://phabricator.wikimedia.org/project/view/5057/ GitLab in Phabricator]
}}
 
This page contains SRE related topics for GitLab. For GitLab application-specific information, user documentation, and policy, please see [[mw:GitLab]] on mediawiki.org.
 
GitLab is reachable at https://gitlab.wikimedia.org/. We run multiple instances of GitLab:
 
* gitlab1001 runs production GitLab serving https://gitlab.wikimedia.org/
* gitlab2001 runs a passive GitLab [[GitLab/Replica|replica]] serving https://gitlab-replica.wikimedia.org/
* gitlab-prod-1001.devtools.eqiad1.wikimedia.cloud runs a production-like [[GitLab/Test Instance|test instance]] in WMCS/VPS serving https://gitlab.devtools.wmcloud.org/
 
== GitLab instances ==
 
[[gitlab1001]], [[gitlab2001]] and test instance gitlab-prod-1001 are setup using puppet. The configuration currently lives in [[gerrit:plugins/gitiles/operations/puppet/+/refs/heads/production/modules/profile/manifests/gitlab.pp|profile::gitlab]]. Former configuration from [[gerrit:plugins/gitiles/operations/gitlab-ansible|gitlab-ansible]] was migrated completely to puppet (see [[phab:T283076|T283076]]). GitLab is installed as a [https://docs.gitlab.com/omnibus/ Omnibus installation] on all instances. So all GitLab components are installed using the official packages and are executed on a single host. The reasons for this setup can be found in the [[mw:GitLab/Initialization|Initialization docs in Mediawiki]].
 
GitLab login is implemented with SSO using the [[CAS-SSO|CAS/SSO]]. So users will be redirected to idp.wikimedia.org (idp.wmcloud.org on WMCS/VPS) to login to the SSO portal. Authentication is currently open to all users with a Wikimedia developer account for the production instance. Access to the replica and test instance is restricted to WMF/NDA groups.
 
== GitLab runners ==
 
GitLab offers CI/CD capabilities. For our current and Runner documentation, see [[GitLab/Gitlab Runner]].
 
== SSH fingerprints ==
 
See [[Help:SSH_Fingerprints/gitlab.wikimedia.org]] for an overview of all fingerprints at once.
 
Each gitlab server has 4 IPs on the same network interface. One IPv4 and one IPv6 for server, the standard sshd that admins use to connect to the individual backend (gitlab1001.wikimedia.org/gitlab2001.wikimedia.org) and one IPv4 and IPv6 for the service address (gitlab.wikimedia.org).
 
If you connect to the service as a user you _should_ expect to see the one for the service IP but currently you will see the one for the backend you are connecting to. Currently this is [[gitlab1001]] but it could change when we switch data centers or fail over.
 
We are looking into getting a new configuration option into gitlab upstream to properly fix this. Meanwhile you can find fingerprints linked on the server pages, [[gitlab1001]] and [[gitlab2001]] and all fingerprints in a single place at [[Help:SSH_Fingerprints/gitlab.wikimedia.org]].
 
also see the status of this ticket: [[phab:T296944]]
 
== How to create or migrate a repo / group / project ==
 
See [[mw:GitLab/Hosting a project on GitLab]] for full user documentation.
 
== Tickets ==
 
*[[phab:T274459]] (VM creation request)
*[[phab:T296944]] (Self-reported GitLab SSH host key fingerprints don’t appear to match actual host key fingerprints)
*[[phab:T295481]] (Setup GitLab Runner in trusted environment)
 
[[Category:SRE Service Operations]]

Revision as of 20:53, 18 May 2022

This page contains SRE related topics for GitLab. For GitLab application-specific information, user documentation, and policy, please see mw:GitLab on mediawiki.org.

GitLab is reachable at https://gitlab.wikimedia.org/. We run multiple instances of GitLab:

GitLab instances

gitlab1001, gitlab2001 and test instance gitlab-prod-1001 are setup using puppet. The configuration currently lives in profile::gitlab. Former configuration from gitlab-ansible was migrated completely to puppet (see T283076). GitLab is installed as a Omnibus installation on all instances. So all GitLab components are installed using the official packages and are executed on a single host. The reasons for this setup can be found in the Initialization docs in Mediawiki.

GitLab login is implemented with SSO using the CAS/SSO. So users will be redirected to idp.wikimedia.org (idp.wmcloud.org on WMCS/VPS) to login to the SSO portal. Authentication is currently open to all users with a Wikimedia developer account for the production instance. Access to the replica and test instance is restricted to WMF/NDA groups.

GitLab runners

GitLab offers CI/CD capabilities. For our current and Runner documentation, see GitLab/Gitlab Runner.

SSH fingerprints

See Help:SSH_Fingerprints/gitlab.wikimedia.org for an overview of all fingerprints at once.

Each gitlab server has 4 IPs on the same network interface. One IPv4 and one IPv6 for server, the standard sshd that admins use to connect to the individual backend (gitlab1001.wikimedia.org/gitlab2001.wikimedia.org) and one IPv4 and IPv6 for the service address (gitlab.wikimedia.org).

If you connect to the service as a user you _should_ expect to see the one for the service IP but currently you will see the one for the backend you are connecting to. Currently this is gitlab1001 but it could change when we switch data centers or fail over.

We are looking into getting a new configuration option into gitlab upstream to properly fix this. Meanwhile you can find fingerprints linked on the server pages, gitlab1001 and gitlab2001 and all fingerprints in a single place at Help:SSH_Fingerprints/gitlab.wikimedia.org.

also see the status of this ticket: phab:T296944

How to create or migrate a repo / group / project

See mw:GitLab/Hosting a project on GitLab for full user documentation.

Tickets

  • phab:T274459 (VM creation request)
  • phab:T296944 (Self-reported GitLab SSH host key fingerprints don’t appear to match actual host key fingerprints)
  • phab:T295481 (Setup GitLab Runner in trusted environment)