(r7) IgiGlite < IGIRelease

Tags: , view all tags
---+ IGI (based on gLite 3.2 release) Installation and Configuration

%TOC%
---++ *Installation*

---+++ OS installation

Install SL5 using [[http://linuxsoft.cern.ch/scientific/5x/][ SL5.X repository (CERN mirror)]] or one of the supported <acronym title="Operating System">OS</acronym> (RHEL5 clones).

You may find information on official repositories at [http://igrelease.forge.cnaf.infn.it/doku.php?id=doc:tips:repos][Repositories for APT and YUM]] <br /> If you want to set up a local installation server please refer to [[http://igrelease.forge.cnaf.infn.it/doku.php?id=doc:tips:mrepo][Mrepo Quick Guide]]

*NOTE*: Please check if <em> =NTP= </em>, <em> =cron= </em> and <em> =logrotate= </em> are installed, otherwise install them!

---++++ Check the FQDN hostname

Ensure that the hostnames of your machines are correctly set. Run the command:
<pre> hostname -f</pre>

It should print the fully qualified domain name (e.g. =prod-ce.mydomain.it=). Correct your network configuration if it prints only the hostname without the domain. If you are installing WN on private network the command must return the external FQDN for the CE and the SE (e.g. =prod-ce.mydomain.it=) and the internal FQDN for the WNs (e.g. =node001.myintdomain=).
---+++ 
---+++ Repository Settings

To have more details to the repository have a look to the this link [[http://wiki.italiangrid.org/twiki/bin/view/IGIRelease/RepositoriesSpecifications][Repository Specifications]]

With standard installation of SL5 it's possible that you have the EPEL repository enabled. Please disable it:
<pre># mv /etc/yum.repos.d/epel.repo /etc/yum.repos.d/epel.repo.disabled
</pre>

otherwise you'll get the following error:
<pre>Missing Dependency: libcares.so.0()(64bit) is needed by package glite-security-gss-2.0.0-3.sl5.x86_64 (glite-generic_sl5_x86_64_release)
</pre>

because of the presence of newer version of c-ares (1.4.0-1.el5). The middleware needs the 1.3.0-4.sl5 !

Remeber to enabled the dag.repo :

With standard installation of SL5 it's possible that you have the DAG repository. Please check if it is enabled, if no please enabled it:

cat /etc/yum.repos.d/dag.repo

.... enabled=1 ....

---++++ Common repositories

Each profile needs a set of common repositories:

| *Common repositories *x86_64** |
| [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/dag.repo][dag.repo]] |
| [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/ig.repo][ig.repo]] |
| [[http://repo-pd.italiangrid.it/mrepo/repos/egi-trustanchors.repo][egi-trustanchors.repo]] |

In order to have a working IGI service you have to download also the gLite repo files. In the table bellow you'll find the match from metapackages to profiles.

---++++ Profile-specific repositories

Furthermore each profile needs a set of repositories that contain the profile-related middleware. Look at the table below to know what specific repositories your profile needs:
| *Metapackages* | *Profile-specific repositories *x86_64** |
| ig_ARGUS | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-argus.repo][glite-argus.repo]] |
| ig_BDII_top | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-bdii_top.repo][glite-bdii_top.repo]] |
| ig_BDII_site | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-bdii_site.repo][glite-bdii_site.repo]] |
| ig_CREAM <br /> ig_CREAM_LSF | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-cream.repo][glite-cream.repo]] |
| ig_CREAM_torque | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-cream_torque.repo][glite-cream_torque.repo]] |
| ig_FTA_oracle | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-fta_oracle.repo][glite-fta_oracle.repo]] |
| ig_FTM | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-ftm.repo][glite-ftm.repo]] |
| ig_FTS_oracle | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-fts_oracle.repo][glite-fts_oracle.repo]] |
| ig_GLEXEC_wn | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-glexec.repo][glite-glexec.repo]] |
| ig_HLR | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-generic.repo][glite-generic.repo]] |
| ig_LB | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-lb.repo][glite-lb.repo]] |
| ig_LFC_mysql | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-lfc_mysql.repo][glite-lfc_mysql.repo]] |
| ig_SE_dpm_mysql | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-se_dpm_mysql.repo][glite-se_dpm_mysql.repo]] |
| ig_SE_dcache_info | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-se_dcache_info.repo][glite-se_dcache_info.repo]] |
| ig_SE_dcache_nameserver_chimera | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-se_dcache_nameserver.repo][glite-se_dcache_nameserver.repo]] |
| ig_SE_dcache_pool | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-se_dcache_pool.repo][glite-se_dcache_pool.repo]] |
| ig_SE_dcache_srm | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-se_dcache_srm.repo][glite-se_dcache_srm.repo]] |
| ig_SE_storm_backend <br /> ig_SE_storm_frontend <br /> ig_SE_storm_checksum | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/ig-storm.repo][ig-storm.repo]] |
| ig_SE_storm_gridftp | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/ig-storm_gridftp.repo][ig-storm_gridftp.repo]] |
| ig_UI <br /> ig_UI_noafs | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-ui.repo][glite-ui.repo]] |
| ig_VOBOX | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-vobox.repo][glite-vobox.repo]] |
| ig_VOMS_mysql | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-voms_mysql.repo][glite-voms_mysql.repo]] |
| ig_VOMS_oracle | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-voms_oracle.repo][glite-voms_oracle.repo]] |
| ig_WN, ig_WN_noafs<strong> <br /> </strong>ig_WN_LSF, ig_WN_LSF_noafs | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-wn.repo][glite-wn.repo]] |
| ig_WN_torque, ig_WN_torque_noafs | [[http://repo-pd.italiangrid.it/mrepo/repos/glite/sl5/x86_64/glite-wn_torque.repo][glite-wn_torque.repo]] |

Then update your host:
<pre>yum clean all
</pre>

---+++ CAa installation:

Install CAs on ALL profiles:
<pre>yum install ca-policy-egi-core
</pre>

---+++ Metapackage installation

Please consider that x86_64 WN profiles has to be installed using the &ldquo;groupinstall&rdquo; yum command as follows:
<pre> yum groupinstall &lt;WN_profile&gt;  </pre>

where &lt;WN_profile&gt; could be one of: ig_WN, ig_WN_noafs, ig_WN_torque, ig_WN_torque_noafs, ig_WN_LSF, ig_WN_LSF_noafs or
<pre> yum groupinstall &lt;UI_profile&gt;  </pre>

where &lt;UI_profile&gt; could be one of: ig_UI, ig_UI_noafs

If you are installing any othere profiles use:
<pre> yum install &lt;metapackage&gt; </pre>

Where =&lt;metapackage&gt;= is one of those reported on the table above ( _Metapackages_ column).

---++ *Configuration*

---+++  Configuration files 
---++++  INFNGRID YAIM configuration files  

YAIM configuration files should be stored in a _directory structure_. All the involved files *HAVE* to be under the same folder =&lt;confdir&gt;=, in a safe place, which *is not world readable*. This directory should contain:
| *File* | *Scope* | *Details* |
| =&lt;your-site-info.def&gt;= | *whole-site* | List of configuration variables in the format of key-value pairs. <br /> It's a *mandatory* file. <br /> It's a parameter passed to the =ig_yaim= command. <br /> *IMPORTANT*: You should always check if your =&lt;your-site-info.def&gt;= is up-to-date comparing with the last =/opt/glite/yaim/examples/siteinfo/ig-site-info.def= template deployed with =ig-yaim= and get the differences you find. <br /> For example you may use =vimdiff=: <pre>vimdiff /opt/glite/yaim/examples/siteinfo/ig-site-info.def &lt;confdir&gt;/&lt;your-site-info.def&gt;</pre> |
| =&lt;your-wn-list.conf&gt;= | *whole-site* | Worker nodes list in the format of =hostname.domainname= per row. <br /> It's a *mandatory* file. <br /> It's defined by =WN_LIST= variable in =&lt;your-site-info.def&gt;=. |
| =&lt;your-users.conf&gt;= | *whole-site* | Pool account user mapping. <br /> It's a *mandatory* file. <br /> It's defined by =USERS_CONF= variable in =&lt;your-site-info.def&gt;=. <br /> *IMPORTANT*: You may create =&lt;your-users.conf&gt;= starting from the =/opt/glite/yaim/examples/ig-users.conf= template deployed with =ig-yaim=, but probably you have to fill it on the base of your site policy on uids/guis. We suggest to proceed as explained here: _&rdquo;<a href="http://igrelease.forge.cnaf.infn.it/doku.php?id=doc:use_cases:users" title="doc:use_cases:users">Whole site: How to create local users.conf and configure users</a>&rdquo;_. |
| =&lt;your-groups.conf&gt;= | *whole-site* | VOMS group mapping. <br /> It's a *mandatory* file. <br /> It's defined by =GROUPS_CONF= variable in =&lt;your-site-info.def&gt;=. <br /> *IMPORTANT*: You may create =&lt;your-groups.conf&gt;= starting from the =/opt/glite/yaim/examples/ig-groups.conf= template deployed with =ig-yaim=. |
---++++  Additional files 

Furthermore the configuration folder can contain:
| *Directory* | *Scope* | *Details* ||
| =services/= | *service-specific* | It contains a file per nodetype with the name format: =ig-node-type=. <br /> The file contains a list of configuration variables specific to that nodetype.<br /> Each yaim module distributes a configuration file in =/opt/glite/yaim/examples/siteinfo/services/[ig or glite]-node-type. <br /> It's a *mandatory* directory if required by the profile and *you should copy it* under the same directory where &lt;your-site-info.def&gt; is. | |
| =nodes/= | *host-specific* | It contains a file per host with the name format: =hostname.domainname=. <br /> The file contains host specific variables that are different from one host to another in a certain site. <br /> It's an *optional* directory. ||
| =vo.d/= | *VO-specific* | It contains a file per VO with the name format: =vo_name=, but most of VO settings are still placed in =ig-site-info.def= template. For example, for &rdquo;<code>lights.infn.it</code>&rdquo;: <pre># cat vo.d/lights.infn.it<br />SW_DIR=$VO_SW_DIR/lights<br />DEFAULT_SE=$SE_HOST<br />VOMS_SERVERS="vomss://voms2.cnaf.infn.it:8443/voms/lights.infn.it?/lights.infn.it"<br />VOMSES="lights.infn.it voms2.cnaf.infn.it 15013 /C=IT/O=INFN/OU=Host/L=CNAF/CN=voms2.cnaf.infn.it lights.infn.it"</pre> <p>It's an *optional* directory for &ldquo;normal&rdquo; VOs (like atlas, alice, babar), *mandatory* only for &ldquo;fqdn-like&rdquo; VOs. In case you support such VOs *you should copy* the structure vo.d/&lt;vo.specific.file&gt; under the same directory where &lt;your-site-info.def&gt; is.</p> ||
| =group.d/= | *VO-specific* | It contains a file per VO with the name format: =groups-&lt;vo_name&gt;.conf=. <br /> The file contains VO specific groups and it replaces the former =&lt;your-groups.conf&gt;= file where all the VO groups were specified all together. <br /> It's an *optional* directory. ||

The optional folders are created to allow system administrators to organise their configurations in a more structured way.&rdquo;

*IMPORTANT NOTE:* <br /> If your site has the intention to support more VOs than the default ones, you should have a look at _&rdquo;<a href="http://igrelease.forge.cnaf.infn.it/doku.php?id=doc:use_cases:enabling-vo" title="doc:use_cases:enabling-vo">Whole site: How to enable a VO</a>&rdquo;_, specially for the *enmr.eu* VO, once the configuration finished you should follow _&rdquo;<a href="http://igrelease.forge.cnaf.infn.it/doku.php?id=doc:use_cases:enabling-vo#extra_configuration" title="doc:use_cases:enabling-vo">extra_configuration</a>&rdquo;_.
Topic revision: r7 - 2012-01-13 - SergioTraldi
Account
- Log In
~~Edit~~
~~Attach~~