The Advanced Recource Connector (ARC) middleware - Testbeds portal
On this page you will find useful information about infrastructure run for testing purposes. Additionally there are some information about how to join and use the infrastructure.
ARC provides an autodeplyment system for ARC services. This system is installing and deploying on daily basis (using Jenkins CI) selected set of ARC services. The new deployment is usually available after 8:00 (if there was a successful nightly Jenkins build). The code used for today is labled as test_job_trunk #70 .
- A-REX: https://testbed1.grid.upjs.sk:443/arex (config file here)
- ARC0 CE: ldapsearch -h testbed1.grid.upjs.sk -p 2135 -x -b 'mds-vo-name=local,o=grid' (config file here)
- Gridftp: gsiftp://testbed1.grid.upjs.sk:2811/unixacl (config file here)
The services are additionally visible over Grid Monitors. Their names contain autodeployed word.
List of allowed DNs is here.
The log files related to these services can be accessed here.
An on-demand autodeployment can be peformed by manually running a test_job_trunk Jenkins build job.
How to connect
In order to connect to ARC infrastructure you have to register to some of the ARC Information index services.Information index services running under ARC testbed are:
Every ARC service (cluster and storage) has to register to indices. To register a cluster or a storage resource to the index service you need put a similar registration blocks in your arc.conf and restart the grid-infosys. Change only the bold texts to suit your setup.
#cluster registration block
ldapsearch -h arc-emi.grid.upjs.sk -p 2135 -x -b 'mds-vo-name=ARC-TESTBED,o=grid' -s base giisregistrationstatus