Dedicated: hand EM references from @denhams to @mckgl, remove @nitinduttsharma (048961e3) · Commits · GitLab.com / Content Sites / handbook

content/handbook/engineering/infrastructure-platforms/gitlab-dedicated/_index.md

+0 −4

Changes for content/handbook/engineering/infrastructure-platforms/gitlab-dedicated/_index.md: 0 added lines, 4 removed lines.
Original line number	Diff line number	Diff line
		@@ -35,10 +35,6 @@ The following people are members of the Dedicated:Environment Automation Team:

		{{< team-by-manager-slug "o-lluch" >}}

		{{< team-by-manager-slug "denhams" >}}

		{{< team-by-manager-slug "nitinduttsharma" >}}

		The following people are members of the Dedicated:US Public Sector Services Team:

		{{< team-by-manager-slug "mckgl" >}}

content/handbook/engineering/infrastructure-platforms/gitlab-dedicated/dedicated-migrations.md

+1 −1

Changes for content/handbook/engineering/infrastructure-platforms/gitlab-dedicated/dedicated-migrations.md: 1 added line, 1 removed line.
Original line number	Diff line number	Diff line
		@@ -133,7 +133,7 @@ Many customers need to perform "catch-up" GitLab upgrades in the post-support wi

		##### Outside the 2-Week Window

		Support is primarily asynchronous via Request for Help (RFH) tickets. Per `@fviegas` all Dedicated Migrations RFH are considered priority 1. Synchronous customer calls are handled adhoc on a case-by-case basis, requiring approval from one of Steve Denham/Oriol Lluch Parellada based on team availability.
		Support is primarily asynchronous via Request for Help (RFH) tickets. Per `@fviegas` all Dedicated Migrations RFH are considered priority 1. Synchronous customer calls are handled adhoc on a case-by-case basis, requiring approval from one of Matt Kirkevold/Oriol Lluch Parellada based on team availability.

		##### RFH Process

content/handbook/engineering/infrastructure-platforms/gitlab-dedicated/ecosystem.md

+1 −2

Changes for content/handbook/engineering/infrastructure-platforms/gitlab-dedicated/ecosystem.md: 1 added line, 2 removed lines.
Original line number	Diff line number	Diff line
		@@ -69,6 +69,5 @@ Core platform development (Runners Platform team), product features, direct vend

		---

		DRI: @nitinduttsharma
		Team: {{< team-by-manager-slug "nitinduttsharma" >}}
		DRI: @fviegas
		Approval: @fviegas - Director, Dedicated Infrastructure

content/handbook/engineering/infrastructure-platforms/gitlab-dedicated/environment-automation.md

+6 −6

Changes for content/handbook/engineering/infrastructure-platforms/gitlab-dedicated/environment-automation.md: 6 added lines, 6 removed lines.
Original line number	Diff line number	Diff line
		@@ -13,7 +13,7 @@ We follow the same processes as listed on the [Dedicated Group](/handbook/engine

		{{< team-by-manager-slug "o-lluch" >}}

		{{< team-by-manager-slug "denhams" >}}
		{{< team-by-manager-slug "mckgl" >}}

		## Functional Teams after Act 2

		@@ -23,11 +23,11 @@ To fulfill this intent, Environment Automation was split into 5 functional teams

		\| Functional team \| Serves \| Scope and ownership \| Key alignment \| Manager \| Functional Lead \|
		\|---\|---\|---\|---\|---\|---\|
		\| Platform Integration \| GitLab module development teams \| Owns the integration path that brings external products and modular GitLab features into Dedicated, including Dedicated binding, productionization, and the testing strategy for integration paths. \| Theseus and the Test Automation Framework. \| Interim: {{< member-by-gitlab "o-olluch" >}}\| {{< member-by-gitlab "bmckitrick" >}} \|
		\| Platform Resilience \| Dedicated operations teams \| Owns resilience and self-healing products for individual tenants — including disaster recovery, autoscaling, automated capacity planning, rate limiting, and other mechanisms that allow an instance to detect, absorb, and recover from failures with minimal human intervention, while keeping infrastructure cost-effective. \| Dedicated Orchestration Automation and Cloud Cost Utilization. \| {{< member-by-gitlab "denhams" >}}\| {{< member-by-gitlab "ktchernov" >}} \|
		\| Dedicated Responder Automation \| Dedicated SRE and DevOps responders \| Owns responder workflows and tooling for Dedicated incidents, including signal and alert enrichment, alert routing, alert aggregation and automated troubleshooting. \| Incident Management and Signals/Observability in Production Engineering. \| {{< member-by-gitlab "o-olluch" >}}\| {{< member-by-gitlab "troblot" >}} \|
		\| Dedicated Orchestration Automation \| Dedicated operators and DevOps teams \| Owns the core orchestration platform and change-management automation: job workflows, underlying infrastructure changes, maintenance operations, and tenant-model segments. Platform Resilience, Responder Automation, and Platform Integration consume the platform and own their workflows and configuration within it. \| Switchboard Orchestration APIs; also coordinates with Service Delivery Platform and Cells operations where interfaces overlap. \| {{< member-by-gitlab "o-olluch" >}}\| {{< member-by-gitlab "SamirHafez" >}} \|
		\| Dedicated Commercial Features \| Dedicated Product and Dedicated customers \| Owns the commercial Dedicated feature roadmap and production-ready implementations, including customer-facing infrastructure and isolation capabilities such as BYOD, network configuration, and Geo Proxy. \| Platform Integration and Dedicated Orchestration Automation for artifact injection, integration, and production quality. \| {{< member-by-gitlab "denhams" >}}\| {{< member-by-gitlab "vmondo" >}} \|
		\| Platform Integration \| GitLab module development teams \| Owns the integration path that brings external products and modular GitLab features into Dedicated, including Dedicated binding, productionization, and the testing strategy for integration paths. \| Theseus and the Test Automation Framework. \| Interim: {{< member-by-gitlab "o-lluch" >}}\| {{< member-by-gitlab "bmckitrick" >}} \|
		\| Platform Resilience \| Dedicated operations teams \| Owns resilience and self-healing products for individual tenants — including disaster recovery, autoscaling, automated capacity planning, rate limiting, and other mechanisms that allow an instance to detect, absorb, and recover from failures with minimal human intervention, while keeping infrastructure cost-effective. \| Dedicated Orchestration Automation and Cloud Cost Utilization. \| {{< member-by-gitlab "mckgl" >}}\| {{< member-by-gitlab "ktchernov" >}} \|
		\| Dedicated Responder Automation \| Dedicated SRE and DevOps responders \| Owns responder workflows and tooling for Dedicated incidents, including signal and alert enrichment, alert routing, alert aggregation and automated troubleshooting. \| Incident Management and Signals/Observability in Production Engineering. \| {{< member-by-gitlab "o-lluch" >}}\| {{< member-by-gitlab "troblot" >}} \|
		\| Dedicated Orchestration Automation \| Dedicated operators and DevOps teams \| Owns the core orchestration platform and change-management automation: job workflows, underlying infrastructure changes, maintenance operations, and tenant-model segments. Platform Resilience, Responder Automation, and Platform Integration consume the platform and own their workflows and configuration within it. \| Switchboard Orchestration APIs; also coordinates with Service Delivery Platform and Cells operations where interfaces overlap. \| {{< member-by-gitlab "o-lluch" >}}\| {{< member-by-gitlab "SamirHafez" >}} \|
		\| Dedicated Commercial Features \| Dedicated Product and Dedicated customers \| Owns the commercial Dedicated feature roadmap and production-ready implementations, including customer-facing infrastructure and isolation capabilities such as BYOD, network configuration, and Geo Proxy. \| Platform Integration and Dedicated Orchestration Automation for artifact injection, integration, and production quality. \| {{< member-by-gitlab "mckgl" >}}\| {{< member-by-gitlab "vmondo" >}} \|

		## Working with us

content/handbook/engineering/infrastructure-platforms/gitlab-dedicated/incident-management/imoc/index.md

+3 −3

Changes for content/handbook/engineering/infrastructure-platforms/gitlab-dedicated/incident-management/imoc/index.md: 3 added lines, 3 removed lines.
Original line number	Diff line number	Diff line
		@@ -240,7 +240,7 @@ As IMOC, you have several escalation paths available to resolve incidents quickl
		1. Acknowledge alert, check who's current [GDEOC](https://gitlab.pagerduty.com/schedules/PE57MNA)
		2. Slack DM: "Hi [name], you have a PagerDuty alert. Can you respond?"
		3. If no response (10 min): Reassign to another Dedicated SRE in current timezone and post in #gitlab-dedicated-team
		4. If still stuck: Page all Dedicated Management (@fviegas, @o-lluch, @denhams, @nitinduttsharma)
		4. If still stuck: Page all Dedicated Management (@fviegas, @o-lluch, @mckgl)
		5. Document, let GDEOC's manager follow up on missed page

		Key Lesson: Find coverage first, address missed page later.
		@@ -292,7 +292,7 @@ As IMOC, you have several escalation paths available to resolve incidents quickl
		\| AWS infrastructure \| AWS Enterprise Support \| AWS Support Sheet \|
		\| GitLab app bug \| Tier 2 / Dev Escalation \| [`/inc escalate`](https://gitlab-com.gitlab.io/gl-infra/gitlab-dedicated/team/runbooks/on-call.html#escalating-internally-gitlab-teams) → tier2: [team] in incident Slack channel \|
		\| Security vulnerability \| SIRT \| They engage you \|
		\| Management support \| Dedicated Management \| @fviegas, @o-lluch, @denhams, @nitinduttsharma \|
		\| Management support \| Dedicated Management \| @fviegas, @o-lluch, @mckgl \|

		## Leading vs. Doing

		@@ -364,7 +364,7 @@ As IMOC, you have several escalation paths available to resolve incidents quickl
		Help:

		- Current IMOC: PagerDuty "GitLab Dedicated Platform Leadership Escalation" schedule
		- EMs: @fviegas, @o-lluch, @denhams, @nitinduttsharma
		- EMs: @fviegas, @o-lluch, @mckgl
		- Slack: #gitlab-dedicated-team, #incident-management

		---

Original line number	Diff line number	Diff line
		@@ -13,7 +13,7 @@ We follow the same processes as listed on the [Dedicated Group](/handbook/engine

		{{< team-by-manager-slug "o-lluch" >}}

		{{< team-by-manager-slug "denhams" >}}
		{{< team-by-manager-slug "mckgl" >}}

		## Functional Teams after Act 2

		@@ -23,11 +23,11 @@ To fulfill this intent, Environment Automation was split into 5 functional teams

		\| Functional team \| Serves \| Scope and ownership \| Key alignment \| Manager \| Functional Lead \|
		\|---\|---\|---\|---\|---\|---\|
		\| Platform Integration \| GitLab module development teams \| Owns the integration path that brings external products and modular GitLab features into Dedicated, including Dedicated binding, productionization, and the testing strategy for integration paths. \| Theseus and the Test Automation Framework. \| Interim: {{< member-by-gitlab "o-olluch" >}}\| {{< member-by-gitlab "bmckitrick" >}} \|
		\| Platform Resilience \| Dedicated operations teams \| Owns resilience and self-healing products for individual tenants — including disaster recovery, autoscaling, automated capacity planning, rate limiting, and other mechanisms that allow an instance to detect, absorb, and recover from failures with minimal human intervention, while keeping infrastructure cost-effective. \| Dedicated Orchestration Automation and Cloud Cost Utilization. \| {{< member-by-gitlab "denhams" >}}\| {{< member-by-gitlab "ktchernov" >}} \|
		\| Dedicated Responder Automation \| Dedicated SRE and DevOps responders \| Owns responder workflows and tooling for Dedicated incidents, including signal and alert enrichment, alert routing, alert aggregation and automated troubleshooting. \| Incident Management and Signals/Observability in Production Engineering. \| {{< member-by-gitlab "o-olluch" >}}\| {{< member-by-gitlab "troblot" >}} \|
		\| Dedicated Orchestration Automation \| Dedicated operators and DevOps teams \| Owns the core orchestration platform and change-management automation: job workflows, underlying infrastructure changes, maintenance operations, and tenant-model segments. Platform Resilience, Responder Automation, and Platform Integration consume the platform and own their workflows and configuration within it. \| Switchboard Orchestration APIs; also coordinates with Service Delivery Platform and Cells operations where interfaces overlap. \| {{< member-by-gitlab "o-olluch" >}}\| {{< member-by-gitlab "SamirHafez" >}} \|
		\| Dedicated Commercial Features \| Dedicated Product and Dedicated customers \| Owns the commercial Dedicated feature roadmap and production-ready implementations, including customer-facing infrastructure and isolation capabilities such as BYOD, network configuration, and Geo Proxy. \| Platform Integration and Dedicated Orchestration Automation for artifact injection, integration, and production quality. \| {{< member-by-gitlab "denhams" >}}\| {{< member-by-gitlab "vmondo" >}} \|
		\| Platform Integration \| GitLab module development teams \| Owns the integration path that brings external products and modular GitLab features into Dedicated, including Dedicated binding, productionization, and the testing strategy for integration paths. \| Theseus and the Test Automation Framework. \| Interim: {{< member-by-gitlab "o-lluch" >}}\| {{< member-by-gitlab "bmckitrick" >}} \|
		\| Platform Resilience \| Dedicated operations teams \| Owns resilience and self-healing products for individual tenants — including disaster recovery, autoscaling, automated capacity planning, rate limiting, and other mechanisms that allow an instance to detect, absorb, and recover from failures with minimal human intervention, while keeping infrastructure cost-effective. \| Dedicated Orchestration Automation and Cloud Cost Utilization. \| {{< member-by-gitlab "mckgl" >}}\| {{< member-by-gitlab "ktchernov" >}} \|
		\| Dedicated Responder Automation \| Dedicated SRE and DevOps responders \| Owns responder workflows and tooling for Dedicated incidents, including signal and alert enrichment, alert routing, alert aggregation and automated troubleshooting. \| Incident Management and Signals/Observability in Production Engineering. \| {{< member-by-gitlab "o-lluch" >}}\| {{< member-by-gitlab "troblot" >}} \|
		\| Dedicated Orchestration Automation \| Dedicated operators and DevOps teams \| Owns the core orchestration platform and change-management automation: job workflows, underlying infrastructure changes, maintenance operations, and tenant-model segments. Platform Resilience, Responder Automation, and Platform Integration consume the platform and own their workflows and configuration within it. \| Switchboard Orchestration APIs; also coordinates with Service Delivery Platform and Cells operations where interfaces overlap. \| {{< member-by-gitlab "o-lluch" >}}\| {{< member-by-gitlab "SamirHafez" >}} \|
		\| Dedicated Commercial Features \| Dedicated Product and Dedicated customers \| Owns the commercial Dedicated feature roadmap and production-ready implementations, including customer-facing infrastructure and isolation capabilities such as BYOD, network configuration, and Geo Proxy. \| Platform Integration and Dedicated Orchestration Automation for artifact injection, integration, and production quality. \| {{< member-by-gitlab "mckgl" >}}\| {{< member-by-gitlab "vmondo" >}} \|

		## Working with us