[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] Upgrading old Condor pool to modern times



Hello,

 

Iâm not sure how things may have shifted in recent years, but during my entire tenure using HTCondor, upgrades were very straightforward â last I knew, any version of HTCondor can interoperate with any other, because the system is schema-free. Anything that an agent sees that it doesnât recognize, it simply ignores, so old startds can advertise seamlessly to new schedds, and vice versa.

 

Iâd encourage you to try adding a 25.2 startd to your 8.4.5 pool, I think youâd find it will work better than expected. In my jump from v6 to v8 back in the day, there were only a handful of tweaks needed to bring the legacy config files into alignment with the new version.

 

This capability might be able to save you some effort.

 

               -Michael Pelletier.

 

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> On Behalf Of Szabolcs HorvÃtth
Sent: Monday, November 3, 2025 8:19 AM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: [HTCondor-users] Upgrading old Condor pool to modern times

 

Hi, We will upgrade our legacy but working Condor pool setup from using 8.â4.â5 to 25.â2. Instead of trying to migrate all the legacy configurations and attributes, we'll start mostly from scratch. Are there any known issues, things to look

Hi,

We will upgrade our legacy but working Condor pool setup from using 8.4.5 to 25.2. Instead of trying to migrate all the legacy configurations and attributes, we'll start mostly from scratch.
Are there any known issues, things to look out for when doing such a big leap in the Condor lifecycle? Were there typical issues that admins faced when upgrading between major versions?
(Both the central manager and the startd machines are on Ubuntu 24.04.)

Cheers,
Szabolcs