You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

I have actually already have a nersc cert. It's automatic with your account.

Test a gridftp from  from RCF site

  1. ssh rssh.rhic.bnl.gov
  2. ssh to stargrid node (01,02,03,04) , e.g.  ssh   stargrid01
  3. create proxy at stargrid node : myproxy-logon -s nerscca.nersc.gov -t 240  
    myproxy-logon -s nerscca.nersc.gov
Enter MyProxy pass phrase: [enter PDSF NIM password]
A credential has been received for user balewski in /tmp/x509up_u3329
    You specify how long you want your cert to last with '-t hours' option.  The limit is ~11 days.
  4. verify proxy expiration time : grid-proxy-info 
    Here's an example of a proxy  on our ALICE installation with  CERN cert
subject  : /DC=ch/DC=cern/OU=Organic Units/OU=Users/CN=jporter/CN=482817/CN=Jeff Porter/CN=1269780641
issuer   : /DC=ch/DC=cern/OU=Organic Units/OU=Users/CN=jporter/CN=482817/CN=Jeff Porter
identity : /DC=ch/DC=cern/OU=Organic Units/OU=Users/CN=jporter/CN=482817/CN=Jeff Porter
type     : Proxy draft (pre-RFC) compliant impersonation proxy
strength : 512 bits
path     : /tmp/x509up_u49514
timeleft : 39:58:38  (1.6 days)
  5. transfer of a single file from RCF to PDSF:  
stargrid01:~$globus-url-copy file:///star/data13/Magellan/source  gsiftp://pdsfdtn1.nersc.gov/project/projectdirs/star/target

Q: what is the path to /star/data13/ visible to globus?

The path is via any of 3 machines:  stargrid02, stargrid03, stargrid04.   
I think stargrid04 is the one to use.  Therefor you will need to define 
that endpoint.  I just made my definition public, so you should be able to 
see porter#star4 as an endpoint.  You will need to activate it 
- BUT here is the next step.  NERSC recognizes your cert, stargrid04 doesn't.  
 For star to recognize it, you need to make a
*** web request with that CERT ***.
To make a web request you need to load it into your browser.

Ok, It's a pain but at least it's a one-time operation.  I'll show you the steps.

1) on a stargrid node,  do the 'myproxy-logon -s nerscca.nersc.gov'
2) copy the proxy file, /tmp/x509up_whateveritisforyou, to your laptop.
3) change it to pk12 format:

openssl pkcs12 -in yourcopiedoverfile -export -out jans-nersc.p12

It will ask for a password to encrypt it.

4) import into your browser.  I'll assume firefox:

preferences->Advanced->Encryption->View Certificates  Then click 'import'.
It will ask for the password of the file (it may first ask for your password if yuo've locked the browser)

5) Once that's installed (it will be in the list in the preferences panel) go to:

https://vo.racf.bnl.gov:8443/voms/star/

It should see your cert (displayed on the webpage). From the page, request to be a member of the STAR VO.  You'll need to reply to an automatic email, but then Jerome will be notified.

Optimization of globus transfer, various suggestions

guc is globus-url-copy - acronym invented by Levente
srm is a software layer over that - it makes sure transfers complete

There is a –r recursive copy option;

Or else you can do a loop in shell:
set daq   = (1380001.daq 1380003.daq 1380004.daq);
foreach f ($daq)
globus-url-copy -p 25 file:/star/bla/bla/$f
gsiftp://pdsfgrid.nersc.gov/bla/bla/bla/$f
end


 If you specify a source ending in "XXX/" , it will treat XXX as a
directory and transfer all files in XXX from the XXX directory

Use -p 25 option for having more streams, but isn't 25 overdoing it? You got 1 file
cut into 25 buffer chunks and all this has to be re-assembled on arrival.
I'd try +-2 around 8.

Use different end-point machine:  dtn01.nersc.gov  to avoid STAR,ATLAS conflicts

there is also carvergrid.nersc.gov gatekeeper I have access too.

 pull from carver, you need to load the osg module ,and then you have the globus commands available

bbbb

  • No labels