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:plan [2026/09/07 07:38] – fokkehabrok:migration:alma9:plan [2026/10/09 10:41] (current) – fokke
Line 1: Line 1:
 ====== Migration plan ====== ====== Migration plan ======
  
-We will migrate Hábrók to Alma Linux 9 in a three step procedure. The first step consists of a testing phase, in which some nodes will be made available to the users for testing their workloads on Alma Linux 9. This is followed by a migration phase, in which compute and user interface nodes will be gradually moved over from Alma Linux 8 to 9. The final phase is when all nodes have been migrated, including the last user interface nodes.+<WRAP center round important> 
 +**2026-10-09**: The migration, outlined below, has been completed. 
 +</WRAP> 
 + 
 +We will migrate Hábrók to AlmaLinux 9 in a three step procedure. The first step consists of a testing phase, in which some nodes will be made available to the users for testing their workloads on AlmaLinux 9. This is followed by a migration phase, in which compute and user interface nodes will be gradually moved over from AlmaLinux 8 to 9. The final phase is when all nodes have been migrated, including the last user interface nodes.
  
 ===== Testing phase ===== ===== Testing phase =====
  
-**The testing phase has been completed on August 31 2026** The reservation has been removed and the ''merel1.hb.hpc.rug.nl'' test node has been shutdown as ''interactive2.hb.hpc.rug.nl'' has been reinstalled with Alma Linux 9.+**The testing phase has been completed on August 31 2026** The reservation has been removed and the ''merel1.hb.hpc.rug.nl'' test node has been shutdown as ''interactive2.hb.hpc.rug.nl'' has been reinstalled with AlmaLinux 9.
  
-We have made a few nodes available, which are running Alma Linux 9, to allow users to test their software and workloads. The following nodes are available:+We have made a few nodes available, which are running AlmaLinux 9, to allow users to test their software and workloads. The following nodes are available:
  
   - Interactive login node ''merel1.hb.hpc.rug.nl''. Users can login to this node and use it in the same way as the other interactive CPU based nodes.   - Interactive login node ''merel1.hb.hpc.rug.nl''. Users can login to this node and use it in the same way as the other interactive CPU based nodes.
Line 23: Line 27:
 ===== Gradual migration of compute and login/interactive nodes ===== ===== Gradual migration of compute and login/interactive nodes =====
  
-After the testing phase we will start the migration of the rest of the infrastructure to Alma Linux 9. This includes the following steps:+After the testing phase we will start the migration of the rest of the infrastructure to AlmaLinux 9. This includes the following steps:
  
-  - We will remove the reservation from the existing test nodes and these will become available for all jobs, that do not explicitly request Alma Linux 8 (see below for details on this) +  - We will remove the reservation from the existing test nodes and these will become available for all jobs, that do not explicitly request AlmaLinux 8 (see below for details on this) 
-  - We will migrate ''login2.hb.hpc.rug.nl'', ''interactive2.hb.hpc.rug.nl'' and ''gpu2.hb.hpc.rug.nl'' to Alma Linux 9. +  - We will migrate ''login2.hb.hpc.rug.nl'', ''interactive2.hb.hpc.rug.nl'' and ''gpu2.hb.hpc.rug.nl'' to AlmaLinux 9. 
-  - We will migrate the other Hábrók compute nodes to Alma Linux 9 in batches. Nodes will only be migrated when the running jobs have finished.+  - We will migrate the other Hábrók compute nodes to AlmaLinux 9 in batches. Nodes will only be migrated when the running jobs have finished.
  
 ==== Submitting explicitly to Alma 8 or Alma 9 nodes ==== ==== Submitting explicitly to Alma 8 or Alma 9 nodes ====
  
-If you want to make sure your jobs land on a node with specifically Alma Linux 8 or 9, you can put a constraint in  your jobs using the sbatch parameter ''%%--%%constraint''. You can either specify ''%%--%%constraint=alma8'' or ''%%--%%constraint=alma9''.+If you want to make sure your jobs land on a node with specifically AlmaLinux 8 or 9, you can put a constraint in  your jobs using the sbatch parameter ''%%--%%constraint''. You can either specify ''%%--%%constraint=alma8'' or ''%%--%%constraint=alma9''.
  
 In a job script this would look like:\\ In a job script this would look like:\\
Line 46: Line 50:
 The last steps of the migration will that the last compute nodes will be migrated and the migration will be completed by reinstalling login1.hb.hpc.rug.nl, interactive1.hb.hpc.rug.nl and gpu1.hb.hpc.rug.nl. The last steps of the migration will that the last compute nodes will be migrated and the migration will be completed by reinstalling login1.hb.hpc.rug.nl, interactive1.hb.hpc.rug.nl and gpu1.hb.hpc.rug.nl.
  
-After this point all user interface and compute nodes are running Alma Linux 9.+After this point all user interface and compute nodes are running AlmaLinux 9.