summaryrefslogtreecommitdiff
path: root/content/design.tex
diff options
context:
space:
mode:
authormjkwiatkowski <mati.rewa@gmail.com>2026-07-10 21:41:05 +0200
committermjkwiatkowski <mati.rewa@gmail.com>2026-07-10 21:41:05 +0200
commitb6202a785ce486531826d23999971712c512c785 (patch)
tree346cc89f739dfa13e16a45bb2ec040512a36a4a4 /content/design.tex
parentefed2f678137467b6d317c61b88494979ed49109 (diff)
feat: changed the TOC and added the preamble
Diffstat (limited to 'content/design.tex')
-rw-r--r--content/design.tex9
1 files changed, 5 insertions, 4 deletions
diff --git a/content/design.tex b/content/design.tex
index 3d53637..48d6ffd 100644
--- a/content/design.tex
+++ b/content/design.tex
@@ -1,4 +1,6 @@
-\chapter{Design}\label{s:design}
+% Changed chapter name, as suggested by Alexandru
+\chapter{Design of \mysystem, a Digital Twin For Predictive Analysis of Datacenters}\label{s:design}
+\section{Overview}\label{ss:design_overview}
\begin{mynote}
Our contribution in this chapter is three-fold:
\vspace{-0.2cm}
@@ -123,7 +125,7 @@ In addition to the functional requirements, we also present non-functional requi
\label{fig:reference_architecture}
\end{figure}
-\section{Design of \emph{Sunfish}}\label{ss:design_of_mysystem}
+\section{Overview of \mysystem Architecture}\label{ss:design_of_mysystem}
As a result of the \emph{AtLarge Design Process}~\cite{DBLP:conf/icdcs/IosupVTETBFMT19} designed a reference architecture for a predictive datacenter digital twin.
\Cref{fig:reference_architecture} encompasses 4 main elements:
\begin{enumerate*}[label=(\Roman*)]
@@ -195,6 +197,7 @@ Any discrepancies are communicated to the Analytics Engine (\myCircled{4b}) for
\caption{The detailed view of the Message Broker (\myCircled{2b}) from \Cref{fig:reference_architecture}.}
\label{fig:message_broker}
\end{figure}
+\section{The Digital Thread and Predictive Analytics}\label{ss:detailed_design}
\subsection{Message Broker}\label{sss:message_broker}
The Message Broker (\myCircled{2b}) is a component is slightly more complex, and necessities a separate diagram.
In \Cref{fig:message_broker} we present the composite elements that make up the Message Broker.
@@ -205,6 +208,4 @@ In the reference architecture, the consumers would constitute the Database (\myC
What is remarkable about the connector manager is the ability to swiftly connect more consumers to the system.
This way, the predictive digital twin can facilitate multiple different types of analytics engines or techniques.
Additionally, the setup is \Cref{fig:message_broker} is currently standard industry practice for large software deployments.
-
\section{Discussion}\label{ss:design_discussion}
-