40m LDAS account

A shared LIGO Data Grid (LDG) account was created for use by the 40m lab. The purpose of this account is to provide access to the LSC computer cluster resources for 40m-specific projects that may benefit from increased computational power and are not linked to any user in particular (e.g. the summary pages).

Access

In order to access the cluster through the 40m account, you must first:

Obtain access to the LDG cluster using yout LIGO.org credentials using this form;
Have your account linked to the 40m shared account by emailing the LDAS admins.

The following LDAS users are already associated with the 40m account and may skip the above steps: rana.adhikari, koji.arai, craig.cahillane, tega.edo, max.isi, jameson.rollins.

Using grid tools

If you have installed and know how to use the LIGO grid tools, you can log into the 40m shared account by adding 40m@ to the server name and proceding as usual, e.g.:

gsissh 40m@ldas-pcdev6.ligo.caltech.edu

Ussing SSH

To access the account using the SSH Login Portal follow these steps (replacing albert.einstein with yout actual username):

Either a single-step login via

ssh -J albert.einstein@ssh.ligo.org 40m@ldas-pcdev6.ligo.caltech.edu

Or a multi-step login via

Open the SSH connection: ssh albert.einstein@ssh.ligo.org
Type in your password
You will be presented with several login options: choose Z to specify an alternative user account
Type 40m when prompted for the alternative user name
Choose the desired site from the server selection menu (e.g. to log to ldas-pcdev6.ligo.caltech.edu, type 2 for CIT and then g for ldas-pcdev6)

The whole process looks like the following:

bash-4.1$ ssh albert.einstein@ssh.ligo.org

*******************************************************************************
!!! Access to this system is limited to members of the LIGO community ONLY. !!!
*******************************************************************************

Please provide your LIGO Directory "albert.einstein" name and password.

albert.einstein@ssh.ligo.org's password: 
Your identity: albert.einstein@LIGO.ORG

Creating proxy .................................... Done
Your proxy is valid until: Jul 24 22:31:11 2015 GMT

::: LIGO Data Grid Login Menu :::

Select from these LDG sites:
 0. Logout
 1. AEI - Albert Einstein Institue, Hannover (Germany)
 2. CIT - California Institute of Technology, Pasadena, CA (USA)
 3. LHO - LIGO Hanford Observatory - Hanford, WA (USA)
 4. LLO - LIGO Livingston Observatory - Livingston, LA (USA)
 5. SYR - Syracuse University, Syracuse, NY (USA)
 6. UWM - Center for Gravitation, Cosmology & Astrophysics (Milwaukee, WI, USA)
 -------------------------------------------------------------
 Z. Specify alternative user account

Enter selection from the list above: Z


NOTE: Keep in mind that you will be logged in to the remote host using the
provided account name.  It is possible that the provided account name does not
exist on the remote host.  If so and the log in fails, please check with the
site admin.

Enter alternative user name or
press return to reset (current: albert.einstein): 40m 


::: LIGO Data Grid Login Menu (Alternative Name: 40m) :::

Select from these LDG sites:
 0. Logout
 1. AEI - Albert Einstein Institue, Hannover (Germany)
 2. CIT - California Institute of Technology, Pasadena, CA (USA)
 3. LHO - LIGO Hanford Observatory - Hanford, WA (USA)
 4. LLO - LIGO Livingston Observatory - Livingston, LA (USA)
 5. SYR - Syracuse University, Syracuse, NY (USA)
 6. UWM - Center for Gravitation, Cosmology & Astrophysics (Milwaukee, WI, USA)
 -------------------------------------------------------------
 Z. Specify alternative user account

Enter selection from the list above: 2


::: LIGO Data Grid Login Menu (Alternative Name: 40m) :::

Select from these LDG sites:
 0. Logout
 1. AEI - Albert Einstein Institue, Hannover (Germany)
 2. CIT - California Institute of Technology, Pasadena, CA (USA)
    a. ldas-grid    -  Primary production submit machine
    b. ldas-pcdev1  -  Very large memory devel & post-processing w/GPU
    c. ldas-pcdev2  -  Very large memory devel & post-processing w/GPU
    d. ldas-pcdev3  -  Large memory devel & post-processing w/Xeon-Phi
    e. ldas-pcdev4  -  Bleeding edge LIGO pre-release software
    f. ldas-pcdev5  -  Over-the-edge upstream pre-release software
    g. ldas-pcdev6  -  RHEL6 Over-the-edge upstream pre-release software
    h. ldas-pcdev7  -  SL6 VM for testing kernel checkpointing
    i. ldas-pcdev8  -  Scientific Linux 7.0
 3. LHO - LIGO Hanford Observatory - Hanford, WA (USA)
 4. LLO - LIGO Livingston Observatory - Livingston, LA (USA)
 5. SYR - Syracuse University, Syracuse, NY (USA)
 6. UWM - Center for Gravitation, Cosmology & Astrophysics (Milwaukee, WI, USA)
 -------------------------------------------------------------
 Z. Specify alternative user account

Enter selection from the list above: g

Certificates

SSH

The public and private keys corresponding to this account are stored in ~/.ssh. The public key has been added to nodus so that it is possible to SSH into the shared controls account without a password:

ssh controls@nodus.ligo.caltech.edu

Kerberos

If you need to access Kerberos-protected services from the account using the command line, you can just use your own credentials (i.e. kinit albert.einstein@LIGO.ORG). However, if you want to have background jobs access this, you probably want to make use of the keytabs stored in ~/.kerberos.

A different keytab is required for each server. So far, I have only requested a keytab to use from the ldas-pcdev1 CIT headnode: ~/.kerberos/40m.robot.ldas-pcdev1.ligo.caltech.edu. The associated Principal Name is: 40m/robot/ldas-pcdev1.ligo.caltech.edu@LIGO.ORG. More keytabs can be requested here.

Note: although we are supposed to obtain a different keytab for each headnode, in practice, the pcdev1 keytab seems to be accessible and usable from all headnodes.

Condor

Condor jobs can be submitted from this account as usual. The only thing to notice is that, on top of the usual tag, the submit file must include a line specifying who the actual user submitting the jobs is:

accounting_group_user = marie.curie

Also, at the moment of writing this, a bug in Condor makes the command condor_q 40m not work; if you run into this problem, add the -s option: condor_q -s 40m (or just do condor_q | grep 40m).