TeraGrid.org Parent Organization Links

TeraGrid FAQ

How to access Purdue TG resources

There are two ways of accessing Purdue TeraGrid systems:

  • Authenticate using Grid credentials supplied by a TeraGrid approved Certificate Authority: Send your DN to help@teragrid.org and login using gsissh and certificates.
    • X.509 Certificates: Information about certificate use on the TeraGrid may be found here
  • Using SSH v2 public/private keys:  
    • SSH v2 public/private keys through TeraGrid Portal: First create an OpenSSH compatible key-pair, if you do not already have one. Procedures for creating SSH v2 public/private keys vary depending on your normal SSH client and operating environment (e.g. PuTTY, SecureCRT, or F-Secure SSH on Windows, ssh-keygen on UNIX, Linux, or Mac OS X). In any event, you should create an SSH version 2 public/private key pair that is compatible with OpenSSH and has a robust passphrase. To use your public key you must then transfer it (usually the 'Identity.pub' created by the keygen program). It is recommended that you then do the following to copy the public key to the ~/.ssh directory on the host. 
      • Login to the TeraGrid Portal (https://portal.teragrid.org/gridsphere/gridsphere) using the login you got in the introductory package, and your password.

      • Click 'My TeraGrid' -> 'Accounts' in the top menu.

      • Login to tg-steele with the Portal applet (gsissh)

      • Create a directory .ssh and change permissions to 600 (mkdir .ssh, chmod 600 .ssh)

      • Change to directory .ssh and create/open file identity.pub (cat > identity.pub)

      • On your local machine, use Notepad.exe or similar to open your Identity.pub file, that was created with the keygen program.

      • With the Identity.pub file opened in the Notepad application, open the Edit menu and choose Select All. Once everything is selected, open the Edit menu again and select Copy.

      • On the remote machine, click on the SecureCRT paste button, to paste the contents of the Clipboard, containing the contents of your Identity.pub file.

      • Issue a CTRL+D to close the Identity.pub file.

      • Convert the key to OpenSSH compatible with this command: ssh-keygen -i -f ~/.ssh/identity.pub >> ~/.ssh/authorized_keys or (OpenSSH < v.2.9) ssh-keygen -X -f ~/.ssh/identity.pub >> ~/.ssh/authorized_keys2

      • Change the permissions on the keyfile to only user: chmod 600 ~/.ssh/authorized_keys

    If you have any problems following the above steps, or if you can not log on after following these steps, contact the TeraGrid Helpdesk.

How to access Purdue TG Condor Pool

Once your account is enabled you can submit jobs via Condor-G to tg-condor.purdue.teragrid.org/jobmanager-condor or simply login to tg-login.purdue.teragrid.org and use condor_submit.

You must define the ClassAd TGProject in your submit file so that your usage can be matched with your Teragrid allocation.

 

+TGProject = "your project number"

 

Failing to include this ClassAd will prevent Condor from running your job!

For remote submissions, use the "project" RSL attribute for your Project number:

 

globus-job-run tg-gatekeeper.purdue.teragrid.org/jobmanager-condor -x '&(project=TG-XYZ12345)' /bin/hostname 

 

With Condor-G, use the "globusrl" expression in your submit file:

 

globusrsl = (project=TG-XYZ12345)

 

If your condor job requires CTSS, add the following Requirements ClassAd:

 

Requirements = (HasCTSS =?= True)

 

This will ensure that only a node with CTSS available to it will be chosen to run your job. If your job requires outbound internet connectivity (ie, outside of purdue.edu):

 

Requirements = (CanReachInternet == True)

 

If your job requires a different architecture (i.e. Windows):

 

Requirements = ( Arch=="Intel") && ( OpSys=="WINNT51" ) Requirements = ( Arch=="IA64") && ( OpSys=="LINUX" ) or Requirements = ( Arch=="SUN4U") && ( OpSys=="SOLARIS" )

 

You can add arbitrary condor ClassAds to your Condor-G globusrsl. The following example will request a node that has CTSS installed, and outbound internet connectivity:

 

globusrsl = (condorsubmit=(Requirements 'HasCTSS == TRUE && CanReachInternet ==TRUE') )

 

TeraDRE Webstart

TeraDRE has made a significant leap in usability with the addition of WebStart job submission. You can get started using web submission from the official TeraDRE homepage http://teradre.rcac.purdue.edu TeraDRE WebStart currently supports Maya, POVray, Blender, & Gelato. Other software packages are in the works. In addition, TeraDRE will soon be released as open source to further aid development in the graphics community.

I am running in the Vanilla universe. Why do my long jobs never finish?

You should run long jobs in the Standard Universe, otherwise it will continue to be stopped and restarted (from scratch) and never finish.

Another option is to develop some application-level checkpointing capability in your jobs.

How do I determine which machines is out there in the Purdue Condor Pool?

A very useful program for finding out which machines and architectures are out there, is the program condor_all. It should be noted, that even though it is located in the "official" Condor directory - /opt/condor/bin, it is a locally (Purdue) developed tool. It is very handy for finding out how many of a certain machine architecture that are available. This is very useful for the submit description file.

Another useful command to see how many machines is there, and how many are available, is condor_pool. Example:

 

 

-bash-3.00$ condor_pool -t
POOL
-------
egret.rcac.purdue.edu (Total=590,Unused=20)
broker.ics.purdue.edu (Total=619,Unused=65)
condor.calumet.purdue.edu (Total=348,Unused=347)
emu.rcac.purdue.edu (Total=2127,Unused=118)
flamingo.rcac.purdue.edu (Total=2256,Unused=613)


 

How do I check on the progress of a job?

Use the command condor_q.

Tracking down Globus errors.

You can run various Globus tests to narrow the possible error down, and determine if it is something in the connection which is wrong, rather than your script. Look here for some example tests:
http://wwwdev.rcac.purdue.edu/userinfo/howtos/teragrid/howto_teragrid.cfm#testing

How do I get a Purdue Certificate?

First, note that this is only for Purdue Affiliates!

Second, this step is not really necessary, since you just need a certificate from one of the TeraGrid sites and you can generate one yourself from NCSA when you have gotten your TeraGrid account.

To get a Purdue certificate you must show up in person and speak with Matthew Lundmark on 6th floor of Young Hall. You must bring some sort of ID with you. It is also a good idea to bring some media to copy the certificate to - like a USB drive.

He will then setup a Purdue Certificate for you and copy it to your USB drive. The certificate consists of the files: usercert.pem and userkey.pem. There will also be a file describing how to install the certificate.

Installing the certificate:

  • copy the certificate files to $HOME/.globus

  • cd /home//.globus

  • ls

    usercert.pem

    userkey.pem

  • change passphrase: grid-change-pass-phrase

  • extract DN from cert: grid-cert-info -subject

  • check if DN is in mapfile: grep /etc/grid-mapfile

If your DN is not in the mapfile, you can use the program gx-request on many of the sites. See here for a list. Otherwise, you will have to mail your DN to help@teragrid.org.

Use tg-login.purdue.teragrid.org as your login point. A list of Purdue's TeraGrid resources can be seen here "Brutus FPGA SGI 450", "Steele Dell 1950 Cluster", and here "Condor Pool".

Note also, that if you are a Purdue affiliate, you can get an account on tg-login.purdue.teragrid.org and login with your career account, using SSH v2.

You may go to the RCAC web site and look at the User Info pages for further information.

How do I use the TeraGrid User Portal?

Logging in

The TeraGrid User portal can be reached from the menu bar on any of the User Info pages on http://www.teragrid.org or by linking to http://portal.teragrid.org.

Then, on the Portal home page, enter your portal username and password in the corresponding fields in the login form, and click the "Login" button. You should have received your portal username and password in your start package.

If you don't see the Login form immediately after you load the portal in your web browser, click the Login link in the upper right-hand corner of the page.

Features

When you have logged in to the Portal, there will be 6 tabs in the top menu. They are the different services available from the portal. Under each tab is a set of navigation links for services within each main service category. Below is taken from the official TeraGrid page.

  • Home: information about the portal, urgent notifications to portal users, and a place for users to provide feedback about the portal. This tab also includes the login page for users who are not logged in.
  • MyTeraGrid: includes information about your TeraGrid projects and allocations, system account usernames on all TeraGrid resources, a list of registered distinguished names, password change form, and an "Add User" form. This tab mostly contains information related to you, the user, and your TeraGrid account.
  • Resources: an interface for monitoring the status of TeraGrid resources. In particular, it shows the load and job queues for compute resources as well as general "static" information about all of the resources. Users may also browse science gateways and data collections from the Resources tab.
  • Documentation: access the full User Info section of www.teragrid.org from without having to leave the portal.
  • Consulting: how to contact the TeraGrid Help Desk.
  • Allocations: how to request TeraGrid allocations.

Hints

If you need help, then click the question mark icon in the upper left corner of the title bar. It will display the available help documentation.

Many of the pages can be customized. If that is the case for a certain page, then there will be a pencil shown in the upper left corner of the title bar. Click the icon to see/change your personal preferences.

When your TeraGrid account was created, a Distinguished Name (DN) was created on your behalf using the NCSA certificate authority. This DN is stored in your profile in our account database and automatically propagated to all sites when your account is created. A proxy certificate with this same DN can be retrieved from the TeraGrid MyProxy certificate repository (myproxy.teragrid.org) on any TG resource by using the myproxy-get-delegation command and supplying your portal username with the -l option and your portal password as the MyProxy passphrase.