diff options
Diffstat (limited to 'main.tex')
| -rw-r--r-- | main.tex | 35 |
1 files changed, 17 insertions, 18 deletions
@@ -33,7 +33,7 @@ \tiny \textbf{Figure 1.2:} Where does our work fit within the field of datacenter digital twinning? There are 5 core elements to any Digital Twin: \myCircled{A} The Digital $\rightarrow$ Physical Twin link, \myCircled{B} the Physical Twin (\emph{e.g.,} the datacenter), \myCircled{C} the Physical $\rightarrow$ Digital Twin link, \myCircled{D} the Digital Twin, \myCircled{E} the features necessary to any Digital Twin. - \textcolor{ForestGreen}{\faHighlighter~Highlighted areas are the contributions from this thesis, which include the autonomous actions resulting from predictive insights \myCircledGreen{A} and the predictive analysis itself within \myCircledGreen{E}.} + \textcolo{Green}{\faHighlighter~Highlighted areas are the contributions from this thesis, which include the autonomous actions resulting from predictive insights \myCircledGreen{A} and the predictive analysis itself within \myCircledGreen{E}.} \end{frame} \begin{frame}\frametitle{Research Questions} @@ -94,13 +94,17 @@ \begin{frame}\frametitle{\textbf{RQ2}: Reference Architecture} \begin{minipage}[b]{0.45\linewidth} - \begin{tcolorbox}[title=Use cases] - + \begin{tcolorbox}[title=Implementation] + %Add the _implementation_ figure here instead. + % I.e., the Kafka, the broker, PostgreSQL, Redis. + % In the implementation graph: keep the datacenter "just" a datacenter -- don't yet mention we use OpenDC. + % Make Kafka logos clearly defined --> add a legend with icons? \end{tcolorbox} \vspace{1cm} \end{minipage} \begin{minipage}[b]{0.45\linewidth} \begin{center} + % Change to Datacenter (Physical Twin) \includegraphics[width=1.25\textwidth]{images/ref_architecture.pdf} \end{center} \vspace{-0.2cm} @@ -117,30 +121,25 @@ %The time-series data flows first to the \texttt{Grafana} dashboard, \texttt{PostgreSQL} database and \texttt{Redis} cache, as advised in~\cite{DBLP:conf/sc/TaheriBPRHDEWPM24}. \begin{minipage}[b]{0.45\linewidth} - \begin{tcolorbox}[title=Setup Recipe] + \begin{tcolorbox}[title=Problem, colbacktitle=red!70!black,colback=red!20!white] + We don't have large systems at hand. + \end{tcolorbox} + \begin{tcolorbox}[title=Solution, colbacktitle=Green!70!black, colback=Green!20!white] \scriptsize - \textbf{Step 1.} Ensure Redis and PostgreSQL servers are up and alive.\newline - - \textbf{Step 2.} Run a Confluent Kafka setup: Kafka Connect, Schema Registry and a Kafka server.\newline - - \textbf{Step 3.} Start the Python HTTP Server, and the Python Redis Monitor.\newline - - \textbf{Step 4.} Run the (modified) OpenDC (physical twin) with example experiment.\newline - - \textbf{Step 5.} \emph{Sunfish} will automatically start a second OpenDC instance, and start the data analysis. + Use a second simulator \end{tcolorbox} \vspace{0.5cm} \end{minipage} - \hspace{0.35cm} + \hspace{0.25cm} \begin{minipage}[b]{0.45\linewidth} \vspace{-0.2cm} \begin{center} - \includegraphics[width=1.2\linewidth]{images/predictive_analyticsv2.pdf} + \includegraphics[width=1.2\linewidth]{images/predictive_analyticsv3.pdf} \end{center} \tiny - \vspace{-0.4cm} - \textbf{Figure 1.5:} We can't just go and test digital twins on large systems as large systems often aren't at hand. - Answering \textbf{RQ3} we provide a novel way to evaluate datacenter digital twins through discrete-event simulation instead. + \vspace{-0.2cm} + \textbf{Figure 1.5:} The experimental setup. + Answering \textbf{RQ3} we provide a novel way to evaluate datacenter digital twins through discrete-event simulation. \end{minipage} \end{frame} |