Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add questions on SRE and Chaos Engineering #325

Merged
merged 1 commit into from
Dec 12, 2022
Merged

Add questions on SRE and Chaos Engineering #325

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions topics/chaos_engineering/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,4 +28,18 @@ 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 changes: 30 additions & 2 deletions topics/devops/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -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>