INFNGRID gLite 3.2 x86_64 Update 10/11 (SL5) - 28/04/2010 [INFNGRID Release Wiki]

You are here: INFN-GRID Release Wiki » Documentation » Updates » INFNGRID gLite 3.2 x86_64 (SL5) » INFNGRID gLite 3.2 x86_64 Update 10/11 (SL5) - 28/04/2010

Show pagesource Old revisions

Recent changes Index

Task Manager
SVN repository
Files repository

INFNGRID gLite 3.2 x86_64 Update 10/11 (SL5) - 28/04/2010

MAIN NEWS

BDII:
- New version of the BDII : - This new version includes a new glite-info-provider-ldap. glite-info-provider-ldap 1.2.4 allows up to 10 MB per source and the script itself is now owned by root instead of nobody.
All top-level BDIIs need to be upgraded with high priority, otherwise jobs or users at some sites may no longer see CERN or other big sites included in the information system at some point.
A top-level BDII with the current glite-info-provider-ldap will reject any site that produces more than 5 MB of information system records.
This problem already occurred on April 16, when the BNL site BDII exceeded the 5 MB limit and the site dropped out of all EGEE/WLCG top-level BDIIs.
NO CONFIGURATION/RECONFIGURATION NEEDED
- Don't forget to update the ig_BDII also on the nodes that are site-level BDIIs.

GLEXEC_wn:
- New version of glite-GLEXEC_wn - This update fixes two security vulnerabilities. Please read the advisories from the GSVG: Advisory 51107. Advisory 57604.

ARGUS:
- New version of glite-ARGUS - This update fixes two security vulnerabilities. Please read the advisories from the GSVG: Advisory 55971. Advisory 59718.

LB:
- Introducing glite-LB in 3.2 - This is the first version of glite-LB introduced in glite 3.2, it corresponds to the next major release of the L&B server.
- It's the final outcome of gLite restructuring activity; internal dependencies were cleaned up, and significant portion of the code streamlined and rewritten (in particular full use of transactional database backend) in order to improve performance and stability.
- At the protocol level L&B server 2.0 is fully compatible with 1.9 clients, it works (and has been thoroughly tested) with gLite 3.1 services and UI.

Involved profiles

see table under ”Updating profiles” section

Prerequisites

It means that all the previous updates have to been applied before the last one:

INFNGRID gLite 3.2 x86_64 Update 09 (SL5) - 29/03/2010

Reference gLite Update

gLite 3.2 x86_64 Updates:
- gLite 3.2 Update 10 - 15/04/2010
- gLite 3.2 Update 11 - 27/04/2010

Reference packages

Package	Version
ig-metapackages	ig11_sl5
`glite-yaim-core`	4.0.12-1
`ig-yaim`	4.0.12-1

To correctly manage new-style yum metadata needed by SL5 installation we suggest to use ”mrepo” (an evolution of ”yam” Dag's tool). Please refer to the following documentation for any configuration details:

Update all metadata:

mrepo -guv

Checking/Updating YUM configuration

Repository settings

Please check the instructions you find at the following link:

INFNGRID Repository settings for gLite 3.2

yum-autoupdate settings

As good practice is suggested to disable the yum-autoupdate service. Any other settings is decided at site-manager own risk!

To disable the service it is available the following script ” disable_yum.sh” (thanks Giuseppe Platania) that can be used to REALLY disable yum-autoupdate.

Updating profiles

Find your nodetype and carefully follow the corresponding actions.

Profiles	Metapackages INSTALLATION	Nodetypes CONFIGURATION	Service restart	Partial reconf	Total reconf	Actions	Notes
ARGUS	`ig_ARGUS`	`ig_ARGUS`	-	-	-	1_Metapackage_update 2_Editing_local_configuration_files 3_Nodetype_reconfiguration	-
BDII	`ig_BDII`	`ig_BDII_site` `ig_BDII_top`	-	-	-	1_Metapackage_update	-
GLEXEC_wn	`ig_GLEXEC_wn`	`ig_GLEXEC_wn`	-	-	-	1_Metapackage_update 2_Editing_local_configuration_files 3_Nodetype_reconfiguration	-
LB	`ig_LB`	`ig_LB`	-	-	-	1_Profile_first_installation	First release!

Important note on how to update ig_UI and ig_WN

Due to a problem of the versioning scheme used by VDT, upgrading an already existing gLite 3.2 WN or UI fails. Using the update command “yum groupupdate ig_WN” or “yum groupupdate ig_UI” fails with an error message “package vdt_globus_essentials-VDT1.10.1x86_64_rhap_5-3.x86_64 (which is newer than vdt_globus_essentials-VDT1.10.1x86_rhap_5-4.i386) is already installed”.
The workaround is to uninstall the vdt_globus_essentials rpms manually:

rpm -e --nodeps vdt_globus_essentials-VDT1.10.1x86_rhap_5-3 vdt_globus_essentials-VDT1.10.1x86_64_rhap_5-3

Then do “yum groupupdate ig_WN” or “yum groupupdate ig_UI”.

Actions

Each of the following sections reports the actions that may be follow in order to upgrade your profiles. Please execute ONLY the actions listed on the table above in the column “Actions” and in the row correspondig to your profile!

Metapackage update

Please see YUM Tips for additional information about YUM.

Update YUM metadata and install the new rpms.

yum clean all
yum install <node-type>

Please remember that on case of WN you should use the “groupinstall”:

yum groupinstall ig_WN_torque

Editing local configuration files

In the last updates many variables have been changed or moved to services and defaults directories (see ”updates” for information about those locations). 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:

vimdiff /opt/glite/yaim/examples/siteinfo/ig-site-info.def <site-info.def>

You can see the main differences between the previous release of ig-site-info.def (ig-yaim-4.0.11-4) and the present one (ig-yaim-4.0.12-1) at the following link ig-site-info.def differences

In order to help the comparison the ”Differences between INFNGRID Updates” page has been prepared. WIP

NOTE

You may find more detailed information on configuration files structure here:

INFNGRID YAIM configuration files

and on configuration variables here:

gLite YAIM configuration variables
INFNGRID addendum (only information complementary to the previous guide)

Nodetype reconfiguration

IMPORTANT: <siteconfig>/services directory

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

For any details please refer to the ”INFNGRID YAIM configuration files” reference.

Known Issues: /etc/init.d/tomcat5

Latest version of tomcat5 has a bug on its init script that arises the following error when the service is stopped/started:

/etc/rc.d/init.d/tomcat5: line 196: log_success_msg: command not found

You may fix it simply modifying the first line of /etc/init.d/tomcat5 file as follows:

#!/bin/sh

Reconfigure the nodetype

/opt/glite/yaim/bin/ig_yaim -c -s <site-info.def> -n <nodetype>

Where <nodetype> 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.

Middleware services restart

Look at your chkconfig services list and restart all middleware-related service:

chkconfig --list | grep 3:on | sort

Then restart with:

service <middleware-service> restart

Profile first installation

Updating site status

After the update please edit the following wiki page with the current situation of your site (when update is done set “3.2 Update 09”):

INFN Site status

doc/updates/ig3_2_64/infngrid-update32_10_11.txt · Last modified: 2010/04/28 14:55 by caiftimiei