Line: 1 to 1 | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
Changed: | |||||||||
< < | IGI gLite 3.2 Update 32/33/34/35 (SL5/x86_64) - WORK IN PROGRESS | ||||||||
> > | IGI gLite 3.2 Update 32/33/34/35 (SL5/x86_64) - 10/02/2012 | ||||||||
In this IGI update we take just a subset of profiles from the gLite 3.2 release. In particular:
| |||||||||
Line: 12 to 12 | |||||||||
NOTES (read before you start) | |||||||||
Changed: | |||||||||
< < | VERY IMPORTANT NOTE:
Due to conflicts between new and old versions of various packages the repository ''glite-generic'' should be disabled:
# mv /etc/yum.repos.d/glite-generic.repo /etc/yum.repos.d/glite-generic.repo.disabled # yum clean allOne of the main consequences of having the same packages but with different versions in repositories for different services/node-types is that the installation/configuration of two or more profiles/node-types on the same machine is no more supported!!! | ||||||||
> > |
| ||||||||
Changed: | |||||||||
< < | MAIN NEWS: | ||||||||
> > | NEWS | ||||||||
Changed: | |||||||||
< < |
| ||||||||
> > |
| ||||||||
| |||||||||
Added: | |||||||||
> > |
| ||||||||
| |||||||||
Line: 54 to 57 | |||||||||
| |||||||||
Added: | |||||||||
> > |
| ||||||||
Prerequisites | |||||||||
Line: 71 to 78 | |||||||||
| |||||||||
Changed: | |||||||||
< < |
| ||||||||
> > |
| ||||||||
| |||||||||
Line: 97 to 104 | |||||||||
| |||||||||
Changed: | |||||||||
< < |
| ||||||||
> > |
| ||||||||
| |||||||||
Changed: | |||||||||
< < |
| ||||||||
> > |
| ||||||||
Actions | |||||||||
Line: 117 to 124 | |||||||||
# yum install <node-type> | |||||||||
Changed: | |||||||||
< < | Please remember that on case of WN you should use the "groupinstall", for ex.: | ||||||||
> > | Please remember that on case of WN (ALL WNs) you should use the "groupinstall", for ex.: | ||||||||
yum groupinstall ig_WN_torque | |||||||||
Changed: | |||||||||
< < | On CE CREAM: | ||||||||
> > |
| ||||||||
Changed: | |||||||||
< < | Before installing/updating a CREAM CE remember to install xml-commons-apis: | ||||||||
> > |
| ||||||||
yum update xml-commons-apis | |||||||||
Changed: | |||||||||
< < | When installing/updating a CREAM CE node, a dependency problem such as: Error: Missing Dependency: libcares.so.0()(64bit) is needed by package glite-security-gss-2.0.0-6.sl5.x86_64 could be seen. In this case, the update should be done doing: | ||||||||
> > |
Error: Missing Dependency: libcares.so.0()(64bit) is needed by package glite-security-gss-2.0.0-6.sl5.x86_64can be seen. In this case, the update should be done doing: | ||||||||
yum update --exclude=c-aresPlease note that doing: yum update ig-CREAM_torqueor yum update ig-CREAM_LSFyou are not guaranteed to have all relevant RPMs updated. | |||||||||
Changed: | |||||||||
< < | When installing/updating ig_CREAM_torque (in general torque) remember to change the torque directory On the Batch Server (usually CREAM CE host) | ||||||||
> > |
| ||||||||
Changed: | |||||||||
< < | /usr/sbin/create-munge-key scp /etc/munge/munge.key <all cluster node> service munge start chkconfig munge on | ||||||||
> > | # /etc/init.d/pbs_server stop # mv /var/spool/pbs /var/torque # ln -s /var/torque /var/spool/pbs # /etc/init.d/pbs_server start | ||||||||
Changed: | |||||||||
< < | |||||||||
> > |
| ||||||||
Added: | |||||||||
> > |
Install the munge package on your pbs_server and submission hosts in your cluster. On one host generate a key with /usr/sbin/create-munge-key Copy the key, /etc/munge/munge.key to your pbs_server and submission hosts on your cluster. Start the munge daemon on these nodes.. service munge start && chkconfig munge onBriefly, you should execute: # /usr/sbin/create-munge-key # scp /etc/munge/munge.key <all cluster node> # service munge start # chkconfig munge on | ||||||||
Editing local configuration files | |||||||||
Changed: | |||||||||
< < | * In the last updates many variables have been changed or moved to ''services'' and ''defaults'' directories. Please carefully check your ''<site-info.def>'' and files under ''services/'' and ''nodes/'' directories comparing to the new ones distributed with latest released ''yaim'' modules. For example you can use ''vimdiff'' like here below: | ||||||||
> > |
| ||||||||
| |||||||||
Changed: | |||||||||
< < | vimdiff /opt/glite/yaim/examples/siteinfo/ig-site-info.def <site-info.def> | ||||||||
> > | # vimdiff /opt/glite/yaim/examples/siteinfo/ig-site-info.def <site-info.def> | ||||||||
Added: | |||||||||
> > |
| ||||||||
You may find more detailed information on configuration files structure here: | |||||||||
Line: 164 to 197 | |||||||||
Nodetype reconfiguration | |||||||||
Changed: | |||||||||
< < |
IMPORTANT: | ||||||||
> > |
| ||||||||
For any details please refer to the reference "IGI YAIM configuration files” | |||||||||
Line: 171 to 206 | |||||||||
For any details please refer to the reference "IGI YAIM configuration files” | |||||||||
Deleted: | |||||||||
< < | |||||||||
| |||||||||
Deleted: | |||||||||
< < | IMPORTANT: | ||||||||
/opt/glite/yaim/bin/ig_yaim -c -s <site-info.def> -n <nodetype> | |||||||||
Changed: | |||||||||
< < | Where '' | ||||||||
> > | Where | ||||||||
Middleware services restart | |||||||||
Changed: | |||||||||
< < | Look at your ''chkconfig'' services list and restart all middleware-related service: | ||||||||
> > | Look at your chkconfig services list and restart all middleware-related service: | ||||||||
chkconfig --list | grep 3:on | sort | |||||||||
Line: 201 to 227 | |||||||||
service <middleware-service> restart | |||||||||
Deleted: | |||||||||
< < | -- SergioTraldi - 2012-02-01 | ||||||||
\ No newline at end of file |