|
META TOPICPARENT |
name="IGIGuides" |
IGI (based on EMI) Installation and Configuration |
| 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 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. |
|
> > |
Directory<-- --> |
Scope |
Details |
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. |
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. |
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. |
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. |
|
|
The optional folders are created to allow system administrators to organise their configurations in a more structured way.” |
|
To proper configure the BDII top profile you have to customize this file with you site parameter: |
|
< < | - ig-site-info.def |
> > | |
|
YAIM Verification |
|
To proper configure the StoRM BackEnd and FrontEnd profiles you have to customize the ig-site-indo.def file with you site parameter: |
|
< < | - ig-site-info.def
- ig-users.conf
- ig-groups.conf |
> > | |
|
YAIM Verification |
|
Host certificate installation: |
|
< < | All nodes except UI, WN and BDII require the host certificate/key files to be installed. Contact your national Certification Authority (CA) to understand how to obtain a host certificate if you do not have one already. |
> > | All nodes except UI, WN and BDII require the host certificate/key files to be installed.
Contact your national Certification Authority (CA) to understand how to obtain a host certificate if you do not have one already. |
|
Once you have obtained a valid certificate: |
| yum install emi-torque-utils
|
|
< < | * If you are running Torque, and your CREAM CE node is NOT the torque master, install the emi-torque-utils metapackage: |
> > |
- If you are running Torque, and your CREAM CE node is NOT the torque master, install the emi-torque-utils metapackage:
|
|
yum install emi-torque-utils
|
| USE_ARGUS=no
|
|
< < | DGAS_sensors:
|
> > | DGAS_sensors: |
| For DGAS_sensors you should customize the services file. You can find in this path an example:
/opt/glite/yaim/examples/siteinfo/services/dgas_sensors |
|
< < | |
| YAIM Configuration
Please use the debug flag ( "-d 6" ) to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog default one. |
|
Install the WN metapackages, containing all packages needed. Have a look to the WN documentation before starting to install: WN Guides.
IGI provides 5 custom profiles (metapackages) one for each specific batch system used in your cluster. Please use one of theese: |
|
< < |
- igi-wn_torque
- igi-wn_torque_noafs
- igi-wn_lsf
- igi-wn_lsf_noafs
- igi-wn (useful for SGE or other Batch System)
|
> > |
Profiles |
Metapackages INSTALLATION |
Nodetypes CONFIGURATION |
WN |
igi-wn igi-wn_lsf igi-wn_lsf_noafs igi-wn_torque igi-wn_torque_noafs |
WN WN_LSF WN_LSF_noafs WN_torque WN_torque_noafs |
Note: the igi-wn metapackage is useful for SGE or other Batch System |
|
yum install <metapackage>
|
|
< < | IMPORTANT NOTE:
All the metapackages name are case sensitive, you have to write it as described above. |
> > |
IMPORTANT NOTE: |
All the metapackages name are case sensitive, you have to write it as described above. |
|
|
IMPORTANT NOTE FOR TORQUE:
After the Torque installation you should have the version 2.5.7-7. Please remember to copy the munge key from the batch master to the WN just installed |
|
Please use the debug flag ( "-d 6" ) to configure the services in order to have detailed information. For your convenience yo can save all the configuration information in a log file you can look at any time, separated from the yaimlog default one. |
|
< < | IMPORTANT NOTE:
All the profiles name are case sensitive, you have to write it as described above. |
> > |
IMPORTANT NOTE: |
All the nodetypes name are case sensitive, you have to write it as described above. |
|
|
For Torque:
/opt/glite/yaim/bin/yaim -c -d 6 -s <site-info.def> -n WN_torque 2>&1 | tee /root/conf_WN_torque.`hostname -s`.`date`.log |