|Development||various||Development||on save||Fixture||individual dev|
Development happens on a local machine. Therefore there is no way to provide any SLA. Access is to the individual dev. This could be either EE/CE depending on what the developer is working on.
|Demo||"GitLab Sales Demo Domains - Internal only" (found on the google drive)||Sales||Release||Fixture||Production Team|
This should be a fully featured version of the current EE release. The high SLA and tightened access is to ensure it is always available for sales. There are no features (feature flags/canary/etc) that we do not ship.
This environment is used as a genesis project from which all other GCP projects used to support/manage/host gitlab.com are provisioned. No compute resources are present in the project, and it is used solely to provide a mechanism for centrally managing GCP projects, provisioning IAM roles/service accounts for infrastructure deployments within those projects, and controlling which APIs are enabled for each GCP project via Infrastructure as Code (terraform).
TODO: Add reference link to README sections in gitlab-com-infrastructure repository and group-projects
|.org||dev.gitlab.org||Tools for Gitlab.com||Nightly||Real Work||Production and build team|
Currently there are two main uses for the .org environment, Builds and repos that are needed in case gitlab.com is offline. This is a critical piece of infrastructure that is always growing in size due to build artifacts. There are discussions to make a new build server where nightly CE/EE builds can be deployed or to move the infra repos to a new host that would be an separate (not gitlab.com) EE instance. Although the environment has dev in its domain name don't refer to it as dev since that could be confused with a local development environment.
|Review apps||various||Test proposal||on commit||Fixture||Review app owner|
Ephemeral app environments that are created dynamically every time you push a new branch up to GitLab, and they're automatically deleted when the branch is deleted. Single container with limited access.
|one-off||various||Testing specific features in a large environment||Release + patches||User specific||Team developing feature|
This is less of a staging environment more like a large scale development environments. This could be because of the number of repos required, or a full sized db is required. A version of CE/EE is installed and then patches are applied as work progresses. These should be very limited in number.
K8s & helm charts (cloud native)
The final version of staging is multiple container deploys managed by K8s via helm charts. This could be mapped to Master and re-deployed every time there is a successful merge to master. There is already work started to move us to containers. https://gitlab.com/gitlab-org/omnibus-gitlab/issues/2420
|ops||ops.gitlab.net||GitLab.com Operations||official ee releases||Fixture||SREs|
The ops environment hold all infrastructure that is critical for managing GitLab.com infrastructure.
At this time it includes:
|Production||gitlab.com||Production||Release Candidate||Production||Production team|
Production will be full scale and size with the ability to have a canary deploy. Production has limited access. It consists of two stages:
|Staging||staging.gitlab.com||Pre-production testing||Frequently||Pseudonymization of prod||all engineers|
Staging has the same topology as Production and includes the same components, since they share the same terraform configuration.
Staging deployments precede production deployments as described in releases, but is deployed a lot more frequently (at least every few hours, given the build is green). This would be a static environment with an pseudonymized production database. The DB is a snapshot of the production DB (updated only often enough to keep migration times to a minimum).
If you need an account to test QA issues assigned to you on Staging, you may already have an account as Production accounts are brought across to Staging. Otherwise, if you require an account to be created, create an issue in the access-request project and assign to your manager for review. Requests for access to database and server environments require the approval of your manager as well as that of one of the Infrastructure managers. The same access-request tracker should be used to request this type of access.
|pre||pre.gitlab.com||GitLab.com PreProd||Security releases and production patches||Separate and local||SREs|
The pre environment is an environment used for validating security releases and production patches. It does not have a full production HA topology or a copy of the production database.
|gitlap||gitlap.com||GitLab support testing||??||??||SREs|
|dev.gitlap||*.dev.gitlap.com||GitLab support testing||N/A||N/A||SRE and support owner|
|do.gitlap||*.do.gitlap.com||GitLab support testing||N/A||N/A||SRE and support owner|
The GitLap environment is an older domain primarily used for support testing.
All DNS records under
*.do.gitlap.com are controlled
via terraform in the dev-resources repository.
The only important system is
gitlab-runner-builder.gitlap.com which is used
as a CI runner by the gitlab-runner project.
|Self-Managed||various||Self hosted versions of CE & EE||User specific||User specific||User specific|
These are environments that are run on-premises by the end-user. We have no influence, access or control of these environments.
If you work at GitLab also see the list of nodes managed by Chef to get an idea.