Commit 2830ddd3 authored by Gerardo Lopez-Fernandez's avatar Gerardo Lopez-Fernandez

Merge branch 'gerir/infra/blueprint/deuppercase' into 'master'

style consistency: deuppercase headings

See merge request !15355
parents 1109cf03 8424ec66
Pipeline #32705662 failed with stages
in 13 minutes and 9 seconds
...@@ -38,9 +38,9 @@ GitLab.com's MTBF. ...@@ -38,9 +38,9 @@ GitLab.com's MTBF.
Infrastructure's OKRs are crafted along these lines of thought. Infrastructure's OKRs are crafted along these lines of thought.
## ROADMAP ## Roadmap
### CULTURAL FOCUS ### Cultural Focus
Achieving ours goals requires a high-performance team that adheres to [**GitLab's values**](/handbook/values/). Achieving ours goals requires a high-performance team that adheres to [**GitLab's values**](/handbook/values/).
We are not simply runnig GitLab.com: we are also building a team we love to work with. As Reed Hastings [eloquently We are not simply runnig GitLab.com: we are also building a team we love to work with. As Reed Hastings [eloquently
...@@ -66,7 +66,7 @@ There are three cultural aspects to focus on as we continue to to develop and po ...@@ -66,7 +66,7 @@ There are three cultural aspects to focus on as we continue to to develop and po
Infrastructure-centric mentality and eliminate SRE-centric nomenclature where appropriate (i.e., #sre-lounge => Infrastructure-centric mentality and eliminate SRE-centric nomenclature where appropriate (i.e., #sre-lounge =>
#infrastructure). #infrastructure).
### WORKLOAD FOCUS ### Workload Focus
Our workload should be managed in a fairly predictable fashion. A minimum of 60% of our work should be known, Our workload should be managed in a fairly predictable fashion. A minimum of 60% of our work should be known,
scheduled work. This work is defined as work that: scheduled work. This work is defined as work that:
...@@ -75,9 +75,9 @@ scheduled work. This work is defined as work that: ...@@ -75,9 +75,9 @@ scheduled work. This work is defined as work that:
When the planned work entails design and discussion, no work changing production should be performed on that issue: create follow up issues as the end result and definition of the work to be done. When the planned work entails design and discussion, no work changing production should be performed on that issue: create follow up issues as the end result and definition of the work to be done.
### FUNCTIONAL FOCUS ### Functional Focus
#### DATABASE #### Database
##### Backup, Restore, and Verification ##### Backup, Restore, and Verification
...@@ -94,7 +94,7 @@ When the planned work entails design and discussion, no work changing production ...@@ -94,7 +94,7 @@ When the planned work entails design and discussion, no work changing production
* Near real-time replication `[uptime]` * Near real-time replication `[uptime]`
* Time-delayed replication `[data protection]` * Time-delayed replication `[data protection]`
#### STORAGE #### Storage
* **Fortified Storage Nodes** `[uptime]` and `[data protection]` * **Fortified Storage Nodes** `[uptime]` and `[data protection]`
* Protect against file system corruption and unwanted deletions `[data protection]` * Protect against file system corruption and unwanted deletions `[data protection]`
...@@ -103,7 +103,7 @@ When the planned work entails design and discussion, no work changing production ...@@ -103,7 +103,7 @@ When the planned work entails design and discussion, no work changing production
* **Repo management tools** `[uptime]` * **Repo management tools** `[uptime]`
* Ability to relocate projects and repos to alternate storage nodes * Ability to relocate projects and repos to alternate storage nodes
#### OBSERVABILITY #### Observability
* **Error Budgets** * **Error Budgets**
* Master definition of uptime * Master definition of uptime
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment