OSG Release Series

About This Document

This document introduces the different OSG release series and how to update from one to a newer one.

Introduction to OSG Series

An OSG release series is what it sounds like! That is, each series is a sequence of OSG software releases. For example, the 3.2 release series contains OSG software 3.2.0, 3.2.1, …, 3.2.26, etc. Further, a release series corresponds to a set of Yum software repositories, including ones for development, testing, and production use. The Yum repositories for one release series are completely distinct from the repositories for a different release series, even though they may share some packages in common. A particular release within a series is really just a snapshot of packages and their exact versions at one point in time. Generally, when you install software from a release series, say 3.2, you get the most current versions of software packages within that series, regardless of the current release version.

When a new OSG Series is released, it is an opportunity for the OSG Technology area to add major new software packages, make substantial updates to existing packages, and remove obsolete packages. When a new series is initially released, most packages are identical to the previous release, but two adjacent series will diverge over time.

OSG Release Series

Since the start of the RPM-based OSG software stack, we have offered the following release series:

  • OSG 3.1 started in April 2012, and was end-of-lifed in April 2015. While the files have not been removed, it is strongly recommended that it not be installed anymore. Historically, there were 3.0.x releases as well, but there was no separate release series for 3.0 and 3.1; we simply went from 3.0.10 to 3.1.0 in the same repositories.

  • OSG 3.2 started in November 2013, and is still available today. The main differences between it and 3.1 were the introduction of glideinWMS 3.2, HTCondor 8.0, and Hadoop/HDFS 2.0; also the gLite CE Monitor system was dropped in favor of osg-info-services.

  • OSG 3.3 will start in August 2015. The main differences between it and 3.2 are the dropping of EL5 support, the addition of EL7 support, and the dropping of Globus GRAM support.

OSG Upcoming

There is one more OSG Series called "upcoming" which contains major updates planned for a future release series. The yum repositories for upcoming (eg, osg-upcoming, osg-upcoming-testing) are available from all OSG 3.x series, and individual packages can be installed from Upcoming without needing to update entirely to a new series. Note, however, that packages in the "upcoming" repositories are tested against the most recent OSG series.

Installing an OSG Release Series

See YumRepositories (under "Install OSG Repositories") for instructions on installing the OSG repositories.

Updating from OSG 3.1 or 3.2 to 3.2 or 3.3

  1. If you have an existing installation based on OSG 3.1 or 3.2 (which will be referred to as the old series), and want to upgrade to 3.2 or 3.3 (the new series), we recommend the following procedure:

    First, remove the old series yum repositories:

    [root@client ~]$ rpm -e osg-release

    This step ensures that any local modifications to *.repo files will not prevent installing the new series repos. Any modified *.repo files should appear under /etc/yum.repos.d/ with the *.rpmsave extension. After installing the new OSG repositories (the next step) you may want to apply any changes made in the *.rpmsave files to the new *.repo files.

  2. Install the OSG repositories:

    [root@client ~]$ rpm -Uvh URL

    Where URL is one of the following:

    Series EL5 URL (for RHEL5, CentOS5, or SL5) EL6 URL (for RHEL6, CentOS6, or SL6) EL7 URL (for RHEL7, CentOS7, or SL7)
    OSG 3.1 (unsupported) http://repo.grid.iu.edu/osg/3.1/osg-3.1-el5-release-latest.rpm http://repo.grid.iu.edu/osg/3.1/osg-3.1-el6-release-latest.rpm N/A
    OSG 3.2 (unsupported) http://repo.grid.iu.edu/osg/3.2/osg-3.2-el5-release-latest.rpm http://repo.grid.iu.edu/osg/3.2/osg-3.2-el6-release-latest.rpm N/A
    OSG 3.3 N/A http://repo.grid.iu.edu/osg/3.3/osg-3.3-el6-release-latest.rpm http://repo.grid.iu.edu/osg/3.3/osg-3.3-el7-release-latest.rpm

  3. Clean yum cache:

    [root@client ~]$ yum clean all --enablerepo=*
  4. Update software:

    [root@client ~]$ yum update

    This command will update all packages on your system.

Troubleshooting If you are not having the expected result or having problems with Yum please see Yum Troubleshooting

Migrating from CEMon to OSG Info Services on the Compute Element

The program CEMon (found in the package glite-ce-monitor) is no longer available starting in OSG 3.2. OSG Info Services (package osg-info-services) now provides the same functionality. To migrate CEMon configuration to OSG Info Services, perform the following procedure (after following the above update instructions):

  1. Ensure osg-info-services and osg-configure-infoservices are installed:
    [root@ce ~]# rpm -q osg-info-services osg-configure-infoservices
  2. If there is a CEMon configuration file at /etc/osg/config.d/30-cemon.ini, copy its settings to the OSG Info Services configuration file at /etc/osg/config.d/30-infoservices.ini

  3. Run osg-configure to configure OSG Info Services:
    [root@ce ~]# osg-configure -c -m infoservices
  4. Enable and start the osg-info-services service:
    [root@ce ~]# chkconfig osg-info-services on
    [root@ce ~]# service osg-info-services start
  5. Remove CEMon and related packages:
    [root@ce ~]# yum erase glite-ce-monitor glite-ce-osg-ce-plugin osg-configure-cemon
In the output from this command, yum should not list other packages than those three. If it lists other packages, cancel the erase operation, make sure the other packages are updated to their OSG 3.2 (or 3.3) versions (they should have ".osg32" or ".osg33" in their versions), and try again.



Topic revision: r18 - 01 May 2017 - 17:11:57 - MatyasSelmeci
Hello, TWikiGuest!


TWiki | Report Bugs | Privacy Policy

This site is powered by the TWiki collaboration platformCopyright by the contributing authors. All material on this collaboration platform is the property of the contributing authors..