CERNVM4 which is the latest version on the download page, comes with HTCondor 8.8.13 which can’t be updated in a running VM due to cernvm-system depending on the installed version.
On the other hand, version 8.8.13 of HTCondor does not support tokens which are already needed for some experiments now.
Would it be possible to release a new CERNVM version using HTCondor in version 10?
there is indeed a new version of CernVM in development and should available in production soon (= during the summer). CernVM 5 focuses more on containers though, and will no longer pin the package versions the same way as CernVM 4 does - see this presentation for more details.
It might be possible to update HTCondor in CernVM 4 though. Let me discuss this internally and get back to you.
Do you have by chance already an update on the possibility to have an alternative CENRVM4 version with a V10 HTcondor installed?
DUNE already stopped the use of X509 for job submission and uses scitokens only. This stopped us from running DUNE jobs for now. It would be greatly appreciated to have a CERNVM version (4) with an updated HTCondor instead of creating and providing own images for the clouds we run jobs on.
Great! The only other packages that could be updated is the shoal-client. We will put a new version by Thursday (PDT) out.
One more technical question: The updated CERNVM version will have a new version number and a new image to be downloaded, right? Or in other words, continuing with the current image will still allow to use the HTCondor 8.8 in the future?
It’s a transition time now, some experiments already switched to use only scitokens (DUNE) while for others we still need to support X509 (Belle-II, ATLAS).
Sorry for the misunderstanding. What I mean is that we need to boot for some experiments also in the future new VMs that still use the old HTCondor 8.8. That’s mainly for Belle-II and ATLAS. Only DUNE has X509 deactivated and switched to use only scitokens.
So we would need to boot up in the future some VMs using the old system and some using the new updated one, in parallel until all experiments switched to use tokens.
So if we boot a new VM in the future using the current cernvm4-micro-2021.05-1.hdd, will we always get an HTCondor 8.8 then? The new version will be something like cernvm4-micro-2023.06-1.hdd and gives only HTCondor 10.x ?
Small correction here; this image will actually stay the same, as this only refers to the kernel and bootloader, which will stay unchanged. The version of CernVM (the pinned system packages) can be selected in the boot options (in virtualbox hit tab on the “Welcome to uCernVM” boot screen), changing
EDIT: this parameter can also be overridden during contextualization with the cernvm-launch command
OK, good to hear. No, cernvm-system-18.104.22.168 with the updated HTCondor is currently only in our testing repositories, so the production images will still have the old version. We can push this to the production repositories whenever you want, just give me the confirmation.