Difference: Update32-35 (5 vs. 6)

Revision 62012-02-10 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="IgiGliteUpdates"
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:
  • CREAM CE
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 all

One 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!!!

>
>
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 all
One 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:
<
<
  • CREAM - This patch provides:
>
>
MAIN NEWS:
  • CREAM - Version 3.2.14-1 provides:
 
    • an updated BLAH to address some problems when SGE is used as batch system in the CREAM CE
      • Known issues (details)
        • First time that run BUpdaterSGE after a long time, if there are a lot of jobs in non final state (removed or completed) in the job registry, many hours can be required to synchronize BUpdaterSGE daemon with the actual status, because a qstat of every pending job is needed.
    • a fix in the glite-security-lcmaps-plugins-verify-proxy package. The fix addresses a problem affecting users holding a Terena grid certificate when they submit to CREAM through WMS.
Added:
>
>
 
  • UI - Version 3.2.11 of the glite-UI - it includes the following changes:
    • GFAL/lcg_utils has been updated to version 1.11.16-3. (patch #4642). Amongst other fixes this version avoids the generation of debug log files
Line: 54 to 57
 

Added:
>
>
  • ig-yaim - version 4.0.14-11
    • ig-site-info.def - updating magic and superb.vo (tkt #12746)
    • ig-groups.conf - updating group information for various VOs, eliminating wildcards (tkt #12771)

 

Prerequisites

Line: 71 to 78
 
Package Version
Changed:
<
<
ig-metapackages ig26_sl5
ig-yaim 4.0.14-7
>
>
ig-metapackages ig27_sl5
ig-yaim 4.0.14-11
 
ig-yaim-core 4.0.14-1

Line: 97 to 104
 
Profiles Metapackages INSTALLATION Nodetypes CONFIGURATION Service restart Partial reconf Total reconf Actions Notes
Changed:
<
<
CREAM ig_CREAM
ig_CREAM_LSF
ig_CREAM_torque
ig_CREAM
ig_CREAM_LSF
ig_CREAM_torque
X - X Metapackage update
Nodetype_reconfiguration
Middleware_services_restart
-
>
>
CREAM ig_CREAM
ig_CREAM_LSF
ig_CREAM_torque
ig_CREAM
ig_CREAM_LSF
ig_CREAM_torque
X - X Metapackage update
Nodetype_reconfiguration
Middleware_services_restart
Pay atention to torque details
 
UI ig_UI
ig_UI_noafs
ig_UI
ig_UI_noafs
- - X Metapackage update
Nodetype_reconfiguration
-
Changed:
<
<
WN ig_WN
ig_WN_noafs
ig_WN_LSF
ig_WN_LSF_noafs
ig_WN_torque
ig_WN_torque_noafs
ig_WN
ig_WN_noafs
ig_WN_LSF
ig_WN_LSF_noafs
ig_WN_torque
ig_WN_torque_noafs
- - X Metapackage update
Nodetype_reconfiguration
-
>
>
WN ig_WN
ig_WN_noafs
ig_WN_LSF
ig_WN_LSF_noafs
ig_WN_torque
ig_WN_torque_noafs
ig_WN
ig_WN_noafs
ig_WN_LSF
ig_WN_LSF_noafs
ig_WN_torque
ig_WN_torque_noafs
- - X Metapackage update
Nodetype_reconfiguration
Pay atention to torque details
 

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:
>
>
On CE CREAM
 
Changed:
<
<
Before installing/updating a CREAM CE remember to install xml-commons-apis:
>
>
  • 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:
>
>
  • 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
can be seen. In this case, the update should be done doing:
 
 yum update --exclude=c-ares 
Please note that doing:
 yum update ig-CREAM_torque 
or
 yum update ig-CREAM_LSF 
you 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)

>
>
  • When installing/updating ig_CREAM_torque (in general torque node-types) remember to change the torque directory, if not already done:
 

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:
<
<
>
>
New versions of torque-* packages require actions before configuring
 
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 on
Briefly, 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:
>
>
  • 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:
>
>
Important Note
Remember to add the variable TORQUE_VAR_DIR in services and change the BATCH_LOG_DIR in ig-site-info.def to /var/torque
 You may find more detailed information on configuration files structure here:
Line: 164 to 197
 

Nodetype reconfiguration
Changed:
<
<
IMPORTANT: /services directory

Please ensure that you have all the NEEDED configuration files under your ''/services'' directory (for example: ''ig-se_dpm_mysql'', ''ig-se_dpm_disk'', ...).

>
>
IMPORTANT: /services directory
Please ensure that you have all the NEEDED configuration files under your ''/services'' directory (for example: ''ig-se_dpm_mysql'', ''ig-se_dpm_disk'', ...).
Remember to add the variable TORQUE_VAR_DIR in services and change the BATCH_LOG_DIR in ig-site-info.def to /var/torque
  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:
<
<
 
  • Reconfigure the nodetype
Deleted:
<
<
IMPORTANT: /services directory

Please ensure that you have all the NEEDED configuration files under your ''/services'' directory (for example: ''ig-mpi'', ''ig-mpi-ce'', ''ig-mpi-wn'', ...).

Remember to add the variable TORQUE_VAR_DIR in services and change the BATCH_LOG_DIR in ig-site-info.def to /var/torque

 
/opt/glite/yaim/bin/ig_yaim -c -s <site-info.def> -n <nodetype>
Changed:
<
<
Where '''' is one of the nodetypes listed in the "Nodetypes" column of the table above.

NOTE: Please remember to add ”-n ig_BDII_site” if you want to reconfiguring a site BDII on top of your CE

>
>
Where is one of the nodetypes listed in the*Nodetypes* column of the table above.
 
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
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback