NTP
, cron
and logrotate
are installed, otherwise install them!
hostname -fIt 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
).
[extras] name=epel mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-5&arch=$basearch protect=0IMPORTANT NOTE If present remember to disable the dag.repo if it is enabled. You need to have enabled only the above repositories (Operating System, EPEL, Certification Authority, EMI):
Common repositories *x86_64* |
---|
epel.repo |
emi.repo |
egi-trustanchors.repo |
File | Scope | Example | Details |
---|---|---|---|
<your-site-info.def> |
whole-site | ig-site-info.def | 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-users.conf> |
whole-site | ig-users.conf | 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: ”<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>”. |
<your-groups.conf> |
whole-site | ig-groups.conf | 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. |
<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>. |
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 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. |
yum clean all
yum install ca-policy-egi-core
yum install emi-bdii-site
/opt/glite/yaim/examples/siteinfo/services/glite-bdii_site
/opt/glite/yaim/bin/yaim -v -s <site-info.def> -n BDII_siteThe mandatory variabiles are: SITE_DESC
SITE_OTHER_GRID="WLCG|EGI" SITE_OTHER_EGI_NGI="NGI_IT"If no errors occurred in the test you can proceed to the configuration.
/opt/glite/yaim/bin/yaim -c -d 6 -s -n BDII_site 2>&1 | tee /root/conf_BDII.`hostname -s`.`date +m%d-M%S`.log-- SergioTraldi - 2011-11-10