Last modified 9 years ago Last modified on 11/18/11 12:25:37

Testbed - provided by dCache

The EMI testbed is a setup from resources that are provided by different Product Teams (PTs). Information concerning the joint EMI-Testbed can be found here: Here can be found:

  • Where to request assistance? SPECIFY: GGUS ("ASSIGN TO EMI Testbeds SU" in the ticket)
  • Where clients can be found is described and that people should ask if they need access to more testing resources.

What we need to provide?

  1. VM with our next minor release (no breaking backward compatibility)
  2. RC Vm with our next major release (breaking backward compatibility allowed)
  3. Production Release VM with our current release
  4. EMI is discussing to have a Integration Ready Version (Version that PT declare to be ready for production)

Machines provided by dCache

Machine name dCache version OS Monitored Purpose Located production-1.9.5-19 (Chimera) SL 5.4 yes Xen Enterprise production-1.9.5-19 (PNFS) SL 4.8 yes production-1.9.5-19 (Chimera) SL 4.8 yes production-1.9.12-2 (Chimera) SL 5.5 yes production-1.9.12-2 (Chimera) SL 5.5 yes none SL 5.4 yes Site-Level-BDII

Further details on the machines and what servers they run on can be found here: XenDomains.

Monitoring (you might have to request access to the page

All machines that are provided to EMI are monitored by the UCO. Monitoring data can be seen here:, just enter the name without in the search field, select Healthstate (OK) and (?), click "Filter Hosts" and you will find the health and performance data.


By entering cork|dublin|ennis|galway|sligo|swords|waterford in the search field all machines can be seen at once. Then click choose the field you would like to aggregate (e.g choose sum of uptime) and click "Show aggregate performance", which will provide an aggregated uptime chart for all machines. This result can be printed in pdf form.

Certificate renewal and creation at GridKa?

  1. Goto <username>@pal, enter password
  2. Cd into /afs/

--> it might happen that you have no access rights. Either type kinit to get a kerberos ticket or get access rights from Andreas Gellrich

  1. Source: source /afs/
  2. Execute: ././ -u <FQHN>
  3. Goto webpage: and choose pem-request, follow the instructions on the page
  4. When you received the certificate put it into /afs/, delete the request