From 8ccbed99a72baf9df7a5b47b5bef10feb0b3c66a Mon Sep 17 00:00:00 2001
From: Tomi Toma <75096265+ttoma00@users.noreply.github.com>
Date: Sun, 29 Sep 2024 16:01:45 +0200
Subject: [PATCH] Create README.md (#2549)

---
 .../week7/ttoma-emilsjol/README.md            | 25 +++++++++++++++++++
 1 file changed, 25 insertions(+)
 create mode 100644 contributions/presentation/week7/ttoma-emilsjol/README.md

diff --git a/contributions/presentation/week7/ttoma-emilsjol/README.md b/contributions/presentation/week7/ttoma-emilsjol/README.md
new file mode 100644
index 0000000000..92ccbb1c80
--- /dev/null
+++ b/contributions/presentation/week7/ttoma-emilsjol/README.md
@@ -0,0 +1,25 @@
+# Assignment Proposal
+
+## Title
+Chaos Engineering with Chaos Monkey
+
+## Names and KTH ID
+
+  - Student Tomi Toma (ttoma@kth.se)
+  - Student Emil Sjölander (emilsjol@kth.se)
+
+## Deadline
+
+Week 7
+
+## Category
+
+Presentation
+
+## Description
+
+In this presentation we will talk about Chaos Monkey which is a tool created by Netflix that intentionally disrupts system to test the systems overall resilience. We will talk about how Chaos Monkey fits in with Chaos Engineering and DevOps and its practical application to ensure system reliability.
+
+**Relevance**
+
+This is relevant to DevOps because it helps developers to identify weakness in production systems early and patch them and reaching the goals of continuous delivery, resilience and high up time for the users. By continously tsting failiures devops teams can confidently realse robust and fault tolerant systems.