feat: finished the thesis

1 files changed, 11 insertions, 0 deletions

diff --git a/content/implementation.tex b/content/implementation.tex
index 3c77011..16cf7ca 100644
--- a/content/implementation.tex
+++ b/content/implementation.tex
@@ -165,6 +165,17 @@ In order to turn it into a \gls{dt}, we have made several design decisions and e
 	\item \textbf{\code{HTTPClient}}\\
 	      The \code{HTTPClient} offers the necessary functionality to communicate between the \gls{dt} and the datacenter.
 	      We decided to use the \gls{http} protocol for short, one-off communications between the \gls{dt} and the datacenter, as is common industry practice.
+	\item \textbf{\code{CpuUtilVictimSelector}}\\
+	      In order to ensure \code{OpenDC} can model different failure injection algorithms, we added new methods for selecting the hosts to be stopped.
+	      The \code{CpuUtilVictimSelector} selects hosts based on their current \gls{cpu} utilization (\ie the hosts with the highest utilization are stopped first).
+	\item \textbf{\code{RoundRobinVictimSelector}}\\
+	      The \code{RoundRobinVictimSelector} is another algorithm to used to inject failures into hosts.
+	      This method works in a round robin fashion, using the alphabetical order of the hosts (\ie by name).
+	      For example, in a scenario hosts \code{H-01} to \code{H-20} are stopped first, and then \code{H-20} to \code{H-40} are stopped next, \etc
+	\item \textbf{\code{RandomVictimSelector}}\\
+	      This is the default \code{OpenDC} victim selection algorithm.
+	      It randomly chooses which host to stop when injecting failures.
+	      This component is left unmodified, but we include it here for the purposes of listing all the failure injection algorithms we use together.
 \end{enumerate}
 \begin{figure}[t]
 	\centering