OSG Software Release 3.4.29¶
Release Date: 2019-05-02
Summary of changes¶
This release contains:
XCache 1.0.5 is a complete overhaul of the packaging and configuration for the StashCache cache and origin services, based on improvements available in XRootD 4.9.1. XCache is also the basis of upcoming work for connecting caches to the CMS and ATLAS data federations.
The configuration has been rewritten to use
config.d-style directories instead of single config files, and supporting services have been added to do the following:
- update authorization for both caches and origins based on data in the OSG Topology service
- automatically renew cache proxies
This overview document contains links to instructions for setting up new caches and origins, and instructions for VOs on how to get their data into the StashCache Federation.
XCache is only available for EL7, and EL7 is now a requirement for a cache or origin to join the StashCache Data Federation.
Because of the extensive changes to the configuration, sites upgrading their caches or origins to this version should consider the upgrade to be the same amount of work as a reinstall of the service.
Update MyProxy to use the Grid Community Toolkit (GCT)
These JIRA tickets were addressed in this release.
This section describes important upgrade notes and/or caveats for packages available in the OSG release repositories. Detailed changes are below. All of the documentation can be found here.
- OSG 3.4 contains only 64-bit components.
- StashCache is only supported on EL7
GlideinWMS 3.4.5 is the last release supporting Globus GRAM (a.k.a. GT2/GT5).
For new Singularity features introduced in GlideinWMS 3.4.1, all factories and frontends need to be >= 3.4.1.
OSG GlideinWMS factories are running at least 3.4.1
If some of the connected Factories are <= 3.4.1 you will see an error during reconfig/upgrade if you try to use features that require a newer Factory. To start using Singularity via GlideinWMS, see:
Upgrades from <= 3.4.0 may require merging
/etc/condor/config.d/*.rpmnewfiles and a restart of HTCondor.
GlideinWMS >= 3.4.5 uses shared port, requiring only port 9618. To ease the transition to shared port, the User Collector secondary collectors and CCBs support both shared and separate, individual ports. To start using shared port, change the secondary collectors lines and the CCBs lines (if any) in
/etc/gwms-frontend/frontend.xml, changing the address to include the shared port sinful string:
<collector DN="/DC=org/DC=opensciencegrid/O=Open Science Grid/OU=Services/CN=gwms-frontend.domain" group="default" node="gwms-frontend.domain:9618?sock=collector0-40" secondary="True"/>
gwms-frontend-domain with the hostname of your GlideinWMS frontend.
See the GlideinWMS documentation for details.
Due to the central RSV service retirement (see this document for details),
the new version of RSV will disable the
gratia-consumer component that reports to the central service.
Please update all RSV packages by running the following command on your RSV host:
[email protected] # yum update rsv\*
Additionally, if you are using osg-configure, please edit
/etc/osg/config.d/30-rsv.ini and set the following:
enable_gratia = False
Updating to the new release¶
To update to this series, you need to install the current OSG repositories.
Once the new repositories are installed, you can update to this new release with:
[email protected] # yum update
- Please be aware that running
yum updatemay also update other RPMs. You can exclude packages from being updated using the
--exclude=[package-name or glob]option for the
- Watch the yum update carefully for any messages about a
.rpmnewfile being created. That means that a configuration file had been edited, and a new default version was to be installed. In that case, RPM does not overwrite the edited configuration file but instead installs the new version with a
.rpmnewextension. You will need to merge any edits that have made into the
.rpmnewfile and then move the merged version into place (that is, without the
.rpmnewextension). Watch especially for
/etc/lcmaps.db, which every site is expected to edit.
Do you need help with this release? Contact us for help.
Detailed changes in this release¶
We added or updated the following packages to the production OSG yum repository. Note that in some cases, there are multiple RPMs for each package. You can click on any given package to see the set of RPMs or see the complete list below.
Enterprise Linux 6¶
Enterprise Linux 7¶
If you wish to manually update your system, you can run yum update against the following packages:
myproxy myproxy-admin myproxy-debuginfo myproxy-devel myproxy-doc myproxy-libs myproxy-server myproxy-voms osg-version stash-cache stash-origin xcache
If you wish to only update the RPMs that changed, the set of RPMs is:
Enterprise Linux 6¶
myproxy-6.2.3-1.1.osg34.el6 myproxy-admin-6.2.3-1.1.osg34.el6 myproxy-debuginfo-6.2.3-1.1.osg34.el6 myproxy-devel-6.2.3-1.1.osg34.el6 myproxy-doc-6.2.3-1.1.osg34.el6 myproxy-libs-6.2.3-1.1.osg34.el6 myproxy-server-6.2.3-1.1.osg34.el6 myproxy-voms-6.2.3-1.1.osg34.el6 osg-version-3.4.29-1.osg34.el6
Enterprise Linux 7¶
myproxy-6.2.3-1.1.osg34.el7 myproxy-admin-6.2.3-1.1.osg34.el7 myproxy-debuginfo-6.2.3-1.1.osg34.el7 myproxy-devel-6.2.3-1.1.osg34.el7 myproxy-doc-6.2.3-1.1.osg34.el7 myproxy-libs-6.2.3-1.1.osg34.el7 myproxy-server-6.2.3-1.1.osg34.el7 myproxy-voms-6.2.3-1.1.osg34.el7 osg-version-3.4.29-1.osg34.el7 stash-cache-1.0.5-1.osg34.el7 stash-origin-1.0.5-1.osg34.el7 xcache-1.0.5-1.osg34.el7