BNL Cooperative Cluster
The BNL Cooperative Cluster (coop)
BNL's coop is documented here http://www.phy.bnl.gov/coop/doc/coop.html
Getting an account
To get an account on the coop is a two step process:
- Cutting BNL red tape
- Asking Brett (email@example.com) for an account
General BNL requirements
To get any account at BNL you must satisfy some requirements:
- Get a BNL guest appointment. This can be either a full appointment if you wish to come on site, or a "remote user only" if you only need a remote account. Either case you must start by filling out the Guest Registration form at https://fsd84.bis.bnl.gov/guest/guest.asp . If you will get a "remote user only" account there is a location to specify that and you may ignore any questions pertaining to coming on site. You will need to specify a BNL employee as your host. Choose the BNL Daya Bay collaborator of your choice.
- Take the online "cyber security" training
- Sign the fax/mail/email the "BNL Computer Use Agreement".
After you do this you will be eligible for general accounts provided by our info-tech department (ITD). However, you don't need them to access the coop cluster.
Request the coop account
After the above has been done, ask Brett (firstname.lastname@example.org) for an account. Don't go to this step until your BNL requirements are satisfied as I will not be able to give you an account until after that.
In the email request you should include this information:
- Indicate that you are a Daya Bay collaborator.
- The final Guest ID number you received from BNL
- Your desired username
- Your desired shell (bash or tcsh)
- An SSH2 public key. For help, see:
Accessing the coop
The coop cluster is behind the BNL firewall and not directly accessed. You will be given an account on the BNL Physics Dept "SSH gateway" which will act as your bridge through the firewall. This machine is "gateway.phy.bnl.gov". You must log using the SSH2 private key which is the pair to the public one sent above.
Once on the gateway you can ssh to "coop.phy.bnl.gov", again using your SSH2 key pairs.