DIET has many extensions (some of them are still) experimental. These extensions most often rely on external packages that need to be pre-installed. One should notice that some of those extensions offer concurrent functionalities. This explains the usage of configuration flags in order to obtain the compilation of the desired extensions.
DIET_USE_ALT_BATCH enables the transparent submission to batch servers. See Chapter 6 for more details.
DIET_BUILD_BLAS_EXAMPLES option activates the compilation of
the BLAS based DIET examples, as a sub-module of examples.
The BLAS 2.1 (Basic Linear
Algebra Subprograms) are high quality ``building block'' routines for
performing basic vector and matrix operations.
Level 1 BLAS do vector-vector operations, Level 2 BLAS do matrix-vector
operations, and Level 3 BLAS do matrix-matrix operations.
Because the BLAS are efficient, portable, and widely available,
they're commonly used in the development of high quality linear algebra
software.
DIET uses BLAS to build demonstration examples of client/server.
Note that the option DIET_BUILD_BLAS_EXAMPLES can only be
effective when DIET_BUILD_EXAMPLES is enabled.
DIET_BUILD_BLAS_EXAMPLES is disabled by default.
DIET_USE_CORI CoRI, which stands for COllector of Resource
Information, provides a framework for probing hardware and performance
information about the SeD.
CoRI also yields a very basic set of probing resources which are
heavily dependent on the system calls available for the considered platform.
When this option is activated (disabled by default), the user can either
define new collectors or use existing collectors (like FAST, see the
DIET_USE_FAST option) through CoRI's interface.
CoRI thus provides a possible tactical approach for tuning the performance
of your favorite plug-in scheduler.
Chapter 8 describes in more details CoRI and its
possible usage within DIET.
DIET_USE_FAST activates DIET support of FAST (refer to
http://www.loria.fr/~quinson/fast.html a grid aware dynamic
forecasting library.
Although the detection of FAST should be correctly handled by cmake
(since detection is based on the FAST provided fast-config utility)
the installation of FAST can be a lengthy process (and, depending on your
platform, potentially quite difficult).
This is due to the dependency of FAST towards numerous sub-libraries on
which it relies (GSL, BDB, NWS, LDAP).
Thus, the activation of this option can only be recommended for advanced
users...
As already mentioned, on activation of the DIET_USE_FAST option
cmake will search among the well known system path for the
fast-config command and set the FAST_CONFIG_EXECUTABLE
with the result. Upon failure, it is up to the user to manually set the
full path name to this command (e.g. with [c]cmake command line argument
-DFAST_CONFIG_EXECUTABLE:PATH=$HOME/local/bin/fast-config.
DIET_USE_FD for activating Fault Detector.
DIET_USE_JUXMEM activates DIET support of JuxMem which allows
the user to manage persistent data.
When this option is activated (disabled by default), a SeD can store
data blocks within JuxMem.
Chapter 13 describes in more details JuxMem and its use
inside DIET.
DIET_USE_JXTA activates the so called MULTI-Master-Agent
support.
This option is which is based on the JXTA layer (refer to
http://www.jxta.org/) allows the user to deploy DIET_JXTA
architectures.
Note that this is to be opposed with
DIET_WITH_MULTI_MA (see 2.2.5 below)
which offers similar functionalities but based on CORBA.
DIET_WITH_MULTI_MA activates the so called MULTI Master Agent
support which allows the user to connect several MA for them to
act as bounded.
When this option is activated, such a bounded MA is allowed to search
for a SeD into the MA hierarchies it is connected to.
Note that MULTI-Master-Agent support is based on the CORBA layer
which is to be opposed with DIET_USE_JXTA which offers similar
functionalities but based on JXTA.
DIET_USE_WORKFLOW enables the support of workflow.
DIET_WITH_STATISTICS enables the generation of statistics logs