Difference: IgiGlite (3 vs. 4)

Revision 42011-11-10 - SergioTraldi

Line: 1 to 1

META TOPICPARENT	name="IGIGuides"

IGI (based on gLite 3.2 release) Installation and Configuration

Line: 110 to 110

Configuration

Changed:

<
<

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

>
>

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

File	Scope	Details

Line: 121 to 120

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

Changed:

<
<

Additional files

>
>

Additional files

Furthermore the configuration folder can contain:

Directory	Scope	Details

Changed:

<
<

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

>
>

`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 or 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.

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