Line: 1 to 1 | |||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Quick gLite Deployment Guide for WeNMR grid site managersThis page provides support on the following topics:
Grid Elements deploymentWeNMR sites willing to deploy gLite services (CE, SE, UI, WN) might consider to follow the installation/configuration instructions of the INFNGRID release gLite 3.1/SL4 guide or gLite 3.2/SL5 guide. Commodity PCs are typically enough powerful to run the majority of the grid services. A minimal hardware configuration can be the following: a biprocessor machine with 1GB/core of RAM and 80GB SATA of HD. Most recent machines with 2-CPU quad-core and 2GB/core RAM can even be virtualized to host 4 different grid services with minimal loss of performances. Quite all of the grid elements you may want to deploy at your site are gLite 3.2 version on Scientific Linux 5/x86_64. The plan for migrating the few grid elements still with gLite 3.1 Scientic Linux 4/ x86 to gLite 3.2 is available here. Most of grid services needs a X509 certificate issued by a IGTF recognized Certification Authority (e.g. DutchGrid CA, GridKa CA, INFN CA, LCG catch-all,...). European sites should identify here their national CA and verify if their Institute is already a Registration Authority (RA) of that CA. If not, they should ask the CA to become a qualified RA, in order to be able to issue both host and personal certificates needed for grid operations. Be sure that the administrative network domain hosting the gLite services to be deployed is configured in order to allow communications with external hosts and ports as described in the document available here. In particular:
enmr.eu VO service configurationAt the link https://voms2.cnaf.infn.it:8443/voms/enmr.eu/configuration/configuration.action you'll find the data needed to configure the Grid services you might want to deploy at your site. If you are using the INFNGRID Release, you can automatically enable the enmr.eu VO in your gLite services using ig-yaim. Particularly the file /opt/glite/yaim/examples/siteinfo/vo.d/enmr.eu already contains the needed lines: SW_DIR=$VO_SW_DIR/enmrDEFAULT_SE=$CLOSE_SE_HOST STORAGE_DIR=$CLASSIC_STORAGE_DIR/enmr VOMS_SERVERS="'vomss://voms2.cnaf.infn.it:8443/voms/enmr.eu?/enmr.eu' 'vomss://voms-02.pd.infn.it:8443 /voms/enmr.eu?/enmr.eu'" VOMSES="'enmr.eu voms2.cnaf.infn.it 15014 /C=IT/O=INFN/OU=Host/L=CNAF/CN=voms2.cnaf.infn.it enmr.eu' 'enmr.eu voms-02.pd.infn.it 15014 /C=IT/O=INFN/OU=Host/L=Padova/CN=voms-02.pd.infn.it enmr.eu'" VOMS_CA_DN="'/C=IT/O=INFN/CN=INFN CA' '/C=IT/O=INFN/CN=INFN CA'" while 20 pool accounts + sgmenmr are included in the relevant files /opt/glite/yaim/examples/ig-users.conf and /opt/glite/yaim/examples/ig-groups.conf When installing e.g. a Computing Element with ig-yaim then automatically you get the VOMS mapping like: [root@prod-ce-01 root]# cat /etc/grid-security/grid-mapfile ... "/enmr.eu/Role=SoftwareManager/Capability=NULL" .sgmenmr "/enmr.eu/Role=SoftwareManager" .sgmenmr "/enmr.eu/*/Role=NULL/Capability=NULL" .enmr "/enmr.eu/*" .enmr "/enmr.eu/Role=NULL/Capability=NULL" .enmr "/enmr.eu" .enmr INFNGRID release is adopting DGAS as accounting system. If you want to enable DGAS accounting on your CE, and use the INFNGRID-Release you can have a look at the item DGAS services on CE (CE LCG, CE CREAM) in the gLite 3.1/SL4 (or gLite3.2/SL5) guide and define the variable DGAS_HLR_RESOURCE="hlr-enmr.pd.infn.it" in your ig-site-info.def. More details are available on the DGAS guide. If you are not using the INFNGRID-Release, to enable the DGAS sensors on your CEs, you have to do the following steps:
"/enmr.eu/*":::: "/enmr.eu":::: For enmr.eu VO a specific structure is needed for sgm pool accounts. To fit these requirements some manual steps have to be performed in the software area exported to WNs. Assuming that the directory $VO_ENMR_EU_SW_DIR is already present with sgmenmr001.sgmenmr ownership, the following commands have to be issued: mkdir $VO_ENMR_EU_SW_DIR/BCBR $VO_ENMR_EU_SW_DIR/BMRZ $VO_ENMR_EU_SW_DIR/CIRMMP chown sgmenmr001.sgmenmr $VO_ENMR_EU_SW_DIR/BCBR; chmod g+w $VO_ENMR_EU_SW_DIR/BCBR chown sgmenmr001.sgmenmr $VO_ENMR_EU_SW_DIR/BMRZ; chmod g+w $VO_ENMR_EU_SW_DIR/BMRZ chown sgmenmr001.sgmenmr $VO_ENMR_EU_SW_DIR/CIRMMP; chmod g+w $VO_ENMR_EU_SW_DIR/CIRMMP enmr.eu VO dedicated gLite servicesSome high-level gLite services have been set-up at INFN-CNAF and CIRMMP. These are:
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 ========================================================================== When other sites will to join the test-bed, they will be match-ables by the glite-WMS, as soon as they'll send us the LDAP address of their site-BDII. This is a string like: ldap://prod-bdii-02.pd.infn.it:2170/mds-vo-name=INFN-PADOVA,o=grid and it allows us to include your site to our Top-BDII bdii-wenmr.pd.infn.it If you have any problems please contact us here. |