Test-bed Installation Sample Clauses

Test-bed Installation. PoC infrastructure In the section 3.3, a list of gLite services that will be install in the neuGRID infrastructure was provided. Here is a recap of this list: • VOMS • MyProxy • LFC • WMS/LB • tBDII • sBDII • DPM • CE/VN The 5 first services (VOMS, MyProxy, LFC, tBDII and WMS/LB) will be part of the GCC as core services of the neuGrid infrastructure. Indeed, they can be seen as gLite core services under which all other neuGRID services can be added / mixed. The VOMS server can be shared for the 2 sub- infrastructures (PoC, PROD) as it is able to deal with sub groups. This is also the case for MyProxy as it’s only a proxy certificate repository into which each user can dump their own. But concerning LFC, tBDII and WMS/LB, there will have one instance of each service per sub-infrastructure to avoid all the potential resource sharing problems and to ease user access rights management. Concerning the other services (sBDII, DPM, CE/WN), they will be installed on each DACS to provide them with data storage and computing power capability. This approach is considered to be a standard practice for gLite middleware deployment. In the following figure (Figure 4-2), you can find a representation that emphasizes the gLite services that are deployed inside of the PoC, as of today. sBDII DPM DACS 2 : CE/WN sBDII DPM LEVEL 1 DACS 1 : CE/WN tBDII WMS/LB LFC CA VOMS MyProxy GCC : LEVEL 0 Figure 4-2: gLite services repartition inside POC As it is described in the project description of work document, “LEVEL 0” represents the “infrastructure ground truth” level and “LEVEL 1” represents the Data Archiving and Computing Sites (DACS). The number of WN will depend on the available hardware at each DACS. The more hardware will be available, the more WNs will be installed to increase the DACS computing power capability. In the context of the PoC deployment, two partners are members of the PoC infrastructure: • MAAT which owns the GCC and one DACS, • PRODEMA which own another DACS. The current development status is the following for the GCC: HOSTNAME/IP SERVICES xx-xxxx-xxxxxx0.xxxx-x.xxx VOMS xx-xxxx-xxxxxx0.xxxx-x.xxx LFC + tBDII xx-xxxx-xxxxxx0.xxxx-x.xxx MyProxy xx-xxxx-xxxxxx0.xxxx-x.xxx WMS + LB xxxxxx.xx-xxxx-xxxxxx0.xxxx-x.xxx CA For the DACS mimicked by MAAT, the deployment is the following: HOSTNAME/IP SERVICES xx-xxxx-xxxxxx0.xxxx-x.xxx DPM + sBDII xx-xxxx-xxxxxx0.xxxx-x.xxx CE xx-xxxx-xxxxxx00.xxxx-x.xxx WN xx-xxxx-xxxxxx00.xxxx-x.xxx WN xx-xxxx-xxxxxx00.xxxx-x.xxx WN