| ... | ... | @@ -4,14 +4,14 @@ EAR requires some third party libraries and headers to compile and run, in addit |
|
|
|
|
|
|
|
| Library | Minimum version | References |
|
|
|
|
| ----------- | --------------- | ----------------------------------------- |
|
|
|
|
| PAPI | 5.4.0 | [Website](http://icl.utk.edu/papi/) |
|
|
|
|
| GSL | 1.4 | [Website](https://www.gnu.org/software/gsl/) |
|
|
|
|
| SLURM | 17.02.6 | [Website](https://slurm.schedmd.com/) |
|
|
|
|
| MPI | - | - |
|
|
|
|
| MySQL* | 15.1 | [MySQL](https://mysql.com) or [MariaDB](https://mariadb.org/) |
|
|
|
|
| PostgreSQL* | 9.2 | [PostgreSQL](https://www.postgresql.org/) |
|
|
|
|
| CUDA** | 7.5 | [CUDA](https://mysql.com) or [MariaDB](https://mariadb.org/) |
|
|
|
|
| Autoconf | 2.69 | [Website](https://www.gnu.org/software/autoconf/autoconf.html) |
|
|
|
|
| GSL | 1.4 | [Website](https://www.gnu.org/software/gsl/) |
|
|
|
|
|
|
|
|
|
|
|
|
\* Just one of them required.
|
|
|
|
\** Required if you want to monitor GPU data.
|
| ... | ... | @@ -23,7 +23,7 @@ Also, some **drivers** has to be present and loaded in the system: |
|
|
|
| CPUFreq | kernel/drivers/cpufreq/acpi-cpufreq.ko | 3.10 | [Information](https://wiki.archlinux.org/index.php/CPU_frequency_scaling) |
|
|
|
|
| Open IPMI | kernel/drivers/char/ipmi/*.ko | 3.10 | [Information](https://docs.oracle.com/en/database/oracle/oracle-database/12.2/cwlin/configuring-the-open-ipmi-driver.html) |
|
|
|
|
|
|
|
|
Lastly, the **compilers**: EAR uses C compiler compilers. It has been tested with both Intel and GNU.
|
|
|
|
Lastly, the **compilers**: EAR uses C compilers. It has been tested with both Intel and GNU.
|
|
|
|
|
|
|
|
| Compiler | Comment | Minimum version | References |
|
|
|
|
| --------------------------------- | -------------------------- | --------------- | --------------- |
|
| ... | ... | @@ -34,7 +34,7 @@ Compilation and installation guide summary |
|
|
|
------------------------------------------
|
|
|
|
1. Before the installation, make sure the installation path is accessible by all the computing nodes. Do the same in the folder where you want to set the configuration files (it will be called `$(EAR_ETC)` in this guide for simplicity).
|
|
|
|
2. Generate Autoconf's `configure` program by typing `autoreconf -i`.
|
|
|
|
3. Read the sections below to understand how to properly set the `configure` parameters.
|
|
|
|
3. Read sections below to understand how to properly set the `configure` parameters.
|
|
|
|
4. Compile EAR components by typing `./configure ...`, `make` and `make install` in the root directory.
|
|
|
|
5. Type `make etc.install` to install the content of `$(EAR_ETC)`. It is the configuration content, but that configuration will be expanded in the next section. You have a link at the bottom of this page.
|
|
|
|
|
| ... | ... | @@ -55,7 +55,7 @@ Configure options |
|
|
|
| EAR_ETC | Defines the read-only single-machine data as 'etc' (default: EPREFIX/etc) (you can also use --sharedstatedir=DIR). |
|
|
|
|
| MAN | Defines the manual directory (default: PREFIX/man) (you can use also --mandir=DIR). |
|
|
|
|
| DOC | Defines the documentation directory (default: PREFIX/doc) (you can use also --docdir=DIR). |
|
|
|
|
| MPI_VERSION | Adds a suffix to the compiled EAR library name. Read on for more information. |
|
|
|
|
| MPI_VERSION | Adds a suffix to the compiled EAR library name. Read further down this page for more information. |
|
|
|
|
| USER | Owner user of the installed files. |
|
|
|
|
| GROUP | Owned group of the installed files |
|
|
|
|
|
| ... | ... | @@ -73,24 +73,24 @@ You can choose the root folder by typing `./configure --PREFIX=<path>`. But ther |
|
|
|
You have more installation options information by typing `./configure --help`. If you want to change the value of any of this options after the configuration process, you can edit the root Makefile. All the options are at the top of the text and its names are self-explanatory.
|
|
|
|
|
|
|
|
##### Adding required libraries installed in custom locations
|
|
|
|
The `configure` script is capable to find libraries located in custom location if a module is loaded in the environment or its path is included in `LD_LIBRARY_PATH`. If not, you can help `configure` to find PAPI, SLURM, or other required libraries in case you installed in a custom location. It is necessary to add its root path for the compiler to see include headers and libraries for the linker. You can do this by adding to it the following arguments:
|
|
|
|
The `configure` script is capable to find libraries located in custom location if a module is loaded in the environment or its path is included in `LD_LIBRARY_PATH`. If not, you can help `configure` to find SLURM, or other required libraries in case you installed in a custom location. It is necessary to add its root path for the compiler to see include headers and libraries for the linker. You can do this by adding to it the following arguments:
|
|
|
|
|
|
|
|
| Argument | Description |
|
|
|
|
| ------------------------ | -------------------------------------------------------------------------- |
|
|
|
|
| --with-papi=\<path\> | Specifies the path to PAPI installation. |
|
|
|
|
| --with-gsl=\<path\> | Specifies the path to GSL installation. |
|
|
|
|
| --with-slurm=\<path\> | Specifies the path to SLURM installation. |
|
|
|
|
| --with-cuda=\<path\> | Specifies the path to CUDA installation. |
|
|
|
|
| --with-mysql=\<path\> | Specify path to MySQL installation. |
|
|
|
|
| --with-pgsql=\<path\> | Specify path to PostgreSQL installation. |
|
|
|
|
| --with-gsl=\<path\> | Specifies the path to GSL installation. |
|
|
|
|
|
|
|
|
|
|
|
|
* This is an example of ‘CC‘ overwriting and PAPI path specification:<br />
|
|
|
|
`./configure --with-papi=/path/to/PAPI`
|
|
|
|
* This is an example of `CC` overwriting the CUDA path specification:<br />
|
|
|
|
`./configure --with-cuda=/path/to/CUDA`
|
|
|
|
|
|
|
|
If unusual procedures must be done to compile the package, please try to figure out how `configure` could check whether to do them and contact the team to be considered for the next release. In the meantime, you can overwrite shell variables or export its paths to the environment (e.g. LD_LIBRARY).
|
|
|
|
|
|
|
|
##### Additional configure flags
|
|
|
|
Also, there are additional flags to help administrator increase the compatibility of EAR in the nodes.
|
|
|
|
Also, there are additional flags to help administrator increase the compatibility of EAR in nodes.
|
|
|
|
|
|
|
|
| Argument | Description |
|
|
|
|
| ---------------- | ------------------------------------------------------------------------------ |
|
| ... | ... | @@ -102,11 +102,11 @@ Pre-installation fast tweaks |
|
|
|
----------------------------
|
|
|
|
Some EAR characteristics can be modified by changing the value of the constants defined in `src/common/config/config_def.h`. You can open it with an editor and modify those pre-procesor variables to alter the EAR behaviour.
|
|
|
|
|
|
|
|
Also, you can quickly switch the user/group of your installation files by modifying the `CHOWN_USR/CHOWN_GRP` variables the root Makefile.
|
|
|
|
Also, you can quickly switch the user/group of your installation files by modifying the `CHOWN_USR/CHOWN_GRP` variables in the root Makefile.
|
|
|
|
|
|
|
|
Library distributions/versions
|
|
|
|
------------------------------
|
|
|
|
As commented in the overview, the EAR library is loaded next to the user MPI application by the [EAR Loader](EARLO). The library uses MPI symbols, so it is compiled by using the includes provided by your MPI distribution. The selection of the library version is automatic in runtime, but in the compiling and installation process is not. Each compiled library has its own file name that has to be defined by the `MPI_VERSION` variable during `./configure` or by editing the root Makefile. The name list per distribution is exposed in the following table:
|
|
|
|
As commented in the overview, the EAR library is loaded next to the user MPI application by the [EAR Loader](EARLO). The library uses MPI symbols, so it is compiled by using the includes provided by your MPI distribution. The selection of the library version is automatic in runtime, but in the compiling and installation process is not required. Each compiled library has its own file name that has to be defined by the `MPI_VERSION` variable during `./configure` or by editing the root Makefile. The name list per distribution is exposed in the following table:
|
|
|
|
|
|
|
|
| Distribution | Name | MPI_VERSION variable |
|
|
|
|
| ---------------- | ------------------- | -------------------- |
|
| ... | ... | @@ -116,7 +116,7 @@ As commented in the overview, the EAR library is loaded next to the user MPI app |
|
|
|
|
|
|
|
If different MPI distributions shares the same library name, it means that its symbols are compatible between them, so compiling and installing the library one time will be enough. However, if you provide different MPI distributions to the users, you will have to compile and install the library multiple times.
|
|
|
|
|
|
|
|
Before compiling new libraries you have to install by `make install`. Then you can run the `./configure` again, changing the `MPICC`, `MPICC_FLAGS` and `MPI_VERSION` variables, or just opening the root `Makefile` and edit the same variables and `MPI_BASE`, which just sets the MPI installation root path. Now type `make full` to perform a clean compilation and `make earl.install`, to install only the new version of the library.
|
|
|
|
Before compiling new libraries you have to install by typing `make install`. Then you can run the `./configure` again, changing the `MPICC`, `MPICC_FLAGS` and `MPI_VERSION` variables, or just opening the root `Makefile` and edit the same variables and `MPI_BASE`, which just sets the MPI installation root path. Now type `make full` to perform a clean compilation and `make earl.install`, to install only the new version of the library.
|
|
|
|
|
|
|
|
If your MPI version is not fully compatible, please contact ear-support@bsc.es. We will add compatibility to EAR and give you a solution in the meantime.
|
|
|
|
|
| ... | ... | @@ -142,7 +142,11 @@ This is the list of the inner installation folders and their content: |
|
|
|
| \<*EAR_ETC*\> | /slurm | ear.plugstack.conf. |
|
|
|
|
| \<*EAR_ETC*\> | /systemd | EAR service files. |
|
|
|
|
|
|
|
|
Fine grain tuning of EAR options
|
|
|
|
---------------------------------
|
|
|
|
Some options such as the maximum number of CPUs or GPUs supported are defined in src/common/config files. It is not recommended to modify these files but some options and default values can be set by modifying them.
|
|
|
|
|
|
|
|
Next step
|
|
|
|
---------
|
|
|
|
For a better overview of the installation process, return to our [Quick installation guide](Admin-guide#quick-installation-guide).
|
|
|
|
To continue the installation, visit the [configuration page](Configuration) to set up properly the EAR configuration file and the SLURMs plugin stack file. |
|
|
|
To continue the installation, visit the [configuration page](Configuration) to set up properly the EAR configuration file and the SLURMs plugin stack file. |
|
|
\ No newline at end of file |
