From dc6d2bf851fc5334687780cea177a5397c5b3b30 Mon Sep 17 00:00:00 2001
From: Stanislav Kosorin <stanokosorin4@gmail.com>
Date: Tue, 20 Aug 2024 11:33:23 +0200
Subject: [PATCH] Set size of images to 500

---
 REPORT.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/REPORT.md b/REPORT.md
index 0606ea8..8b24768 100644
--- a/REPORT.md
+++ b/REPORT.md
@@ -78,7 +78,7 @@ Next, we want to be able to change the hosts during runtime. We built a Python-b
 
 The controller also keeps track of the match-action table state, by a target IP -> index mapping. The index mapping corresponds to the value in the `ecmp_nhop` table. This makes it more efficient to look up the index of a specific IP in the table, without the need to fetch table state from the switch on each update request.
 
-<img src="assets/controller_light.png" alt="controller" width="600"/>
+<img src="assets/controller_light.png" alt="controller" width="500"/>
 
 
 During this stage, we faced minor issues:
@@ -119,7 +119,7 @@ Using netns, veth pairs, and the iproute2 suite to set MAC and IP addresses of v
 
 The following diagram shows the created topology, including the virtual interfaces:
 
-<img src="assets/linux_network_light.png" alt="controller" width="600"/>
+<img src="assets/linux_network_light.png" alt="controller" width="500"/>
 
 Setting up a complex virtual network topology is not straightforward. We outlined key challenges we faced during implementation:
 
@@ -135,7 +135,7 @@ Specifically, Podman uses the netavark backend for virtual networking. Each netw
 
 The following diagram shows the network topology of a single host and the connection of the network to a switch port:
 
-<img src="assets/container_interface_light.png" alt="container_interface" width="400"/>
+<img src="assets/container_interface_light.png" alt="container_interface" width="500"/>
 
 We wrote a script to create a network and a pod for each container. A pod is a group of containers with a shared IP address. This is also the case within the Kubernetes network model. We built a container image using the TCP server executable from the previous steps. Analogously, we built a client image. 
 
@@ -159,7 +159,7 @@ For simplicity, the switch container runs on the host network. The container ima
 
 The following diagram shows the network topology, which consists of 4 Podman networks interfaced by bridges, connected to a single BMv2 switch running in a container, but on the host network:
 
-<img src="assets/container_network_light.png" alt="container_interface" width="400"/>
+<img src="assets/container_network_light.png" alt="container_interface" width="500"/>
 
 
 ### Redis container migration