diff options
-rw-r--r-- | doc/client.tex | 34 | ||||
-rw-r--r-- | doc/repository.tex | 35 |
2 files changed, 69 insertions, 0 deletions
diff --git a/doc/client.tex b/doc/client.tex index e69de29bb..a9cf42062 100644 --- a/doc/client.tex +++ b/doc/client.tex @@ -0,0 +1,34 @@ +\documentclass[11pt]{article} + +\title{Bcfg2 Client Design} +\author{Narayan Desai \\ desai@mcs.anl.gov} + +\setlength{\oddsidemargin}{0in} +\setlength{\evensidemargin}{0in} +\setlength{\topmargin}{0.0in} +\setlength{\headheight}{0in} +\setlength{\headsep}{0.5in} +\setlength{\textwidth}{6.5in} +\setlength{\textheight}{8.5in} +\setlength{\parskip}{0.05in} + +\begin{document} +\maketitle + +\section{Overview} +The client model in BCFG2 remains much the same as the client model in +BCFG1. This assumptions in place are as follows: +\begin{itemize} +\item{BCFG is the source of all client configuration.} +\item{Skew from the configuration determined by BCFG is defined to be + incorrect.} +\item{Local state isn't trusted. All client metadata is determined on + the server side.} +\end{itemize} + +The client configuration consists of a complete software inventory, +extra filesystem modifications, and configuration file changes. The +client configuration will be augmented in BCFG2 to also include state +information about process profiles and normal usage. + +\end{document}
\ No newline at end of file diff --git a/doc/repository.tex b/doc/repository.tex index e69de29bb..2068d2432 100644 --- a/doc/repository.tex +++ b/doc/repository.tex @@ -0,0 +1,35 @@ +\documentclass[11pt]{article} + +\title{Bcfg2 Repository Design} +\author{Narayan Desai \\ desai@mcs.anl.gov} + +\setlength{\oddsidemargin}{0in} +\setlength{\evensidemargin}{0in} +\setlength{\topmargin}{0.0in} +\setlength{\headheight}{0in} +\setlength{\headsep}{0.5in} +\setlength{\textwidth}{6.5in} +\setlength{\textheight}{8.5in} +\setlength{\parskip}{0.05in} + +\begin{document} +\maketitle + +The BCFG repository is the storage depot for all components of client +configurations. In BCFG1, this depot was composed of several SQL +database tables and a filesystem hierarchy, composed of several types +of data. + +One of the high-level features desired from BCFG from the start was +the ability for configuration changes, acquired through some automated +mechanism, to be correctly installed into the configuration +repository. While using this ad-hoc repository, the underlying +structure of data made automatic inclusion of new configuration +fragments difficult. To address this problem, we have redesigned the +repository to allow better data access and update semantics. + +\section{Why is an ad-hoc repository problematic?'} + +\section{Design} + +\end{document}
\ No newline at end of file |