Repos-que-me-gustan/devops-exercises
1
0
Fork 0
Code Pull Requests Activity

Add questions on SRE and Chaos Engineering (#325)

Browse Source
This commit is contained in:
Chimon Sultan 2022-12-12 15:01:55 +01:00 committed by GitHub
parent 407533d580
commit 9d0662d8cc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 44 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
topics/chaos_engineering/README.md
View File

@ -29,3 +29,17 @@ According to [Gremlin](gremlin.com) there are three steps:
The process then repeats itself either with same scenario or a new one.
</b></details>
<details>
<summary>Cite a few tools used to operate Chaos exercises</summary><br><b>
- AAWS Fault Injection Simulator: inject failures in AWS resources
- Azure Chaos Studio: inject failures in Azure resources
- Chaos Monkey: one of the most famous tools to orchestrate Chaos on diverse Cloud providers
- Litmus - A Framework for Kubernetes
- Chaos Mesh: for Cloud Kubernetes platforms
See an extensive list [here](https://github.com/dastergon/awesome-chaos-engineering)
</b></details>

32
topics/devops/README.md
View File

@ -393,10 +393,10 @@ This situation might lead to bugs which hard to identify and reproduce.
<details>
<summary>Explain Declarative and Procedural styles. The technologies you are familiar with (or using) are using procedural or declarative style?</summary><br><b>
Declarative - You write code that specifies the desired end state<br><b>
Declarative - You write code that specifies the desired end state<br>
Procedural - You describe the steps to get to the desired end state
Declarative Tools - Terraform, Puppet, CloudFormation, Ansible<br><b>
Declarative Tools - Terraform, Puppet, CloudFormation, Ansible<br>
Procedural Tools - Chef
To better emphasize the difference, consider creating two virtual instances/servers.
@ -506,3 +506,31 @@ Google: "Monitoring is one of the primary means by which service owners keep tra
Read more about it [here](https://sre.google/sre-book/introduction)
</b></details>
<details>
<summary>What are the two main SRE KPIs</summary><br><b>
Service Level Indicators (SLI) and Service Level Objectives (SLO).
</b></details>
<details>
<summary>What is Toil?</summary><br><b>
Google: Toil is the kind of work tied to running a production service that tends to be manual, repetitive, automatable, tactical, devoid of enduring value, and that scales linearly as a service grows
Read more about it [here](https://sre.google/sre-book/eliminating-toil/)
</b></details>
<details>
<summary>What is a postmortem ? </summary><br><b>
The postmortem is a process that should take place folowing an incident. It’s purpose is to identify the root cause of an incident and the actions that should be taken to avoid this kind of incidents from hapenning again. </b></details>
<details>
<summary>What is the core value often put forward when talking about postmortem?</summary><br><b>
Blamelessness.
Postmortems need to be blameless and this value should be remided at the begining of every postmortem. This is the best way to ensure that people are playing the game to find the root cause and not trying to hide their possible faults.</b></details>