Difference: Update24-25 (1 vs. 2)

Revision 22012-02-01 - SergioTraldi

Line: 1 to 1
 
META TOPICPARENT name="IgiGliteUpdates"
Changed:
<
<

IGI gLite 3.2 x86_64 Update 24/25(SL5) - 23/03/201

>
>

IGI gLite 3.2 x86_64 Update 24/25(SL5) - 23/03/2011

 

NOTES (read before start to update)

Line: 108 to 108
 

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

Changed:
<
<
>
>
  and on configuration variables here:
Line: 120 to 120
  Please ensure that you have all the NEEDED configuration files under your ''/services'' directory (for example: ''ig-se_dpm_mysql'', ''ig-se_dpm_disk'', ...).
Changed:
<
<
For any details please refer to the reference.
>
>
For any details please refer to the reference "IGI YAIM configuration files”
 

Known Issues: /etc/init.d/tomcat5

Revision 12012-01-31 - SergioTraldi

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="IgiGliteUpdates"

IGI gLite 3.2 x86_64 Update 24/25(SL5) - 23/03/201

NOTES (read before start to update)

VERY IMPORTANT NOTE: Please be aware that because of the IMPORTANT NOTE 2 below, the installation/configuration of two or more profiles/node-types on the same macchine is no more supported!!!

IMPORTANT NOTE 2: 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

IMPORTANT NOTE 3: Download the last repo of lcg-CA and remember to cancel the old lcg-ca.repo:

egi-trustanchors.repo

MAIN NEWS:

  • BDII_top:
    New version of BDII_top (Priority *HIGH*):
    - The main purpose of this top-level BDII release is to address IS-205, the GOC DB URL change. In addition, IS-209 and IS-185 were also addressed. IS-209 is an issue relating to the case sensitivity of GLUE 2.0 and how this is handled in the BDII. IS-185 is an issue relating to how multivalued attributes are handled in the BDII. A number of small packaging issues have also been addressed, see the rpm change log for more details.
    Known Issue: Under some circumstances the old bdii rpm is still installed after the update. Therefore, after updating, please check that the old version of the bdii rpm has been removed using *rpm –qi bdii*; If the previous version is still there, you can remove it using yum remove bdii-5.1.13-1
    - Details about bug fixes & feature

  • BDII_site:
    New version of BDII_site:
    - The main purpose of this site-level BDII release is to address IS-209 and IS-185. IS-209 is an issue relating to the case sensitivity of GLUE 2.0 and how this is handled in the BDII. IS-185 is an issue relating to how multivalued attributes are handled in the BDII. In addition, a number of small packaging issues have also been addressed, see the rpm change log for more details.
    Known Issue: Under some circumstances the old bdii rpm is still installed after the update. Therefore, after updating, please check that the old version of the bdii rpm has been removed using rpm –qi bdii; If the previous version is still there, you can remove it using rpm -e --nodeps --noscripts bdii-5.1.9-1 bdii-5.1.22-1, and afterwards reinstall again the bdii with yum install bdii
    - Details about bug fixes & features

  • WN:
    New version of WN:
    - FTS clients added as new dependencies.
    - New version of WMS and LB clients.
    - New version of Data Management clients: Added python 2.5 and python 2.6 bindings for Data Management clients.
    - New version of yaim clients including the SAGA adapters configuration.
    - New version of yaim core.
    - New version of glite-version (change doesn't actually affect glite-WN).
    - New version of VOMS-Admin.
    - New versions of lcg-infosites and lcg-ManageVOTag.
    - Details about bug fixes & features

  • STORM:
    - This is the first release of SE_storm_[backend|frontend|checksum|gridftp] for SL5/x86_64, containing the same features as the SL4/i386 versions with the adition of:
    - SE_storm_backend:
    - added extended ACL usage sanity check
    - added explicit log appenders for stdout and stderr
    - added distinction between critical and not critical checks
    - removed check of mtab for mount extended attribute option
    - fixed a bug on user FQANS mapping
    - anity check at service startup
    - changed the default JVM opts used at startup
    default log level is INFO
    - SE_storm_frontend:
    - updates on internal documentation
    - added handling of distbin and distsrc
    - SE_storm_gridftp:
    - updates on internal documentation
    - ig-yaim-storm:
    - removed the default JVM opts (now managed by BE start script only)

Prerequisites

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

Reference gLite Update

* gLite 3.2 x86_64 Updates: * gLite 3.2 Update 24 - 01/03/2011 * gLite 3.2 Update 25 - 15/03/2011

Reference packages

Package Version
ig-metapackages ig24_sl5
''ig-yaim'' 4.0.14-3
''ig-yaim-storm'' 4.0.9-12

Instructions

Checking/Updating YUM configuration

Repository settings

Please check the instructions you find at the following link:

IGI 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
<-- -->
Sorted ascending
Metapackages*
*INSTALLATION
Nodetypes*
*CONFIGURATION
Service restart Partial reconf Total reconf Actions Notes
BDII_site ''ig_BDII_site'' ''ig_BDII_site'' - - X Metapackage_update
Nodetype_reconfiguration
Middleware_services_restart
-
BDII_top ''ig_BDII_top'' ''ig_BDII_top'' - - X Metapackage_update
Nodetype_reconfiguration
Middleware_services_restart
-
SE_storm_backend ''SE_storm_backend'' ''SE_storm_backend'' - - - Profile_first_installation First release!
SE_storm_checksum ''SE_storm_checksum'' ''SE_storm_checksum'' - - - Profile_first_installation First release!
SE_storm_frontend ''SE_storm_frontend'' ''SE_storm_frontend'' - - - Profile_first_installation First release!
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
-

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 corresponding 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 

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

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

and on configuration variables here:

Nodetype reconfiguration

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'', ...).

For any details please refer to the 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  -n 

Where '''' is one of the nodetypes listed in the "Nodetypes" column of the table above.

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  restart

Profile first installation

* Follow the IGI Installation and Configuration Guide for gLite 3.2 SL5 x86_64

-- SergioTraldi - 2012-01-31

 
This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback