summaryrefslogtreecommitdiff
path: root/content
diff options
context:
space:
mode:
Diffstat (limited to 'content')
-rw-r--r--content/intro.tex37
1 files changed, 21 insertions, 16 deletions
diff --git a/content/intro.tex b/content/intro.tex
index ecf4c84..2233cb3 100644
--- a/content/intro.tex
+++ b/content/intro.tex
@@ -89,11 +89,12 @@ We propose that digital twinning can be enhanced by integrating predictive analy
\begin{enumerate}[label=\emph{RQ\textsubscript{\arabic*}}, align=left, itemsep=0pt]
% First research question stolen from Capelin by Georgios Andreadis and adapted to my work.
\item \emph{How capture and assess the current state-of-the-art of digital twinning for datacenters?}\\
- There is currently a lack of a unified definition of what constitutes a \gls{dcdt}, and the differences between a \gls{dcdt} and a generic \gls{dt}.
- It is necessary that we establish a common definition of a \gls{dcdt} in the research community.
+ There is currently a lack of a unified system model of what constitutes a \gls{dcdt}, and the differences between existing \gls{dcdt} deployments.
+ It is necessary that we establish a common model of a \gls{dcdt} in the research community.
We must develop a holistic \gls{dcdt} model that factors in the necessary components of a \gls{dt}.
- This is very challenging, because the \gls{dcdt} definition must address many kinds of operational and technical requirements, compatible with the existing background on \gls{dt}'s.
+ This is very challenging, because the \gls{dcdt} system model must address many kinds of operational and technical requirements, compatible with the existing background on \gls{dt}s.
\item \emph{How to design a \gls{dcdt} system model using discrete-event simulation and predictive data analysis?}\\
+ % You should start referring to my_system as a framework, rather than a standalone system.
Existing \gls{dcdt} frameworks lack the necessary predictive capabilities to prevent unplanned behaviour in datacenters.
In this work, we aim to explore the design space of a predictive \gls{dcdt} and the different design trade-offs.
Through discrete-event simulation, we aim provide the foundation for the system model to interact with a physical datacenter.
@@ -130,24 +131,28 @@ We define the correct experiment setup(s) and perform the experiments on a speci
\section{Thesis Contributions}\label{s:thesis-contributions}
-\subsection{Conceptual Contributions}\label{ss:conceptual_contributions}
+\begin{enumerate}
+ \item \textbf{Conceptual}:
+ \begin{enumerate}[label=\emph{C\textsubscript{\arabic*}}, align=left, labelsep=0pt]
+ \item We conduct a systematic literature review and detailed analysis of existing works on digital twinning in the scientific research community.
+ We collect and organize the \gls{dcdt}'s characteristics and based on our findings we propose a unified system model of the design space.
+ \item We propose the design of \gls{my_system}, a discrete-event \gls{dcdt} for reliable and timely failure prediction in datacenters.
+ \gls{my_system} includes a set of novel system components which leverage \gls{oda} and discrete-event simulation.
-\begin{enumerate}[label=\emph{C\textsubscript{\arabic*}}, align=left, labelsep=0pt]
- \item We conduct a systematic literature review and detailed analysis of existing \gls{dcdt}'s in the scientific community.
- We collect and organize the \gls{dcdt}'s characteristics and based on our findings we propose a unified system model of the design space.
- \item We propose the design of a discrete-event \gls{dcdt} for reliable and timely failure prediction in datacenters.
- The conceptual design of the predictive \gls{dcdt} proposes a set of system components which leverage operational data analysis and discrete-event simulation.
-\end{enumerate}
+ \item We evaluate \gls{my_system} using a novel experimentation technique and datacenter workload traces from the industry.
+ We design a method to evaluate \gls{dcdt}s without expensive and costly real-world experimentation.
+ We conduct a set of experiments and analyse the results.
+ \end{enumerate}
+ \item \textbf{Technical:}
-\subsection{Technical Contributions}\label{ss:technical_contributions}
+ \begin{enumerate}[label=\emph{C\textsubscript{\arabic*}}, align=left, labelsep=0pt]
+ \item We prototype \gls{my_system} following the established \gls{dt} design principles using discrete-event simulation and \gls{oda}.
+ We include the code as an Open Science artifact and ensure the prototype remains accessible to the broader scientific community including exhaustive project documentation.
+ \item We provide the experiment setup, validation and evaluation of \gls{my_system} for predicting datacenter failures in real-time as an Open Science artifact.
+ \end{enumerate}
-\begin{enumerate}[label=\emph{C\textsubscript{\arabic*}}, align=left, labelsep=0pt]
- \item We prototype \gls{my_system} following the established \gls{dt} design principles using discrete-event simulation and \gls{oda}.
- \item We evaluate the predictive \gls{dcdt} prototype using a novel experimentation technique and datacenter workload traces from the industry.
- We design a method to evaluate \gls{dcdt}'s without the overhead of real-world computation, conduct a set of experiments and analyse the results.
\end{enumerate}
-
\section{Plagiarism Declaration}\label{s:plagiarism-declaraion}
I hereby declare that this thesis is my own independent work and writing.
The thesis does not contain any material copied from other sources (person, Internet, or \gls{ai}), and has not been submitted for assessment elsewhere.