Version 5.11.0.1-1 was deployed in production at CERN during the last week, in order to upgrade the catalogue schema version.
This was followed by the deployment of 5.11.2.0-1, today.
Both releases are exclusively Alma9.
Which version should I install?
If setting up CTA for the first time:
Install 5.11.2.0-1 directly.
If upgrading from a previous CTA version (more specifically, from 4/5.10.X.Y-Z):
Hi George,
in production we have been using eos 5.2.24 (CentOS7 and Alma9) and 5.2.27 (on Alma9 only).
On the EOS side at CERN everything is under Alma9 with eos 5.2.27.
Version 5.2.24 was the CentOS 7 to Alma 9 pivot version.
On Alma 9 you need to be careful with the openSSL version on the MGM: it must be > 3.2.2 to offer good X509 performance.
Today I tried to install cta-frontend-5.11.2 from cta-public-repo, while cta-frontend-5.11.2 requires xrootd 5.6.1. Is it correct? Or should it be xrootd 5.7.1?
It was mentioned in the CTA DB upgrade hands-on session of the CTA workshop last week that it is possible to update the DB schema without service downtime (although the tape drives should be kept DOWN).
Just want to confirm once again if this is true.
As far as I remember, our DBAs request all DB connections (cta-frontend and cta-taped) to be stopped but I think this is for the purpose of taking a schema backup/sanpshot before the upgrade.
Hi @george_patargias,
indeed I have always performed DB schema upgrade with no service downtime at CERN.
Once all the cta-taped and cta-frontend are running the pivot version you can upgrade the catalogue schema to the next one. It is compatible with the pivot CTA version and the next CTA version (that starts using some of the new schema features).
This allows you to have some frontends and cta-taped running the pivot version or the next CTA release in production. Hence no full service downtime needed.
Thanks for the heads up Julien, I will try to do the upgrade your way!
We will need to test that both the pivot version (5.11.0.1-1) and 5.11.2.0-1 will work
with the EOS 5.2.23 that we are currently running on the EOS buffer. It should work
I thinkbut we we will double check.
Hi @biyujiang,
I am deploying cta 5.11.7.0-1 in production at CERN with xrootd upgrade and a move to eos 5.3.10.
We’ll flag it for stable beginning of next week with the corresponding release announcement.
You can get it today if you want to test it from CTA testing repository.
For CTA release 5.11.2.0-1, XRootD 5.6.1 is in fact the required version.
It was the same for CTA release 5.10.10.1, but the difference is that CTA 5.11.2.0-1 required an exact version of XRootD (=) while CTA 5.10.10.1 did allow more recent ones (>=).
This is unfortunate, and it also has impacted us…
Therefore, we have decided to revert it, in favour of using versionlock.list to lock specific RPM versions when necessary.
Please note that we are planning to do a new stable release of CTA soon, which will require the XRootD 5.8.2 (or higher).
We did deploy 5.11.8.0-1 at CERN last week, but we encountered some issues that prevented us from announcing the release as we had expected.
At the moment, we already have the fix (version 5.11.9.0-1), which we plan to deploy and release as stable as soon as possible (once it’s deployed at CERN at the beginning of next week).
My apologies for this delay.
If you want to go ahead, you can find the RPMs of both 5.11.8.0-1 (currently deployed at CERN) and 5.11.9.0-1 (to be deployed next week) here:
Thanks for the info and no problem at all. We will keep an eye for the release of 5.11.9.0-1 next week or so. As far as I can see from CHANGELOG.md this version does not require a further DB schema update - the update from catalogue version 14.0 to 15.0 should be sufficient, right?
Can you please also confirm the EOS version with withich CTA 5.11.9.0-1 is/will be deployed.
Exactly, all 5.11.x.y-z versions share the same CTA Catalogue schema between themselves (15.0), so there should be no need to update it when only the minor version of CTA was updated.
The EOS version used in the CI with this CTA release is the 5.3.10-1: