Difference: IgiGlite (2 vs. 3)

Revision 32011-11-10 - SergioTraldi

Line: 1 to 1

META TOPICPARENT	name="IGIGuides"

IGI (based on gLite 3.2 release) Installation and Configuration

Line: 47 to 47

Each profile needs a set of common repositories:

Common repositories x86_64

Changed:

<
<

dag.repo

ig.repo

egi-trustanchors.repo

>
>

dag.repo

ig.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.

Line: 57 to 57

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

Changed:

<
<

ig_ARGUS	glite-argus.repo
ig_BDII_top	glite-bdii_top.repo
ig_BDII_site	glite-bdii_site.repo
ig_CREAM ig_CREAM_LSF	glite-cream.repo
ig_CREAM_torque	glite-cream_torque.repo
ig_FTA_oracle	glite-fta_oracle.repo
ig_FTM	glite-ftm.repo
ig_FTS_oracle	glite-fts_oracle.repo
ig_GLEXEC_wn	glite-glexec.repo
ig_HLR	glite-generic.repo
ig_LB	glite-lb.repo
ig_LFC_mysql	glite-lfc_mysql.repo
ig_SE_dpm_mysql	glite-se_dpm_mysql.repo
ig_SE_dcache_info	glite-se_dcache_info.repo
ig_SE_dcache_nameserver_chimera	glite-se_dcache_nameserver.repo
ig_SE_dcache_pool	glite-se_dcache_pool.repo
ig_SE_dcache_srm	glite-se_dcache_srm.repo
ig_SE_storm_backend ig_SE_storm_frontend ig_SE_storm_checksum	ig-storm.repo
ig_SE_storm_gridftp	ig-storm_gridftp.repo
ig_UI ig_UI_noafs	glite-ui.repo
ig_VOBOX	glite-vobox.repo
ig_VOMS_mysql	glite-voms_mysql.repo
ig_VOMS_oracle	glite-voms_oracle.repo
ig_WN, ig_WN_noafs ig_WN_LSF, ig_WN_LSF_noafs	glite-wn.repo
ig_WN_torque, ig_WN_torque_noafs	glite-wn_torque.repo

>
>

ig_ARGUS	glite-argus.repo
ig_BDII_top	glite-bdii_top.repo
ig_BDII_site	glite-bdii_site.repo
ig_CREAM ig_CREAM_LSF	glite-cream.repo
ig_CREAM_torque	glite-cream_torque.repo
ig_FTA_oracle	glite-fta_oracle.repo
ig_FTM	glite-ftm.repo
ig_FTS_oracle	glite-fts_oracle.repo
ig_GLEXEC_wn	glite-glexec.repo
ig_HLR	glite-generic.repo
ig_LB	glite-lb.repo
ig_LFC_mysql	glite-lfc_mysql.repo
ig_SE_dpm_mysql	glite-se_dpm_mysql.repo
ig_SE_dcache_info	glite-se_dcache_info.repo
ig_SE_dcache_nameserver_chimera	glite-se_dcache_nameserver.repo
ig_SE_dcache_pool	glite-se_dcache_pool.repo
ig_SE_dcache_srm	glite-se_dcache_srm.repo
ig_SE_storm_backend ig_SE_storm_frontend ig_SE_storm_checksum	ig-storm.repo
ig_SE_storm_gridftp	ig-storm_gridftp.repo
ig_UI ig_UI_noafs	glite-ui.repo
ig_VOBOX	glite-vobox.repo
ig_VOMS_mysql	glite-voms_mysql.repo
ig_VOMS_oracle	glite-voms_oracle.repo
ig_WN, ig_WN_noafs ig_WN_LSF, ig_WN_LSF_noafs	glite-wn.repo
ig_WN_torque, ig_WN_torque_noafs	glite-wn_torque.repo

Then update your host:

yum clean all

Line: 110 to 110

Configuration

Added:

>
>

Configuration files

<-- including doc:guides:yaim-configuration-files // /var/lib/gforge/chroot/home/groups/igrelease/htdocs/data/pages/doc/guides/yaim-configuration-files.txt -->

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 <confdir>, in a safe place, which is not world readable. This directory should contain:

File	Scope	Details
`<your-site-info.def>`	whole-site	List of configuration variables in the format of key-value pairs. It's a mandatory file. It's a parameter passed to the `ig_yaim` command. IMPORTANT: You should always check if your `<your-site-info.def>` 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. For example you may use `vimdiff`: vimdiff /opt/glite/yaim/examples/siteinfo/ig-site-info.def <confdir>/<your-site-info.def>
`<your-wn-list.conf>`	whole-site	Worker nodes list in the format of `hostname.domainname` per row. It's a mandatory file. It's defined by `WN_LIST` variable in `<your-site-info.def>`.
`<your-users.conf>`	whole-site	Pool account user mapping. It's a mandatory file. It's defined by `USERS_CONF` variable in `<your-site-info.def>`. IMPORTANT: You may create `<your-users.conf>` 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: ”Whole site: How to create local users.conf and configure users”.
`<your-groups.conf>`	whole-site	VOMS group mapping. It's a mandatory file. It's defined by `GROUPS_CONF` variable in `<your-site-info.def>`. IMPORTANT: You may create `<your-groups.conf>` 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`. The file contains a list of configuration variables specific to that nodetype. Each yaim module distributes a configuration file in `/opt/glite/yaim/examples/siteinfo/services/[ig`	glite]-node-type. It's a mandatory directory if required by the profile and you should copy it under the same directory where <your-site-info.def> is.
`nodes/`	host-specific	It contains a file per host with the name format: `hostname.domainname`. The file contains host specific variables that are different from one host to another in a certain site. 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 ”`lights.infn.it`”: # cat vo.d/lights.infn.it SW_DIR=$VO_SW_DIR/lights DEFAULT_SE=$SE_HOST VOMS_SERVERS="vomss://voms2.cnaf.infn.it:8443/voms/lights.infn.it?/lights.infn.it" 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" It's an optional directory for “normal” VOs (like atlas, alice, babar), mandatory only for “fqdn-like” VOs. In case you support such VOs you should copy the structure vo.d/<vo.specific.file> under the same directory where <your-site-info.def> is.
`group.d/`	VO-specific	It contains a file per VO with the name format: `groups-<vo_name>.conf`. The file contains VO specific groups and it replaces the former `<your-groups.conf>` file where all the VO groups were specified all together. It's an optional directory.

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

IMPORTANT NOTE:
If your site has the intention to support more VOs than the default ones, you should have a look at ”Whole site: How to enable a VO”, specially for the enmr.eu VO, once the configuration finished you should follow ”extra_configuration”.

-- CristinaAiftimiei - 2011-11-10

View topic | History: r12 < r11 < r10 < r9 | More topic actions...