Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
habrok:migration:alma9:start [2026/06/16 15:12] – [Personal Python and R libraries] Add link to Python environement docs page pedrohabrok:migration:alma9:start [2026/10/09 10:40] (current) – fokke
Line 1: Line 1:
-====== Hábrók upgrade from Alma Linux 8 to 9 ======+====== Hábrók upgrade from AlmaLinux 8 to 9 ======
  
-This page covers a general overview of Hábrók's move to Alma Linux 9 and what it means for your software. Make sure you also check the following related pages:+<WRAP center round important> 
 +**2026-10-09**: The migration to AlmaLinux 9.8 has been completed. This means that all your applications will now run on the new OS. The impact of this change is described below. 
 +</WRAP> 
 + 
 +This page covers a general overview of Hábrók's move to AlmaLinux 9 and what it means for your software. Make sure you also check the following related pages:
  
   * [[habrok:migration:alma9:plan|Migration plan]] — the three-step rollout (testing → mixed environment → completion), the Alma 9 test reservation, and how to target Alma 8 or Alma 9 explicitly with ''sbatch''   * [[habrok:migration:alma9:plan|Migration plan]] — the three-step rollout (testing → mixed environment → completion), the Alma 9 test reservation, and how to target Alma 8 or Alma 9 explicitly with ''sbatch''
Line 8: Line 12:
 ---- ----
  
-===== TLDR =====+===== TL;DR =====
  
-Hábrók's OS is currently Alma Linux 8.10 and we will start a migration to Alma Linux 9.8 on a date to be announced soon. This migration will be gradual and we will first set up a test environment for our users. After the initial test period we will gradually migrate login, interactive and compute nodes from Alma Linux 8 to 9. This means there will be a mixed environment for a while, see [[habrok:migration:alma9:plan|here]] for details, including on how to access a particular Alma Linux version.+Hábrók's OS is currently AlmaLinux 8.10 and we will start a migration to AlmaLinux 9.8 on a date to be announced soon. This migration will be gradual and we will first set up a test environment for our users. After the initial test period we will gradually migrate login, interactive and compute nodes from AlmaLinux 8 to 9. This means there will be a mixed environment for a while, see [[habrok:migration:alma9:plan|here]] for details, including on how to access a particular AlmaLinux version.
  
-The upgrade to Alma Linux 9 will not change the way the cluster works, but there are a few important details about your software that you should be aware of.+The upgrade to AlmaLinux 9 will not change the way the cluster works, but there are a few important details about your software that you should be aware of.
  
-The current applications are expected to work. In the near future you need to load a module to access the [[habrok:software_environment:eessi|EESSI software stack]], which will become the default on Alma Linux 9 nodes. You will still be able the existing software but you will need to explicitly load the module ''2023.01''. This change will be announced to the users before it is being made.+The current applications are expected to work. In the near future you need to load a module to access the [[habrok:software_environment:eessi|EESSI software stack]], which will become the default on AlmaLinux 9 nodes. You will still be able the existing software but you will need to explicitly load the module ''2023.01''. This change will be announced to the users before it is being made.
  
-The node names of the compute nodes will change after the migration to Alma Linux 9.+The node names of the compute nodes will change after the migration to AlmaLinux 9.
  
 All further changes will be announced in the login messages, and a change log is kept on the wiki at: [[habrok:additional_information:changelog|Hábrók Changelog]] All further changes will be announced in the login messages, and a change log is kept on the wiki at: [[habrok:additional_information:changelog|Hábrók Changelog]]
Line 24: Line 28:
 ===== Introduction ===== ===== Introduction =====
  
-The current OS used on Hábrók, Alma Linux 8 (which is based on RedHat Enterprise Linux 8), originates in 2019, with the final version 8.10 released in 2024. The OS still gets security updates for several more years, but may no longer support new hardware. Furthermore the versions of the software inside it are getting outdated.+The current OS used on Hábrók, AlmaLinux 8 (which is based on RedHat Enterprise Linux 8), originates in 2019, with the final version 8.10 released in 2024. The OS still gets security updates for several more years, but may no longer support new hardware. Furthermore the versions of the software inside it are getting outdated.
  
-The latter means that it is becoming necessary to move to a newer release of Alma Linux to make sure newer applications are supported. Since Alma Linux version 10 was just released last year, we will migrate to the proven stable Alma Linux 9.+The latter means that it is becoming necessary to move to a newer release of AlmaLinux to make sure newer applications are supported. Since AlmaLinux version 10 was just released last year, we will migrate to the proven stable AlmaLinux 9.
  
 This page documents the impact that this may have for you as a Hábrók user. The migration will have an effect on the application side and there will be a mixed environment for a certain period. These parts will be described in the [[#3_software_support|Software support]] section below and on the [[habrok:migration:alma9:plan|Migration plan]] page. This page documents the impact that this may have for you as a Hábrók user. The migration will have an effect on the application side and there will be a mixed environment for a certain period. These parts will be described in the [[#3_software_support|Software support]] section below and on the [[habrok:migration:alma9:plan|Migration plan]] page.
Line 38: Line 42:
 Many applications are available by loading these through our "module" system. By default these modules are taken from the current ''2023.01'' software stack. All these applications have been built by us on a RedHat Enterprise Linux 8 derivative with optimizations for most of the CPU architectures that we have available in Hábrók. Many applications are available by loading these through our "module" system. By default these modules are taken from the current ''2023.01'' software stack. All these applications have been built by us on a RedHat Enterprise Linux 8 derivative with optimizations for most of the CPU architectures that we have available in Hábrók.
  
-We have tested several of these applications on an Alma Linux 9 system and have not encountered issues. We have not been able to test the hundreds of applications that are installed, but since all applications that we tested work properly, including R and Python, we expect the current stack to still work in Alma Linux 9.+We have tested several of these applications on an AlmaLinux 9 system and have not encountered issues. We have not been able to test the hundreds of applications that are installed, but since all applications that we tested work properly, including R and Python, we expect the current stack to still work in AlmaLinux 9.
  
-Although the current software stack still works, we cannot continue building new applications on Alma Linux 8 and we therefore need to move to a new software stack for the future. This stack will be based on EESSI and is described in a later section.+Although the current software stack still works, we cannot continue building new applications on AlmaLinux 8 and we therefore need to move to a new software stack for the future. This stack will be based on EESSI and is described in a later section.
  
 <WRAP center round important> <WRAP center round important>
Line 77: Line 81:
 ==== Self-compiled applications ==== ==== Self-compiled applications ====
  
-Binary applications, compiled on Alma Linux 8, may still  work on Alma Linux 9. We strongly encourage you to recompile these applications. Applications built with the OS compilers can be recompiled on Alma Linux 9 directly. Applications that have been built using compiler modules from the ''2023.01'' software stack should be recompiled using a compiler from ''EESSI/2025.06''. +Binary applications, compiled on AlmaLinux 8, may still  work on AlmaLinux 9. We strongly encourage you to recompile these applications. Applications built with the OS compilers can be recompiled on AlmaLinux 9 directly. Applications that have been built using compiler modules from the ''2023.01'' software stack should be recompiled using a compiler from EESSI (e.g. ''EESSI/2025.06''). Note that compiling applications with compilers from EESSI require you to load the ''buildenv'' module for the corresponding compiler toolchain, e.g. for ''foss/2025b'' you would need to load ''buildenv/default-foss-2025b''. This is a wrapper module ensuring that the compilers insert the path to dependencies into your binaries. Compiling without this module could lead to the following kind of error when running your executable: 
 +<code> 
 +error while loading shared libraries: libsomelibrary.so: cannot open shared object file: No such file or directory 
 +</code>
 ==== Personal Python and R libraries ==== ==== Personal Python and R libraries ====
  
 === Python libraries === === Python libraries ===
  
-Most Python libraries are distributed as binary wheels. These binary wheels are expected to work on Alma Linux 9. Some wheels that no longer supported Alma Linux 8, may even work again on Alma Linux 9.+Most [[..:..:software_environment:python|]] libraries are distributed as binary wheels. These binary wheels are expected to work on AlmaLinux 9. Some wheels that no longer supported AlmaLinux 8, may even work again on AlmaLinux 9.
  
 We do advise you to reinstall your virtual environments with a Python version from the ''EESSI/2025.06'' software stack, as the ''2023.01''  software stack will be deprecated in the future.  See [[habrok:software_environment:eessi|here]] for more details on EESSI). Reinstalling your virtual environments is similar to the process of installing them in the first place. You can find detailed information on how to do this in the [[..:..:software_environment:python:environments|]] page. We do advise you to reinstall your virtual environments with a Python version from the ''EESSI/2025.06'' software stack, as the ''2023.01''  software stack will be deprecated in the future.  See [[habrok:software_environment:eessi|here]] for more details on EESSI). Reinstalling your virtual environments is similar to the process of installing them in the first place. You can find detailed information on how to do this in the [[..:..:software_environment:python:environments|]] page.