Difference between revisions of "NGI CZ:VO auger"

From EGIWiki
Jump to: navigation, search
Line 13: Line 13:
 
= Links  =
 
= Links  =
  
*[[NGI_CZ:CVMFS for auger]]<br>
+
*[[NGI CZ:CVMFS for auger |CVMFS for auger]]<br>
  
 
<br>  
 
<br>  

Revision as of 14:16, 11 July 2014

VO auger is one of the biggest resource consumers of the EGI grid. It is used for Monte Carlo simulations of the extensive cosmic ray showers. Reconstructed signal is compared with measurements of the Pierre Auger Observatory.

VO auger central servers

  • VOMS server: voms1.egee.cesnet.cz, voms2.grid.cesnet.cz
  • LFC server: lfc1.egee.cesnet.cz


Links


Resources for the VO auger

Czech Republic

  • CESNET
    • Prague site:
      • Storage: dpm1.egee.cesnet.cz: 46 TB of disk space total (for all supported VOs), 15 TB of it reserved via space token AUGERPROD for production
      • CPU: No special reservations, 72 cores available in total
    • Data Storage at Pilsen:
      • Storage: dcache.du.cesnet.cz: 7 TB of disk space total, 5 TB of it reserved via space token AUGERPROD (for production), remaining 2 TB of disk space for auger users; arround 100 TB available on tape via space token AUGERTAPE (with 1 TB disk buffer for write and another 1 TB buffer for read). Available since November 2012.
  • FZU (Institute of Physics of the Academy of Sciences of the Czech Republic), site praguelcg2:
    • Storage: golias100.farm.particle.cz: 122 TB of disk space for VO auger, 54 TB of it reserved via space token AUGERPROD for production
    • CPU: fairshare set to 2% of published 3860 cores

Frequently Asked Questions

  • I got a new certificate. What do I have to do to continue my work?

a) If the DN of your certificate did not change and the issuing CA (Certification Authority) is the same, you do not have to do anything special regardng your membership in the VO. Just put your new certificate into the proper dircetory on your UI (usually in $HOME/.globus) in the proper format and you can use it. Also do not forget to load your new certificate into your browser if your certificate renewal was not done via browser.


b) The case when the DN has changed (and possible also CA has changed is more complicated. You must prove thet you are the same person as the holder of the old certificate and you must let it known to the registration system PERUN. If the old certificate is still valid, make sure that your both certificates are loaded in your browser. Then visit the consolidator of identities and select first your old certificate and then your new certificate when prompted. You can also use the new one first and then the old one. This procedure  registers your new certificate to your existing identity. The new certificate will be propagated to VOMS servers in less than 1 hour. In case that your old certificate is not valid anymore, you must register as a new user to the VO. Usualy the DN is similar to the old one (it contains name and surname) and the system will alert VO manager, that the new user resmbles an old one. The VO manager can ask perun support (perun@cesnet.cz) to unify these identities.

This procedure will keep the username and password on the centraly managed UIs the same, but all grid files owned by the old certificate are considered as files of another user. You may ask VO data manager (and he must often ask site system administrator) to change ownership.




--Chudoba 15:15, July 11, 2014 (CET)