Quick gLite HOW-TO for WeNMR users

The WeNMR Grid Infrastructure is available and running the latest INFNGRID gLite 3.2 (SL5) release. Its present layout and a few hints for administrators on how to deploy a new site are available here. The test-bed has been accessible since December 2007, 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 enmr.eu VO filling the form available here. Having the personal certificate installed in your browser is required for the registration procedure; in case of problems with the browser, please have a look at this link;
• Install in your Linux PC the Miramare Interoperable Lite UI (MILU) version of the gLite User Interface (a.k.a. gLite-UI); no root privileges are needed for this installation; this UI has been tested on several linux-based distributions; you can download it from here; please read the documentation available here to install and properly configure it for working with WeNMR in few minutes.
• Put your usercert.pem and userkey.pem under $HOME/.globus directory (have a look here to learn how to convert formats).
• Create a proxy using the command voms-proxy-init -voms enmr.eu 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 synchronisation among grid elements, 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 enmr.eu VO services:

from <-- -->	port	to	port	service
localhost	>1023	wms-enmr.cerm.unifi.it	7443	WMProxy
localhost	>1023	wms-enmr.cerm.unifi.it	2811	GridFTP server
localhost	>1023	lb-enmr.cerm.unifi.it	9000	LB
localhost	>1023	lb-enmr.cerm.unifi.it	9003	LB
localhost	>1023	voms2.cnaf.infn.it	15014	VOMS server

For a quick test, try the command below and look at the output message:

$ glite-wms-job-list-match -a test.jdl
Connecting to the service https://wms-enmr.cerm.unifi.it:7443/glite_wms_wmproxy_server
======================================================================
COMPUTING ELEMENT IDs LIST
The following CE(s) matching your job requirements have been found:
CEId
- ce-enmr.chem.uu.nl:2119/jobmanager-lcgpbs-long
- ce-enmr.chem.uu.nl:2119/jobmanager-lcgpbs-medium
- ce-enmr.chem.uu.nl:2119/jobmanager-lcgpbs-short
- ce-enmr.chem.uu.nl:2119/jobmanager-lcgpbs-verylong
- ce-cr-02.ts.infn.it:8443/cream-lsf-grid
- ce-enmr.chemie.uni-frankfurt.de:2119/jobmanager-lcgpbs-long
- ce-enmr.chemie.uni-frankfurt.de:2119/jobmanager-lcgpbs-medium
- ce-enmr.chemie.uni-frankfurt.de:2119/jobmanager-lcgpbs-short
- ce-enmr.chemie.uni-frankfurt.de:2119/jobmanager-lcgpbs-verylong
- ce.cp.di.uminho.pt:2119/jobmanager-lcgpbs-enmr.eu
- ce01.eela.if.ufrj.br:2119/jobmanager-lcgpbs-enmr
- ce02.eela.if.ufrj.br:8443/cream-pbs-enmr
- cream-ce-2.ba.infn.it:8443/cream-pbs-infinite
- cream-ce-2.ba.infn.it:8443/cream-pbs-long
- cream-ce-2.ba.infn.it:8443/cream-pbs-short
- cream01.iihe.ac.be:8443/cream-pbs-enmr.eu
- gazon.nikhef.nl:2119/jobmanager-pbs-medium
- gazon.nikhef.nl:2119/jobmanager-pbs-short
- grid-ce-01.ba.infn.it:2119/jobmanager-lcgpbs-infinite
- grid-ce-01.ba.infn.it:2119/jobmanager-lcgpbs-long
- grid-ce-01.ba.infn.it:2119/jobmanager-lcgpbs-short
- grid001.cecalc.ula.ve:2119/jobmanager-lcgpbs-enmr
- grid001.ts.infn.it:2119/jobmanager-lcglsf-grid
- gridce.ilc.cnr.it:8443/cream-pbs-grid
- juk.nikhef.nl:8443/cream-pbs-medium
- juk.nikhef.nl:8443/cream-pbs-short
- kg-ce01.cc.kuleuven.be:2119/jobmanager-pbs-enmr.eu
- pbs-enmr.cerm.unifi.it:8443/cream-pbs-long
- pbs-enmr.cerm.unifi.it:8443/cream-pbs-medium
- pbs-enmr.cerm.unifi.it:8443/cream-pbs-short
- pbs-enmr.cerm.unifi.it:8443/cream-pbs-verylong
- prod-ce-01.pd.infn.it:8443/cream-lsf-grid
- prod-ce-02.pd.infn.it:2119/jobmanager-lcglsf-grid
- t2-ce-01.lnl.infn.it:2119/jobmanager-lcglsf-enmr1
- t2-ce-02.lnl.infn.it:2119/jobmanager-lcglsf-enmr1
- t2-ce-03.lnl.infn.it:2119/jobmanager-lcglsf-enmr1
- t2-ce-04.lnl.infn.it:2119/jobmanager-lcglsf-enmr1
- t2-ce-05.lnl.infn.it:8443/cream-lsf-enmr1
- t2-ce-06.lnl.infn.it:8443/cream-lsf-enmr1
- trekker.nikhef.nl:2119/jobmanager-pbs-medium
- trekker.nikhef.nl:2119/jobmanager-pbs-short
- deimos.htc.biggrid.nl:2119/jobmanager-pbs-long
- deimos.htc.biggrid.nl:2119/jobmanager-pbs-medium
- deimos.htc.biggrid.nl:2119/jobmanager-pbs-medium32
- deimos.htc.biggrid.nl:2119/jobmanager-pbs-medium64
- deimos.htc.biggrid.nl:2119/jobmanager-pbs-short
- phoebe.htc.biggrid.nl:8443/cream-pbs-long
- phoebe.htc.biggrid.nl:8443/cream-pbs-medium
- phoebe.htc.biggrid.nl:8443/cream-pbs-medium32
- phoebe.htc.biggrid.nl:8443/cream-pbs-medium64
- phoebe.htc.biggrid.nl:8443/cream-pbs-short
- grid012.ct.infn.it:2119/jobmanager-lcglsf-infinite
- grid012.ct.infn.it:2119/jobmanager-lcglsf-long
- grid012.ct.infn.it:2119/jobmanager-lcglsf-short
- ce01.dur.scotgrid.ac.uk:2119/jobmanager-lcgpbs-q1d
- ce01.dur.scotgrid.ac.uk:2119/jobmanager-lcgpbs-q2d
- ce01.dur.scotgrid.ac.uk:2119/jobmanager-lcgpbs-q30m
- ce01.dur.scotgrid.ac.uk:2119/jobmanager-lcgpbs-q3d
- ce01.dur.scotgrid.ac.uk:2119/jobmanager-lcgpbs-q6h
- ce02.dur.scotgrid.ac.uk:2119/jobmanager-lcgpbs-q1d
- ce02.dur.scotgrid.ac.uk:2119/jobmanager-lcgpbs-q2d
- ce02.dur.scotgrid.ac.uk:2119/jobmanager-lcgpbs-q30m
- ce02.dur.scotgrid.ac.uk:2119/jobmanager-lcgpbs-q3d
- ce02.dur.scotgrid.ac.uk:2119/jobmanager-lcgpbs-q6h
======================================================================

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 enmr.eu VOMS server, which are publicly available in the 3rd and 4th string of the second line of the web page here.

For more details about gLite and its use have also a look at this on-line Training Material produced by the GILDA team.

If you have any problems please contact us here.