Basic information

Information

Inula cluster users can use multiple queues depending on the type of task to be executed and project association. The following list presents all available queues on Inula cluster.

Queues

Queues are grouped as follows:

• glite - for VO ops and VO dteam purposes
• plgrid - for PL-GRID project -> https://docs.plgrid.pl/pages/viewpage.action?pageId=4260885

• local - for local users
• special - special purpose (routing, infrastructure management)

General info

Modules are the standard methods used to manage the user environment for clusters (e.g. Inula). Oprate approach on modules means that the user does not need to specify paths for different versions of applications and take care of setting the dependent environment variables. It is enough for the user to 'load' module associated with a given application to set all required environment variables (PATH, LD_LIBRARY_PATH INCLUDE etc.) accordingly. If the user wants to use a different version of the application, one has to unload the current-in-use module and load the module associated with the new version.

Usage

Listing loaded modules

To list loaded modules please use the following command.

module list

Exemplary result may look similar to:

[username@hostname ~]$ module list
Currently Loaded Modulefiles:
  1) open64-4.2.5.2

Listing available modules

To list modules available for given user please use the following command:

module avail

Exemplary result may look similar to:

[username@hostname ~]$ module avail

----------- /usr/share/Modules/PSNC/Development/Languages -----------
open64-4.2.5.2

----------- /usr/share/Modules/PSNC/Development/Libraries -----------
openmpi-gcc-x86_64    openmpi-opencc-x86_64

Listing additional information about module

Additional info about the module can be obtained by executing the command:

module help <module_name>

Exemplary execution for module named 'open64-4.2.5.2':

[username@hostname ~]$ module help open64-4.2.5.2

----------- Module Specific Help for 'open64-4.2.5.2' ---------------------------

	Name:			AMD x86 Open64 Compiler Suite
	Version:		4.2.5.2
	Platform:		x86_64
	Category:		Development/Languages
	URL				http://developer.amd.com
	Provides:		opencc, openCC, openf90, openf95

	Description:

	The x86 Open64 compiler system is a high performance, production
	quality code generation tool designed for high performance parallel
	computing workloads. The x86 Open64 environment provides the developer
	the essential choices when building and optimizing C, C++, and Fortran
	applications targeting 32-bit and 64-bit Linux platforms.

	The x86 Open64 compiler system offers a high level of advanced
	optimizations, multi-threading, and processor support that includes
	global optimization, vectorization, interprocedural analysis, feedback
	directed optimizations, loop transformations, and code generation
	which extracts the optimal performance from each x86 processor core.

	man pages:		no
	Restrictions:	none

-------------------------------------------------------------------------------

Loading module

module load <module_name>

Unloading module

module unload <module_name>

Checking for environment variables modified by given module

module show <module_name>

Exemplary result may look similar to:

[username@hostname ~]$ module show open64-4.2.5.2
-------------------------------------------------------------------
/usr/share/Modules/PSNC/Development/Languages/open64-4.2.5.2:

module-whatis	AMD x86 Open64 Compiler Suite, 4.2.5.2 
setenv			open64_root /opt/x86_open64-4.2.5.2 
prepend-path	PATH /opt/x86_open64-4.2.5.2/bin 
prepend-path	LD_LIBRARY_PATH /opt/x86_open64-4.2.5.2/lib 
prepend-path	INCLUDE /opt/x86_open64-4.2.5.2/include 
-------------------------------------------------------------------

Settings customization

In the environment using modules user can decide which modules will be loaded when logging into the system. To do this, one has to edit the file ~ / .bashrc or ~ / .bash_profile and add the appropriate lines. Below is an example in which a variable ModulePath has been added to the directory, which contains the user module and the module open64 compiler in version 4.2.5.2 is loaded.

[username@hostname ~]$ cat ~/.bash_profile 
...
# Environment Modules

# Prepend directory to the MODULEPATH environment variable.
module use --append $HOME/.modules/my_modules

# Modules loaded at login time.
module load open64-4.2.5.2
...

Additional info

Additional info can be obtained by typing one of the following commands.

# Information on modules usage
man module

# Information on writing user modules
man modulefile

Listing tasks

squeue --long

Presenting given job status and other info

scontrol show job <job_id>