Obtaining OSG Credentials for the MCDRD VO
The first step is joining the Muon Collider Detector Research and Development Virtual Organization. This will give you access to MCD grid computing resources. This section tells you how.
Note: As of March 23, 2013, DOEGrids CA will stop issuing new certificates as the transition to OSG completes. For more information see the Fermilab PKI Transition page.
Follow the instructions on the Fermilab documentation for obtaining a personal OSG certificate as a Fermilab staff or user. You will be joining the MCDRD VO, but when you fill out the OIM User Certificate Request Form choose Fermilab as the VO.
Upon submitting the OIM User Certificate Request form you should receive mail confirming the opening of your request ticket. Shortly thereafter it should be confirmed, allowing you to download the ticket from the OIM ticket page.
Import the ticket into your browser (In Chrome, go to Settings -> Advanced Settings... -> HTTP/SSL -> Manage Certificates... -> Import...). Now you should be able to access the MCDRD VO registration page. Fill in the form on this page and submit. The request will be submitted to the VO's administrator and you should get a confirmation email when the submission is made and when the request is approved.
Using the OSG
(Subsections are modified from this page unless otherwise noted.)
Fermilab uses Kerberos for external authentication. This section assumes that you have a Fermilab Kerberos principal. Follow these instructions if you need an account at Fermilab and are authorized to obtain one.
Assuming that your machine has recent versions of SSH and Kerberos and you will not be using a Cryptocard, download Fermilab's official Kerberos configuration file.
Download the file.
Set the environment variable KRB5_CONFIG to point to the Fermilab configuration file.
This variable can be added to your shell profile or setup in a script and the configuration file it points to will override the one in /etc.
Connecting to detsim
Initialize the Kerberos session.
Connect to detsim using ssh
You may need to use ssh_config for the SSH configuration file.
Using Globus tools for submitting grid jobs from Linux/UNIX
This subsection modified from https://fermi.service-now.com/kb_view.do?sysparm_article=KB0010815
If you will be using Globus tools to run grid jobs from a Linux or other UNIX machines, you need to get a proxy certificate. To do so, your certificate and user key need to be in PEM format. To convert them from their original PKCS#12 format to PEM:
- Export your Open Science Grid certificate from your browser.
Use the scp utility to copy the certificate to your detsim account, then ssh into detsim to perform the rest of these steps.
Convert the certificate using the openssl command as shown (use your actual .p12 certificate filename with no angle brackets; use the output name usercert.pem as shown). (You may have to create the $HOME/.globus directory)
To get the encrypted private key (again use your actual .pl2 certificate filename; use the output name userkey.pem as shown):
You must set the mode on your userkey.pem file to read/write only by the owner, otherwise grid-proxy-init will not use it
Session Certificate and quotas
Finally, obtain a session certificate .
By default the proxy is valid for 12 hours, which is probably too short for your job. To obtain a proxy that is valid for 72 hours, issue the command:
To check the status of the proxy:
To check quotas and to check how many slots are already taken:
Example Grid Jobs
Submitting the First Example Jobs
Now you should be all setup to submit a test job to make sure that everything is working. Cut and paste the following lines into your terminal window. This will submit a grid job which starts 5 separate processes. The processes will just execute sleep for 10 seconds before terminating. Since no output is created the sleep_grid.out.$(Cluster).$(Process) and sleep_grid.err.$(Cluster).$(Process) files should be empty.
(Note!: $(Cluster) represents the job number and $(Process) represents the (5) process numbers)
The condor log files are: sleep_grid.log.\$(Cluster).\$(Process)
The second example is an exploration job where the job reports the run time environment it encounters and the file systems that are mounted. This is very often useful to find out what is available on the worker nodes . So have a look at env_grid.out.$(Cluster).$(Process).
Note!: The grid job doesn't inherit the run time environment from your interactive session!