LQCD Home
QDCOC Computing
Lattice Archives at BNL
Contacts
Accessing QCDOC
Command Line Allocator
(replaces the Web Allocator)
Call Tracking System (CTS)
(Account is required)
User Guide
Batch System
File Transfers to/from BNL
Transfering Files between US LQCD Sites
(FNAL Link)
| US LQCD Common Runtime Environment |
CRE: Setup
(CRE_HOME, setup scripts etc. )
CRE: Filesystems
(QDATA, QCACHE, QSCRATCH etc.)
CRE: Interactive System
(Compilers, Libraries, devel. tools, etc.)
CRE: File Management
(qsplit, qunsplit etc.)
CRE Definition (pdf)
(as of June 14th, 2006)
Web Display (Under Construction)
(Allocation status of all available partitions)
QCDOC Status (USDOE only)
(Partitions, Jobs DB, etc.)
Batch System: Current Status
(Available Queues, Running Jobs, etc.)
Errors Database
(DB of ASIC and Wire errors.)
Computer Accounts
Accessing QCDOC
CTS accounts
CyberSecurity Training
RBRC Users Mailing List
USDOE Users Mailing List
|
Accessing QCDOC Computers
The only way to access the QCDOC computing resources remotely (outside the QCDOC network enclave)
is through the QCDOC ssh gateways. Even if you are inside the BNL campus network you still need
to login into the gateways. The gateways ouside BNL are known as ssh.qcdoc.bnl.gov. Inside
the BNL campus they are known as ssh.qcdoc.bnl.local.
Accessing the QCDOC ssh gateways
Static passwords are not supported any more on any BNL ssh gateways. In order to access
the QCDOC ssh gateway a "two factor authentication" method must be used. Allowed
gateway access methods are:
Regarding SSH keys, users must create an SSH public/private key pair and have their public key deployed on the
gateway. Since the gateways are administered by the ITD Unix group, QCDOC users should
email their generated SSH public key to the ITD Help Desk
itdhelp@bnl.gov. It is important that
the users emphasize in their email to the Help Desk that their public key should be deployed
on the QCDCOC ssh gateway and not on the general BNL gateways.
Detailed instructions on how to generate SSH public/private key pairs and how to contact the
Help Desk regarding keys issues are posted in the
Cybersecurity SSH web pages.
Having the user keys setup, users should be able to ssh to the QCDOC gateways:
- ssh ssh.qcdoc.bnl.gov (outside the BNL network)
- ssh ssh.qcdoc.bnl.local (inside the BNL network)
- NOTE:
- You can have more than one public key stored in the .ssh/authorized_keys file. Once your first
SSH public key is deployed by the Help Desk and if you are normally accessing the QCDOC ssh gateways
from more remote machines, you can deploy additional keys by yourself. Simply append your
keys to your authorized_keys file.
Accessing the QCDOC Front-End Nodes
Similarly to the ssh gateways, a "two factor authentication" is required to access the QCDOC
Front-End nodes. Once users have accessed the QCDOC ssh gateways, they should generate a new SSH
public/private key pair and email their new public key to the QCDOC staff.
Users should then be able to access the Front-End nodes from the QCDOC ssh gateways:
- ssh qcdochosta (RBRC)
- ssh qcdochostb (US LQCD)
|
One of ten national laboratories overseen and primarily
funded by the Office of Science of the U.S. Department of Energy (DOE), Brookhaven
National Laboratory conducts research in the physical, biomedical, and environmental
sciences, as well as in energy technologies and national security. Brookhaven Lab also
builds and operates major scientific facilities available to university, industry and
government researchers. Brookhaven is operated and managed for DOE’s Office of Science by
Brookhaven Science Associates, a limited-liability company founded by Stony Brook University,
the largest academic user of Laboratory facilities, and Battelle, a nonprofit, applied science
and technology organization.