-- MarcoVerlato - 2011-12-16

Quick gLite HOW-TO for CYCLOPS users

The CYCLOPS test-bed is available and running the gLite 3.1 release with latest updates. Its present layout and a few hints to deploy a new site are available here. The test-bed has been accessible since December 2006, and only a few steps are needed to access it from almost any Linux PC. You will need to:

• Own a personal certificate issued by a IGTF recognized CA (i.e. ASGCCA, INFN CA, LCG catch-all,...);
• Register with the '''cyclops VO''' filling the form available here. Having the personal certificate installed in your browser is required for the registration procedure;
• Download from here and install in your Linux PC the Plug & Play version of the gLite 3.1/SL4 User Interface (a.k.a. UI); no root privileges are needed for this installation (see the README file in the distribution); this UI has been tested on Scientific Linux CERN 4.5 (SLC4.5), but it should work on most of the common Linux distributions; it works for both gLite 3.0 and 3.1 services; to access cyclops resources just replace the following lines in the file UIPnP.conf:

BDII_HOST=prod-bdii-01.pd.infn.it
DEFAULT_LB_HOST=prod-lb-01.pd.infn.it
DEFAULT_RB_HOST=prod-wms-01.pd.infn.it
DEFAULT_VO=cyclops

• Create a proxy using the command voms-proxy-init -voms cyclops and start to submit jobs (see the gLite User Guide for more details). Please notice that since September 2007 the NS component of the WMS has been removed, so '''you must use the WMProxy''' component which is accessed through the glite-wms-job-* commands. Therefore the edg-job-* and glite-job-* commands will not work anymore.
• Be sure that the administrative network domain from where you perform these operations is configured in order to allow communications with external hosts and ports as described in the document available here. In particular, most of the grid services has to be run on hosts with public IP address, and only the WNs can run under NAT with an appropriate configuration. Another important requirement is time syncronisation among grid element, typically achieved making use of NTP. As an example, for the UI you should make sure that the following ports are open for communication with the cyclops VO services:

For a quick test, if you deployed the UIPnP in your home directory, try the command below and look at the output message:

$ glite-wms-job-list-match -a UIPnP/test.jdl

Connecting to the service https://prod-wms-01.pd.infn.it:7443/glite_wms_wmproxy_server

======================================================================

COMPUTING ELEMENT IDs LIST
The following CE(s) matching your job requirements have been found:

CEId

- ce.cp.di.uminho.pt:2119/jobmanager-lcgpbs-cyclops
- ce.egee.di.uminho.pt:2119/jobmanager-lcgpbs-cyclops
- egee-ce.datagrid.jussieu.fr:2119/jobmanager-lcgpbs-esr
- grid001.ts.infn.it:2119/jobmanager-lcglsf-grid
- grid003.roma2.infn.it:2119/jobmanager-lcgpbs-grid
- gridce.ilc.cnr.it:2119/jobmanager-lcgpbs-grid
- gridce.pi.infn.it:2119/jobmanager-lcglsf-grid4
- gridce.sns.it:2119/jobmanager-lcgpbs-grid
- prod-ce-01.pd.infn.it:2119/jobmanager-lcglsf-cyclops
- prod-ce-02.pd.infn.it:2119/jobmanager-lcglsf-cyclops
- gridba2.ba.infn.it:2119/jobmanager-lcgpbs-infinite
- gridba2.ba.infn.it:2119/jobmanager-lcgpbs-long
- gridba2.ba.infn.it:2119/jobmanager-lcgpbs-short
- ce02.lip.pt:2119/jobmanager-lcgsge-cyclopsgrid
- gridce2.pi.infn.it:2119/jobmanager-lcglsf-grid4
- grid002.ca.infn.it:2119/jobmanager-lcglsf-grid

======================================================================

If you are planning to access the WMProxy via its web-services interface, you may want to generate voms proxies programatically, e.g. from java code. In this case, it can be useful to know the Port and the DN of the cyclops VOMS server, which are publicly available in the 3rd and 4th string of the second line of the web page here. More information about WMProxy APIs are available here.

If you have any problems please contact us at this email address.