The FNAL_FERMIGRID site policy and some documentation can be found here:
http://fermigrid.fnal.gov/policy.html
All users with STAR VOMS proxies are mapped to a single user account ("star").
Technical note: (Quoting from an email that Steve Timm sent to Levente) "Fermigrid1.fnal.gov is not a simple jobmanager-condor. It is emulating the jobmanager-condor protocol and then forwarding the jobs on to whichever clusters have got free slots, 4 condor clusters and actually one pbs cluster behind it too." For instance, I noticed jobs submitted to this gatekeeper winding up at the USCMS-FNAL-WC1-CE site in MonAlisa. (What are the other sites?)
You can use SUMS to submit jobs to this site (though this feature is still in beta testing) following this example:
star-submit-beta -p dynopol/FNAL_FERMIGRID jobDesription.xml
where jobDescription.xml is the filename of your job's xml file.
Hostname: fermigrid1.fnal.gov
condor queue is available (fermigrid1.fnal.gov/jobmanager-condor)
If no jobmanager is specified, the job runs on the gatekeeper itself (jobmanager-fork, I’d assume)
[stargrid02] ~/> globus-job-run fermigrid1.fnal.gov
/bin/cat /etc/redhat-release
Scientific Linux Fermi LTS release 4.2 (Wilson)
[stargrid02] ~/> globus-job-run fermigrid1.fnal.gov/jobmanager-condor /bin/cat /etc/redhat-release
Scientific Linux SL release 4.2 (Beryllium)
[stargrid02] ~/> globus-job-run fermigrid1.fnal.gov/jobmanager-condor /usr/bin/gcc -v
Using built-in specs.
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-java-awt=gtk --host=i386-redhat-linux
Thread model: posix
gcc version 3.4.4 20050721 (Red Hat 3.4.4-2)
There doesn't seem to be a GNU fortran compiler such as g77 on the worker nodes.