Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @

NGI CZ:DIRAC for Auger

From EGIWiki
Jump to navigation Jump to search

DIRAC for Auger

We have chosen DIRAC interware as a base underlying software for distributed computing.

Client Installation

Users can install DIRAC client on their local computer. First, they must be registered on the DIRAC portal. Contact me ( if you want to be registered. Instructions for client installation are on DIRAC web site

The VO auger specific installation instructions: Create or choose a directory where you want to install the DIRAC software and set it as the current working directory (e.g. mkdir ~/dirac; cd dirac). Download it, change permissions and run it with teh strinng "auger" as a parameter:

wget -np -O dirac-install --no-check-certificate
chmod +x dirac-install
./dirac-install -V auger
source bashrc

The next step is to configure the client. You need a valid X509 certificate in a standard place (~/.globus directory)

dirac-proxy-init -x
dirac-configure defaults-auger.cfg

Now you can initialize your proxy with auger group and test it:

dirac-proxy-init -g auger_user -M 
dls /

You should get:


Another possibility suitable mostly for test job submission, job monitoring and accounting is to connect to the France Grille DIRAC web server.

Command line interface is also available on Example how to start a session:

# initialisation
source /home/chudoba/dirac/bashrc
dirac-proxy-init -g auger_user -M 

Basic Examples

Initialize the environment and certificate proxy. Then:

# job submission
dirac-wms-job-submit auger_basic_test_cesnet.jdl 
JobID = 29086015

# job status query
dirac-wms-job-status 29086015
JobID=29086015 Status=Done; MinorStatus=Execution Complete;;

# output download
dirac-wms-job-get-output -D out 29086015

The JDL file is simillar to gLite JDL files. Only syntax to specify a concrete site via requirements is different. An example for the CESNET site

[chudoba@ui1 dirac]$ cat auger_basic_test_cesnet.jdl
Executable = "/bin/sh";
StdOutput = "auger_basic_test.out";
StdError = "auger_basic_test.err";
InputSandbox = {""};
OutputSandbox = {"auger_basic_test.err","auger_basic_test.out"};
RetryCount = 3;
VirtualOrganisation = "auger";
Arguments = " 1";

Site = {};

For DIRAC Admins

User registration

Since April 2018 users are automatically propagated to DIRAC server from the VOMS server. The nickname field in the VOMS is used for user names. There were several cases when a user has more than one certificate registered in Perun. This creates two or more "users" in the VOMS server with the same nickname. The export procedure to DIRAC server can map correctly these multiple entries to a single user according the nickname. However we encourage users to remove obsolete certificates from Perun.

Obsolete since April 2018:

Each user must be added (registered) to the DIRAC portal. The command must be issued by user with dirac_admin role. Example:

# get dirac admin role
dirac-proxy-init -g dirac_admin -M
# add a user
dirac-admin-add-user -N grubio -D /DC=es/DC=irisgrid/O=ugr/CN=gines.rubio -M -G auger_user

Other possibility is to use the web interface: Applications, Registry Manager, Users. One must have a role dirac_admin. Do not forget to add the new user to the group auger_user (separate step).

Note: the long version of options for user registration did not work (16 march 2015):

dirac-admin-add-user --UserName grubio --UserDN /DC=es/DC=irisgrid/O=ugr/CN=gines.rubio --UserMail --UserGroup auger_user