Difference: WebHome (1 vs. 70)

Revision 692014-10-07 - PaoloVeronesi

Line: 1 to 1
 

Sita Admin Corner

Line: 27 to 27
 

National Squid service for CVMFS

If you are going to run jobs on your cluster using CernVM-FS you should also use squids to cache data at your site. In case you decide to not install a squid service at your site or in case of failover at your site, Italian NGI provide a National squid service accessible only by registered italian sites.
Changed:
<
<
We have two squids with ACLs based source and destination. If you decide to use this service, please contact igi-noc@lists.italiangrid.it providing:
>
>
We have two squids with ACLs based source and destination. If you decide to use this service, please open a ticket through XGUS providing:
 
  • the network information of your WNs (eg 131.154.101.0/255.255.255.0);
  • the cvmfs server(s) your WNs need to contact (eg: cvmfs-gridit.cnaf.infn.it);
  • add the line CVMFS_HTTP_PROXY="http://squid01.cnaf.infn.it:3128|http://squid02.cnaf.infn.it:3128" to the configuration of the cvmfs client on each WN (usually under /etc/cvmfs/config.d/).

Revision 622013-11-08 - GiuseppeMisurelli

Line: 1 to 1
 

Sita Admin Corner

Changed:
<
<

Italian Production sites

>
>

Italian Production sites

 you can find here the list of Italian sites.
Changed:
<
<

Controlli con Glue Validator

>
>

Central banning setup for sites

Howto for NGI_IT sites only available here

Controlli con Glue Validator

 Informazioni sullo strumento e segnalazioni degli errori
Changed:
<
<

National Squid service for CVMFS

>
>

National Squid service for CVMFS

 If you are going to run jobs on your cluster using CernVM-FS you should also use squids to cache data at your site. In case you decide to not install a squid service at your site or in case of failover at your site, Italian NGI provide a National squid service accessible only by registered italian sites.

We have two squids with ACLs based source and destination. If you decide to use this service, please contact igi-noc@lists.italiangrid.it providing:

Line: 72 to 76
 
Changed:
<
<

Upgrade Plan

>
>

Upgrade Plan

 
Changed:
<
<

Tutorial

>
>

Tutorial

 
V Corso di formazione INFN per amministratori di siti GRID
Agenda
Tutorial WNoDes
Line: 83 to 87
 
Tutorial Cream
Tutorial Yaim
Changed:
<
<

Notes about services from IGI middleware, based on EMI/UMD

>
>

Notes about services from IGI middleware, based on EMI/UMD

 These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation. This document is addressed to site administrators responsible for middleware installation and configuration.
Line: 118 to 122
 
CORE service File Transfer Service (FTS) TODO EMI-2
CORE service VOMS Notes about Installation and Configuration of EMI2 VOMS-MySQL on SL6 EMI-2
Changed:
<
<

References

>
>

References

 
  1. About IGI - Italian Grid infrastructure
  2. About IGI Release
  3. IGI Official Installation and Configuration guide
Line: 126 to 130
 
  1. Grid Administration FAQs page


Changed:
<
<

Outdated Guides

gLite middleware (OUTDATED)

>
>

Outdated Guides

gLite middleware (OUTDATED)

 Notes about services based on gLite middleware
Changed:
<
<

How to join, installing and configure igi.italaingrid.it VO on your site (OUTDATED)

>
>

How to join, installing and configure igi.italaingrid.it VO on your site (OUTDATED)

 How to join, installing and configure igi.italaingrid.it VO on your site

Table about Installation and Configuration of Grid services EMI-1 (OUTDATED)

Revision 602013-10-28 - PaoloVeronesi

Line: 1 to 1
 

Sita Admin Corner

Line: 18 to 18
 

Using National Squid service for failover

If you run local squid service, you can also add the national squid servers for failover case. CVMFS_HTTP_PROXY is used to specify the squid server(s) to be used for local caching. It supports both load balance and failover:
Changed:
<
<
>
>
 

Configuration test for failover

Line: 59 to 59
 
INFN-CATANIA failover
INFN-PISA failover
INFN-ROMA2 primario
Added:
>
>
Siti Scope UNINA failover
 
TRIGRID-INFN-CATANIA failover
UNI-PERUGIA primario

Revision 592013-10-24 - AlessandroPaolini

Line: 1 to 1
 

Sita Admin Corner

Added:
>
>

Italian Production sites

you can find here the list of Italian sites.
 

National Squid service for CVMFS

If you are going to run jobs on your cluster using CernVM-FS you should also use squids to cache data at your site. In case you decide to not install a squid service at your site or in case of failover at your site, Italian NGI provide a National squid service accessible only by registered italian sites.
Line: 67 to 70
 

Upgrade Plan

Deleted:
<
<

Italian Production sites

you can find here the list of Italian sites.
 

Tutorial

V Corso di formazione INFN per amministratori di siti GRID
Agenda

Revision 572013-10-17 - PaoloVeronesi

Line: 1 to 1
 

Sita Admin Corner

National Squid service for CVMFS

Changed:
<
<
If you are going to run jobs on your cluster using CernVM-FS you should also use squids to cache data at your site. In case you decide to not install a squid service at your site, Italian NGI provide a National squid service accessible only by registered italian sites.
>
>
If you are going to run jobs on your cluster using CernVM-FS you should also use squids to cache data at your site. In case you decide to not install a squid service at your site or in case of failover at your site, Italian NGI provide a National squid service accessible only by registered italian sites.
  We have two squids with ACLs based source and destination. If you decide to use this service, please contact igi-noc@lists.italiangrid.it providing:
  • the network information of your WNs (eg 131.154.101.0/255.255.255.0);
Line: 12 to 12
  Eg. for VO gridit: /etc/cvmfs/config.d/gridit..conf:CVMFS_HTTP_PROXY="http://squid01.cnaf.infn.it:3128|http://squid02.cnaf.infn.it:3128"
Added:
>
>

Using National Squid service for failover

If you run local squid service, you can also add the national squid servers for failover case. CVMFS_HTTP_PROXY is used to specify the squid server(s) to be used for local caching. It supports both load balance and failover:

Configuration test for failover

Thanks to E. Mazzoni, INFN-PISA.
# cmssquid.pi.infn.it and cmssquid2.pi.infn.it primary group, squid01.cnaf.infn.it and squid01.cnaf.infn.it failover group

# Normal behaviour
[root@stormgf1 ~]# cvmfs_talk -i belle.cern.ch proxy info
Load-balance groups:
[0] http://cmssquid.pi.infn.it:3128, http://cmssquid2.pi.infn.it:3128
[1] http://squid01.cnaf.infn.it:3128, http://squid02.cnaf.infn.it:3128
Active proxy: [0] http://cmssquid.pi.infn.it:3128 

# Failover behaviour (cmssquid.pi.infn.it and cmssquid2.pi.infn.it denied by acl on router)
[root@stormgf1 ~]# cvmfs_talk -i belle.cern.ch proxy info
Load-balance groups:
[0] http://cmssquid2.pi.infn.it:3128, http://cmssquid.pi.infn.it:3128
[1] http://squid02.cnaf.infn.it:3128, http://squid01.cnaf.infn.it:3128
Active proxy: [1] http://squid02.cnaf.infn.it:3128 
 

Table

List of the cvmfs servers and sites supported by national squid server.
cvmfs servers
Line: 27 to 53
 
Sites Note
IGI-BOLOGNA primario
Changed:
<
<
INFN-PERUGIA primario
>
>
UNI-PERUGIA primario
 
INFN-PISA failover
INFN-ROMA2 primario

Revision 542013-09-26 - PaoloVeronesi

Line: 1 to 1
 

Sita Admin Corner

Line: 7 to 7
  We have two squids with ACLs based source and destination. If you decide to use this service, please contact igi-noc@lists.italiangrid.it providing:
  • the network information of your WNs (eg 131.154.101.0/255.255.255.0);
Changed:
<
<
  • the cvmfs server(s) your WNs need to contact (eg: igi-cvmfs.cnaf.infn.it);
>
>
  • the cvmfs server(s) your WNs need to contact (eg: cvmfs-gridit.cnaf.infn.it);
 
  • add the line CVMFS_HTTP_PROXY="http://squid01.cnaf.infn.it:3128|http://squid02.cnaf.infn.it:3128" to the configuration of the cvmfs client on each WN (usually under /etc/cvmfs/config.d/).
Changed:
<
<
Eg. for VO igi.italiangrid.it.conf: /etc/cvmfs/config.d/igi.italiangrid.it.conf:CVMFS_HTTP_PROXY="http://squid01.cnaf.infn.it:3128|http://squid02.cnaf.infn.it:3128"
>
>
Eg. for VO gridit: /etc/cvmfs/config.d/gridit..conf:CVMFS_HTTP_PROXY="http://squid01.cnaf.infn.it:3128|http://squid02.cnaf.infn.it:3128"
 

Useful link

Revision 532013-09-25 - PaoloVeronesi

Line: 1 to 1
 

Sita Admin Corner

National Squid service for CVMFS

If you are going to run jobs on your cluster using CernVM-FS you should also use squids to cache data at your site. In case you decide to not install a squid service at your site, Italian NGI provide a National squid service accessible only by registered italian sites.
Changed:
<
<
We have two squids with ACLs based source and destination. If you decide to use this service, please contact igi-noc@lists.italiangrid.it providing the network information of your WNs and the cvmfs server(s) your WNs need to contact.
>
>
We have two squids with ACLs based source and destination. If you decide to use this service, please contact igi-noc@lists.italiangrid.it providing:
  • the network information of your WNs (eg 131.154.101.0/255.255.255.0);
  • the cvmfs server(s) your WNs need to contact (eg: igi-cvmfs.cnaf.infn.it);
  • add the line CVMFS_HTTP_PROXY="http://squid01.cnaf.infn.it:3128|http://squid02.cnaf.infn.it:3128" to the configuration of the cvmfs client on each WN (usually under /etc/cvmfs/config.d/).

Eg. for VO igi.italiangrid.it.conf: /etc/cvmfs/config.d/igi.italiangrid.it.conf:CVMFS_HTTP_PROXY="http://squid01.cnaf.infn.it:3128|http://squid02.cnaf.infn.it:3128"

 

Useful link

Revision 522013-09-12 - PaoloVeronesi

Line: 1 to 1
 

Sita Admin Corner

Added:
>
>

National Squid service for CVMFS

If you are going to run jobs on your cluster using CernVM-FS you should also use squids to cache data at your site. In case you decide to not install a squid service at your site, Italian NGI provide a National squid service accessible only by registered italian sites.

We have two squids with ACLs based source and destination. If you decide to use this service, please contact igi-noc@lists.italiangrid.it providing the network information of your WNs and the cvmfs server(s) your WNs need to contact.

Useful link

 

Upgrade Plan

Line: 16 to 26
 
Tutorial Cream
Tutorial Yaim
Deleted:
<
<

How to join, installing and configure igi.italaingrid.it VO on your site

How to join, installing and configure igi.italaingrid.it VO on your site
 

Notes about services from IGI middleware, based on EMI/UMD

These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation. This document is addressed to site administrators responsible for middleware installation and configuration.
Added:
>
>

Information about ARGUS and gLexec Deployment

* Actions for site-admins
 

Table about Installation and Configuration of Grid services EMI-3

The core services are those that are typically shared by multiple VOs and which interact with the resources made available at the Grid Site level. They should not be installed at Site level.
Service Type Service Name Installation Notes Provider O.S.
Line: 50 to 61
 
CORE service File Transfer Service (FTS) TODO EMI-2
CORE service VOMS Notes about Installation and Configuration of EMI2 VOMS-MySQL on SL6 EMI-2
Changed:
<
<

Table about Installation and Configuration of Grid services EMI-1

>
>

References

  1. About IGI - Italian Grid infrastructure
  2. About IGI Release
  3. IGI Official Installation and Configuration guide
  4. Troubleshooting Guide for Operational Errors on EGI Sites
  5. Grid Administration FAQs page


Outdated Guides

gLite middleware (OUTDATED)

Notes about services based on gLite middleware

How to join, installing and configure igi.italaingrid.it VO on your site (OUTDATED)

How to join, installing and configure igi.italaingrid.it VO on your site

Table about Installation and Configuration of Grid services EMI-1 (OUTDATED)

 The core services are those that are typically shared by multiple VOs and which interact with the resources made available at the Grid Site level. They should not be installed at Site level.
Service Type Service Name Installation Notes Provider
SITE service User Interface (UI) Notes about Installation and Configuration of UI EMI-1
Line: 69 to 95
 
CORE service LCG file Catalog (LFC) Notes about Installation and Configuration of a LFC server EMI-1
CORE service File Transfer Service (FTS) TODO EMI-1
CORE service VOMS Notes about Installation and Configuration of VOMS-MySQL EMI-1
Deleted:
<
<

References

  1. About IGI - Italian Grid infrastructure
  2. About IGI Release
  3. IGI Official Installation and Configuration guide
  4. Troubleshooting Guide for Operational Errors on EGI Sites
  5. Grid Administration FAQs page


gLite middleware (OUTDATED)

Notes about services based on gLite middleware

Information about ARGUS and gLexec Deployment

Revision 512013-07-22 - PaoloVeronesi

Line: 1 to 1
 

Sita Admin Corner

Line: 27 to 27
 The core services are those that are typically shared by multiple VOs and which interact with the resources made available at the Grid Site level. They should not be installed at Site level.
Service Type Service Name Installation Notes Provider O.S.
CORE service LCG file Catalog (LFC) Notes about Installation and Configuration of EMI-3 (SL6) LFC server EMI-3 SL6
Added:
>
>
CORE service MyProxy Notes about MyProxy - EMI-3 - SL6 EMI-3 SL6
 

Table about Installation and Configuration of Grid services EMI-2

The core services are those that are typically shared by multiple VOs and which interact with the resources made available at the Grid Site level. They should not be installed at Site level.

Revision 492013-06-24 - PaoloVeronesi

Line: 1 to 1
 

Sita Admin Corner

Line: 20 to 20
 These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation. This document is addressed to site administrators responsible for middleware installation and configuration.
Added:
>
>

Table about Installation and Configuration of Grid services EMI-3

The core services are those that are typically shared by multiple VOs and which interact with the resources made available at the Grid Site level. They should not be installed at Site level.
Service Type Service Name Installation Notes Provider O.S.
CORE service LCG file Catalog (LFC) Notes about Installation and Configuration of EMI-3 (SL6) LFC server EMI-3 SL6
 

Table about Installation and Configuration of Grid services EMI-2

The core services are those that are typically shared by multiple VOs and which interact with the resources made available at the Grid Site level. They should not be installed at Site level.
Service Type Service Name Installation Notes Provider O.S.

Revision 472012-09-26 - PaoloVeronesi

Line: 1 to 1
 

Sita Admin Corner

Line: 22 to 22
 

Table about Installation and Configuration of Grid services EMI-2

The core services are those that are typically shared by multiple VOs and which interact with the resources made available at the Grid Site level. They should not be installed at Site level.
Service Type Service Name Installation Notes Provider O.S.
Changed:
<
<
SITE service User Interface (UI) TODO EMI-2
>
>
SITE service User Interface (UI) Notes about installation and configuration of EMI-UI - EMI-2 SL6 EMI-2 SL6
 
SITE service Torque server stand alone (no cream) Notes about torque server - EMI-2 SL6 EMI-2 SL6
SITE service Cream Computing Element (without TORQUE) with MPI Notes about Cream without Torque with MPI - EMI-2 SL6 EMI-2 SL6
SITE service Worker Node (WN) + TORQUE + MPI + GLEXEC Notes about WN (torque, mpi, glexec) - EMI-2 SL6 EMI-2 SL6

Revision 452012-09-14 - PaoloVeronesi

Line: 1 to 1
Changed:
<
<

Italian Production sites

>
>

Sita Admin Corner

Italian Production sites

 you can find here the list of Italian sites.
Changed:
<
<

How to enable igi.italiangrid.it VO

>
>

Tutorial

V Corso di formazione INFN per amministratori di siti GRID
Agenda
Tutorial WNoDes
Tutorial StoRM

How to join, installing and configure igi.italaingrid.it VO on your site

How to join, installing and configure igi.italaingrid.it VO on your site
 

Notes about services from IGI middleware, based on EMI/UMD

These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation. This document is addressed to site administrators responsible for middleware installation and configuration.
Deleted:
<
<
 

Table about Installation and Configuration of Grid services EMI-2

The core services are those that are typically shared by multiple VOs and which interact with the resources made available at the Grid Site level. They should not be installed at Site level.
Service Type Service Name Installation Notes Provider O.S.

Revision 442012-08-14 - PaoloVeronesi

Line: 1 to 1
 

Italian Production sites

you can find here the list of Italian sites.
Added:
>
>

How to enable igi.italiangrid.it VO

 

Notes about services from IGI middleware, based on EMI/UMD

These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation. This document is addressed to site administrators responsible for middleware installation and configuration.

Deleted:
<
<

How to join, enable and configure igi.italiangrid.it VO

VO igi.italiangrid.it

The goal of the VO is to provide access to the existing computing and storage resources of the Italian Grid Infrastructure, to individuals or groups who are new to the Grid, or whose experiment haven't an own VO yet. The VO identity card is available HERE

Users

How to join the VO igi.italiangrid.it

Users can join the VO at the HERE.

How to deploy software for the VO igi.italiangrid.it

To distribute users software to Grid sites supporting the VO igi.italiangrid.it, please send an email to info@lists.italiangrid.it.

Sites

How to enable and support the VO igi.italiangrid.it at your site

site-info.def

  • Add igi.italiangrid.it to VOS variable in your site-info.def. For example:
VOS="igi.italiangrid.it comput-er.it dteam glast.org infngrid ops gridit enmr.eu"

  • Add igi.italiangrid.it to the related queue settings inside the GROUP_ENABLE variable in your site-info.def. For example (we suppose to use ''prod'' queue):
PROD_GROUP_ENABLE="comput-er.it gridit igi.italiangrid.it

  • Create vo.d/igi.italiangrid.it file inside your site configuration directory.
$ cat <confdir>/vo.d/igi.italiangrid.it
SW_DIR=$VO_SW_DIR/igi
DEFAULT_SE=$SE_HOST
STORAGE_DIR=$CLASSIC_STORAGE_DIR/igi
VOMS_SERVERS="'vomss://vomsmania.cnaf.infn.it:8443/voms/igi.italiangrid.it?/igi.italiangrid.it'"
VOMSES="'igi.italiangrid.it vomsmania.cnaf.infn.it 15003 /C=IT/O=INFN/OU=Host/L=CNAF/CN=vomsmania.cnaf.infn.it igi.italiangrid.it'"
VOMS_CA_DN="'/C=IT/O=INFN/CN=INFN CA'"

users.conf

Add to your users.conf the users for the igi.italiangrid.it fitting your site's policy in users management (range of uid and gid). To find your users.conf:
# grep USERS_CONF site-info.def
site-info.def:USERS_CONF=/root/igi-siteinfo/ig-users.conf

As example, here a list of pool account:

# grep italiangrid /root/igi-siteinfo/ig-users.conf
3601:igi001:7400:igi:igi.italiangrid.it::
3602:igi002:7400:igi:igi.italiangrid.it::
3603:igi003:7400:igi:igi.italiangrid.it::
3604:igi004:7400:igi:igi.italiangrid.it::
3605:igi005:7400:igi:igi.italiangrid.it::
3606:igi006:7400:igi:igi.italiangrid.it::
3607:igi007:7400:igi:igi.italiangrid.it::
3608:igi008:7400:igi:igi.italiangrid.it::
3609:igi009:7400:igi:igi.italiangrid.it::
3610:igi010:7400:igi:igi.italiangrid.it::
3611:igi011:7400:igi:igi.italiangrid.it::
3612:igi012:7400:igi:igi.italiangrid.it::
3613:igi013:7400:igi:igi.italiangrid.it::
3614:igi014:7400:igi:igi.italiangrid.it::
3615:igi015:7400:igi:igi.italiangrid.it::
3616:igi016:7400:igi:igi.italiangrid.it::
3617:igi017:7400:igi:igi.italiangrid.it::
3618:igi018:7400:igi:igi.italiangrid.it::
3619:igi019:7400:igi:igi.italiangrid.it::
3620:igi020:7400:igi:igi.italiangrid.it::
3621:igi021:7400:igi:igi.italiangrid.it::
3622:igi022:7400:igi:igi.italiangrid.it::
3623:igi023:7400:igi:igi.italiangrid.it::
3624:igi024:7400:igi:igi.italiangigi:it::
3625:igi025:7400:igi:igi.italiangrid.it::
10161:sgmigi001:7450,7400:sgmigi,igi:igi.italiangrid.it:sgm:
10162:sgmigi002:7450,7400:sgmigi,igi:igi.italiangrid.it:sgm:
10163:sgmigi003:7450,7400:sgmigi,igi:igi.italiangrid.it:sgm:
10164:sgmigi004:7450,7400:sgmigi,igi:igi.italiangrid.it:sgm:
10165:sgmigi005:7450,7400:sgmigi,igi:igi.italiangrid.it:sgm:
Some useful informations are available in /opt/glite/yaim/examples/users.conf.README=

groups.conf

Add to groups.conf the VOMS FQANs for the igi.italiangrid.it VO. To find your groups.conf:
# grep GROUPS_CONF site-info.def
site-info.def:USERS_CONF=/root/igi-siteinfo/ig-groups.conf

# grep italiangrid /root/igi-siteinfo/ig-groups.conf 
"/igi.italiangrid.it/ROLE=SoftwareManager":::sgm:
"/igi.italiangrid.it"::::
"/igi.italiangrid.it/*"::::

Some useful informations are available in ''/opt/glite/yaim/examples/groups.conf.README''.

Configure your nodetypes

In order to enable the newly added "<voname>'' VO on your site you have to run for each nodetype the function you find in the table below. Naturally you can also complete reconfigure your nodetypes but this is a more expensive procedure.

For each nodetype you have to use the following command, properly replacing the profile and function's names:

/opt/glite/yaim/bin/yaim -r -s <confdir>/<your-site-info.def> -n <profile> -f <function>

Profiles Function
BDII Site ''config_newvo_bdii_site''
BDII Top ''config_newvo_bdii_top''
CREAM ''config_newvo_cream''
''config_newvo_cream_lsf''
''config_newvo_cream_torque''
GRIDFTP ''config_newvo_gridftp''
HLR ''config_newvo_hlr''
LB ''config_newvo_lb''
SE_DPM ''config_newvo_se_dpm_disk''
''config_newvo_se_dpm_mysql''
''config_newvo_se_dpm_oracle''
SE StoRM ''config_newvo_se_storm_backend''
''config_newvo_se_storm_frontend''
UI ''config_newvo_ui''
WMS ''config_newvo_wms''
WN ''config_newvo_wn''
''config_newvo_wn_lsf''
''config_newvo_wn_torque''

Configuring the Software Structure

TODO
 

Table about Installation and Configuration of Grid services EMI-2

The core services are those that are typically shared by multiple VOs and which interact with the resources made available at the Grid Site level. They should not be installed at Site level.

Revision 432012-08-09 - PaoloVeronesi

Line: 1 to 1
 

Italian Production sites

you can find here the list of Italian sites.
Line: 141 to 141
 
SITE service StoRM Storage Element (StoRM SE) TODO EMI-2
SITE/CORE service Home Location Register (HLR) TODO IGI
CORE service MyProxy Notes about MyProxy - EMI-2 - SL6 EMI-2 SL6
Changed:
<
<
CORE service top-bdii TODO EMI-2
>
>
CORE service top-bdii Notes about top-bdii - EMI-2 - SL6 EMI-2 SL6
 
CORE service Workload Management System (WMS) TODO EMI-2
CORE service Logging & Bookepping (LB) TODO EMI-2
CORE service LCG file Catalog (LFC) Notes about Installation and Configuration of EMI-2 (SL5) LFC server EMI-2 SL5

Revision 422012-08-09 - PaoloVeronesi

Line: 1 to 1
 

Italian Production sites

you can find here the list of Italian sites.
Line: 144 to 144
 
CORE service top-bdii TODO EMI-2
CORE service Workload Management System (WMS) TODO EMI-2
CORE service Logging & Bookepping (LB) TODO EMI-2
Changed:
<
<
CORE service LCG file Catalog (LFC) TODO EMI-2
>
>
CORE service LCG file Catalog (LFC) Notes about Installation and Configuration of EMI-2 (SL5) LFC server EMI-2 SL5
 
CORE service File Transfer Service (FTS) TODO EMI-2
CORE service VOMS Notes about Installation and Configuration of EMI2 VOMS-MySQL on SL6 EMI-2

Revision 412012-06-29 - PaoloVeronesi

Line: 1 to 1
Deleted:
<
<
 

Italian Production sites

Changed:
<
<
you can find here the list of Italian sites
>
>
you can find here the list of Italian sites.
 
Changed:
<
<

Notes about services from IGI middleware, based on EMI/UMD

>
>

Notes about services from IGI middleware, based on EMI/UMD

 These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation. This document is addressed to site administrators responsible for middleware installation and configuration.

Added:
>
>

How to join, enable and configure igi.italiangrid.it VO

VO igi.italiangrid.it

The goal of the VO is to provide access to the existing computing and storage resources of the Italian Grid Infrastructure, to individuals or groups who are new to the Grid, or whose experiment haven't an own VO yet. The VO identity card is available HERE

Users

How to join the VO igi.italiangrid.it

Users can join the VO at the HERE.

How to deploy software for the VO igi.italiangrid.it

To distribute users software to Grid sites supporting the VO igi.italiangrid.it, please send an email to info@lists.italiangrid.it.

Sites

How to enable and support the VO igi.italiangrid.it at your site

site-info.def

  • Add igi.italiangrid.it to VOS variable in your site-info.def. For example:
VOS="igi.italiangrid.it comput-er.it dteam glast.org infngrid ops gridit enmr.eu"

  • Add igi.italiangrid.it to the related queue settings inside the GROUP_ENABLE variable in your site-info.def. For example (we suppose to use ''prod'' queue):
PROD_GROUP_ENABLE="comput-er.it gridit igi.italiangrid.it

  • Create vo.d/igi.italiangrid.it file inside your site configuration directory.
$ cat <confdir>/vo.d/igi.italiangrid.it
SW_DIR=$VO_SW_DIR/igi
DEFAULT_SE=$SE_HOST
STORAGE_DIR=$CLASSIC_STORAGE_DIR/igi
VOMS_SERVERS="'vomss://vomsmania.cnaf.infn.it:8443/voms/igi.italiangrid.it?/igi.italiangrid.it'"
VOMSES="'igi.italiangrid.it vomsmania.cnaf.infn.it 15003 /C=IT/O=INFN/OU=Host/L=CNAF/CN=vomsmania.cnaf.infn.it igi.italiangrid.it'"
VOMS_CA_DN="'/C=IT/O=INFN/CN=INFN CA'"

users.conf

Add to your users.conf the users for the igi.italiangrid.it fitting your site's policy in users management (range of uid and gid). To find your users.conf:
# grep USERS_CONF site-info.def
site-info.def:USERS_CONF=/root/igi-siteinfo/ig-users.conf

As example, here a list of pool account:

# grep italiangrid /root/igi-siteinfo/ig-users.conf
3601:igi001:7400:igi:igi.italiangrid.it::
3602:igi002:7400:igi:igi.italiangrid.it::
3603:igi003:7400:igi:igi.italiangrid.it::
3604:igi004:7400:igi:igi.italiangrid.it::
3605:igi005:7400:igi:igi.italiangrid.it::
3606:igi006:7400:igi:igi.italiangrid.it::
3607:igi007:7400:igi:igi.italiangrid.it::
3608:igi008:7400:igi:igi.italiangrid.it::
3609:igi009:7400:igi:igi.italiangrid.it::
3610:igi010:7400:igi:igi.italiangrid.it::
3611:igi011:7400:igi:igi.italiangrid.it::
3612:igi012:7400:igi:igi.italiangrid.it::
3613:igi013:7400:igi:igi.italiangrid.it::
3614:igi014:7400:igi:igi.italiangrid.it::
3615:igi015:7400:igi:igi.italiangrid.it::
3616:igi016:7400:igi:igi.italiangrid.it::
3617:igi017:7400:igi:igi.italiangrid.it::
3618:igi018:7400:igi:igi.italiangrid.it::
3619:igi019:7400:igi:igi.italiangrid.it::
3620:igi020:7400:igi:igi.italiangrid.it::
3621:igi021:7400:igi:igi.italiangrid.it::
3622:igi022:7400:igi:igi.italiangrid.it::
3623:igi023:7400:igi:igi.italiangrid.it::
3624:igi024:7400:igi:igi.italiangigi:it::
3625:igi025:7400:igi:igi.italiangrid.it::
10161:sgmigi001:7450,7400:sgmigi,igi:igi.italiangrid.it:sgm:
10162:sgmigi002:7450,7400:sgmigi,igi:igi.italiangrid.it:sgm:
10163:sgmigi003:7450,7400:sgmigi,igi:igi.italiangrid.it:sgm:
10164:sgmigi004:7450,7400:sgmigi,igi:igi.italiangrid.it:sgm:
10165:sgmigi005:7450,7400:sgmigi,igi:igi.italiangrid.it:sgm:
Some useful informations are available in /opt/glite/yaim/examples/users.conf.README=

groups.conf

Add to groups.conf the VOMS FQANs for the igi.italiangrid.it VO. To find your groups.conf:
# grep GROUPS_CONF site-info.def
site-info.def:USERS_CONF=/root/igi-siteinfo/ig-groups.conf

# grep italiangrid /root/igi-siteinfo/ig-groups.conf 
"/igi.italiangrid.it/ROLE=SoftwareManager":::sgm:
"/igi.italiangrid.it"::::
"/igi.italiangrid.it/*"::::

Some useful informations are available in ''/opt/glite/yaim/examples/groups.conf.README''.

Configure your nodetypes

In order to enable the newly added "<voname>'' VO on your site you have to run for each nodetype the function you find in the table below. Naturally you can also complete reconfigure your nodetypes but this is a more expensive procedure.

For each nodetype you have to use the following command, properly replacing the profile and function's names:

/opt/glite/yaim/bin/yaim -r -s <confdir>/<your-site-info.def> -n <profile> -f <function>

Profiles Function
BDII Site ''config_newvo_bdii_site''
BDII Top ''config_newvo_bdii_top''
CREAM ''config_newvo_cream''
''config_newvo_cream_lsf''
''config_newvo_cream_torque''
GRIDFTP ''config_newvo_gridftp''
HLR ''config_newvo_hlr''
LB ''config_newvo_lb''
SE_DPM ''config_newvo_se_dpm_disk''
''config_newvo_se_dpm_mysql''
''config_newvo_se_dpm_oracle''
SE StoRM ''config_newvo_se_storm_backend''
''config_newvo_se_storm_frontend''
UI ''config_newvo_ui''
WMS ''config_newvo_wms''
WN ''config_newvo_wn''
''config_newvo_wn_lsf''
''config_newvo_wn_torque''

Configuring the Software Structure

TODO
 

Table about Installation and Configuration of Grid services EMI-2

The core services are those that are typically shared by multiple VOs and which interact with the resources made available at the Grid Site level. They should not be installed at Site level.

Revision 402012-06-12 - PaoloVeronesi

Line: 1 to 1
 

Italian Production sites

Line: 23 to 23
 
SITE service site-bdii Notes about site-bdii EMI-2 SL6 EMI-2 SL6
SITE service StoRM Storage Element (StoRM SE) TODO EMI-2
SITE/CORE service Home Location Register (HLR) TODO IGI
Changed:
<
<
CORE service MyProxy TODO EMI-2
>
>
CORE service MyProxy Notes about MyProxy - EMI-2 - SL6 EMI-2 SL6
 
CORE service top-bdii TODO EMI-2
CORE service Workload Management System (WMS) TODO EMI-2
CORE service Logging & Bookepping (LB) TODO EMI-2

Revision 392012-06-04 - AlessandroPaolini

Line: 1 to 1