Project

General

Profile

Using NOvASoft on the GPVM nodes » History » Version 9

Gavin Davies, 06/08/2011 04:55 PM

1 1 Brian Rebel
{{toc}}
2 1 Brian Rebel
3 1 Brian Rebel
h1. Using NOvASoft on the GPVM nodes
4 1 Brian Rebel
5 1 Brian Rebel
h2. Available nodes
6 1 Brian Rebel
7 1 Brian Rebel
The new GPVM nodes are virtual machines that are accessible by the intensity frontier experiments.  The list of nodes for NOvA is
8 1 Brian Rebel
9 8 Gavin Davies
<pre>
10 2 Brian Rebel
*nova01.fnal.gov
11 2 Brian Rebel
*nova02.fnal.gov
12 2 Brian Rebel
*nova03.fnal.gov
13 2 Brian Rebel
*nova04.fnal.gov
14 1 Brian Rebel
*nova05.fnal.gov
15 8 Gavin Davies
</pre>
16 1 Brian Rebel
These nodes will give us access to the FermiGrid.
17 1 Brian Rebel
18 1 Brian Rebel
If you have just received notification that you have an account on one of these machines, your login shell is likely bash.  If you prefer a different login shell you need to submit a ServiceDesk ticket to get it changed.
19 1 Brian Rebel
20 6 Mayly Sanchez
h2. Kerberos
21 1 Brian Rebel
22 6 Mayly Sanchez
Users must have a valid kerberos ticket to access Fermilab computing at the time an attempt to log into a Fermilab machine. The ticket is obtained by executing the following command at a terminal prompt:
23 8 Gavin Davies
<pre>
24 6 Mayly Sanchez
$ kinit principal @FNAL.GOV
25 8 Gavin Davies
</pre>
26 8 Gavin Davies
where principal is the user's kerberos principal. If a user is attempting to access the repository from a non-Fermilab machine, the following lines must be in the users' .ssh/config:
27 8 Gavin Davies
<pre>
28 6 Mayly Sanchez
Host *.fnal.gov
29 6 Mayly Sanchez
ForwardAgent yes
30 6 Mayly Sanchez
ForwardX11 yes
31 6 Mayly Sanchez
ForwardX11Trusted yes
32 6 Mayly Sanchez
GSSAPIAuthentication yes
33 6 Mayly Sanchez
GSSAPIDelegateCredentials yes
34 8 Gavin Davies
</pre>
35 6 Mayly Sanchez
In case of trouble when connecting via ssh (permission denied error) the reason can be in the OpenSSH client, the following client is compatible with Fermilab Kerberos authentification:
36 6 Mayly Sanchez
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008 
37 6 Mayly Sanchez
38 1 Brian Rebel
h2. Setting up NOvASoft
39 1 Brian Rebel
40 7 Mayly Sanchez
There is a setup script provided to get the environment ready for using NOvASoft on these machines.  To use it, one does (for tags S11.04.30 and later including development): 
41 8 Gavin Davies
<pre>
42 9 Gavin Davies
$ source /grid/fermiapp/nova/novaart/novasoft/setup/setup_novasoft_nusoft.(c)sh
43 8 Gavin Davies
</pre>
44 7 Mayly Sanchez
If you are using tagged release S11.04.09 and earlier do: 
45 7 Mayly Sanchez
46 1 Brian Rebel
@$source /grid/fermiapp/nova/novaart/novasoft/releases/development/setup/setup_novasoft_ifcluster.(c)sh@
47 3 Brian Rebel
48 7 Mayly Sanchez
The above commands will set your $PATH and $LD_LIBRARY_PATH variables as well as the variables that define the locations of the necessary external packages.
49 1 Brian Rebel
50 2 Brian Rebel
While the public release of the code is located in /grid/fermiapp/nova/novaart/novasoft/releases/development/, the average user should _never_ make any files in that directory.  It has limited space and is only for code releases.  Instead, use the disk space described in the next section.
51 1 Brian Rebel
52 1 Brian Rebel
h2. Disk Space
53 1 Brian Rebel
54 1 Brian Rebel
The user space for those logging into these nodes is 
55 8 Gavin Davies
<pre>
56 8 Gavin Davies
/nova/app/users
57 8 Gavin Davies
</pre>
58 1 Brian Rebel
This is where users should store their test releases as well as any analysis files.
59 1 Brian Rebel
60 1 Brian Rebel
Any data or Monte Carlo files for general consumption by the experiment should be stored in 
61 8 Gavin Davies
<pre>
62 8 Gavin Davies
/nova/data
63 8 Gavin Davies
</pre>
64 1 Brian Rebel
When operating on the grid, the /data directories cannot have executables run from them, executables can only be run from the /app directories.