DIET's extensions configuration flags

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_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_ALT_BATCH enables the transparent submission to batch servers. See Chapter 6 for more details.

• DIET_USE_WORKFLOW enables the support of workflow. For the support of workflows inside DIET, Xerces and Xqilla libraries are mandatory (see http://xerces.apache.org/xerces-c/ and http://xqilla.sourceforge.net/HomePage). For more details about the workflow support in DIET see Chapter 15.

• 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.

• DIET_WITH_STATISTICS enables the generation of statistics logs. The logs can be obtained for any element in the DIET hierarchy. To do so, you have to define the DIET_STAT_FILE_NAME environment variable. For instance :
  
  export DIET_STAT_FILE_NAME=/tmp/client
  then calling a client will generate the statistics for the client in the /tmp/client file.

• DIET_USE_USERSCHED allows using custom plugin schedulers at the DIET agents level. See chapter 9.

• DIET_USE_SECURITY enables ssl communications between DIET entities (agents, SeDs and clients). This extension uses the SSL part of OmniORB, so you need the library omnisslTP to be installed. In order to do that OmniORB should be compiled on an environment where OpenSSL is available. Please refer to the OmniORB doc if necessary^2.2. To run DIET with security on, keys and certificates will be specified in the configuration files of each entities (see Appendix A page )