Changes for content/handbook/engineering/architecture/design-documents/capacity_planning/_index.md: 1 added line, 1 removed line.
Original line number
Diff line number
Diff line
@@ -45,7 +45,7 @@ For illustration, we can see a saturation forecast plot below for the `disk_spac
Within the 90 days forecast horizon, we predict a violation of the `soft` SLO (set at 85% saturation) and this resulted in the creation of a [capacity planning issue](https://gitlab.com/gitlab-com/gl-infra/capacity-planning/-/issues/1219) for further review and potential actions.
At present, the Scalability::Observability group reviews those issues and engages with the respective DRI for the service in question to remedy a saturation concern.
For GitLab.com capacity planning, we operate Tamland from a scheduled CI pipeline with access to the central Thanos, which provides saturation and utilization metrics for GitLab.com.
The CI pipeline produces the desired report, exposes it on GitLab Pages and also creates capacity planning issues.
Changes for content/handbook/engineering/infrastructure/team/gitlab-dedicated/architecture/from-dedicated-to-cells-technical-analysis.md: 2 added lines, 2 removed lines.
Original line number
Diff line number
Diff line
@@ -49,8 +49,8 @@ are not replicas of one another, or the same configuration with different input
smaller/cheaper copy of Production). They are two distinctive environments, built in parallel to one another.
<pfloat="middle">
<imgalt="GKE Zonal Configuration for Staging"src="./img/gke-zonal-conf-gstg.png"width="49%"/>
<imgalt="GKE Zonal Configuration for Production"src="./img/gke-zonal-conf-gprd.png"width="49%"/>
<imgalt="GKE Zonal Configuration for Staging"src="/images/engineering/infrastructure/team/gitlab-dedicated/architecture/gke-zonal-conf-gstg.png"width="49%"/>
<imgalt="GKE Zonal Configuration for Production"src="/images/engineering/infrastructure/team/gitlab-dedicated/architecture/gke-zonal-conf-gprd.png"width="49%"/>
</p>
*Same Same, but Different: the GKE Zonal Configuration for Staging and Production. Similar, but not the same.*
Changes for content/handbook/enterprise-data/organization/data-science/_index.md: 1 added line, 1 removed line.
Original line number
Diff line number
Diff line
@@ -108,7 +108,7 @@ Please refer to the [Data Science Initiatives Internal Handbook](https://interna
The Data Science Team follows [Cross-Industry standard process for data mining (CRISP-DM)](https://en.wikipedia.org/wiki/Cross-industry_standard_process_for_data_mining), which consists of 6 iterative phases: