<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-2">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-size: 11pt; color: rgb(0, 0, 0);">One week from now, on the upcoming CST Division monthly maintenance day,</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">Tuesday, May 21st, jobs which do not explicitly request `el7` will be</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">assigned to land on AlmaLinux 9. *Incompatible jobs will fail,* or,</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">depending on their other constraints, may fail to submit or run at all.</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"><br>
</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">When we started the migration, we configured the batch system so that</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">submitted jobs would default to running exclusively on CentOS Linux 7,</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">in order to avoid intermittent failures with incompatible jobs landing</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">on the newly available AlmaLinux 9 nodes, while allowing users to begin</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">migrating their jobs by overriding the default. We must change that</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">default before the migration is complete, so that any remaining</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">incompatible jobs will begin to fail before users no longer have the</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">option of continuing to run by explicitly requesting CentOS Linux 7</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">while they work to make their jobs compatible with AlmaLinux 9.</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"><br>
</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">See Knowledge Base Articles</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"> </div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"> https://jlab.servicenowservices.com/scicomp?id=kb_article&sysparm_article=KB0015330</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"><br>
</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">which details how to select the desired operating system using Slurm</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">feature constraints, and</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"><br>
</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"> https://jlab.servicenowservices.com/scicomp?id=kb_article_view&sysparm_article=KB0015346</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"><br>
</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">which contains information about changes between using EL7 and EL9 Farm</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">nodes that may affect your work. We intend for the Farm to be 90%</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">migrated this week, and to migrate the remaining 10% on the June</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">maintenance day, the 18th. You can see the migration progress at</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"> </div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"> https://scicomp.jlab.org/scicomp/nodeStatus/os</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"> </div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">or with a command like</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"> </div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"> sinfo -ho'%f %N' | awk '$1=substr($1,0,3)' | sort</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"><br>
</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"><br>
</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">***Also of note, but unrelated to the operating system migration,***</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">all Farm GPU (sciml) nodes and a subset of Farm nodes (farm16) have been</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">reserved from 6am to 5pm on May 21st for a planned power outage that is</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">needed to install additional metering. Jobs which require those nodes</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">and whose TimeLimit stretches into the reservation period will remain</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">in the Pending state.</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"><br>
</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"><br>
</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">Please file a ServiceNow Incident at</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"><br>
</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"> https://jlab.servicenowservices.com/scicomp</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"><br>
</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);">with any questions or concerns.<br>
<br>
<br>
________________________________________<br>
Od: Bryan Hess <bhess@jlab.org><br>
Poslano: torek, 27. februar 2024 10:28<br>
Za: jlab-scicomp-briefs@jlab.org<br>
Zadeva: JLab Farm Upgrade to AlmaLinux 9</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"><br>
</div>
<div style="font-size: 11pt; color: rgb(0, 0, 0);"><br>
Farm Upgrade to AlmaLinux 9<br>
<br>
The Jefferson Lab computing farm is being upgraded from CentOS 7 to AlmaLinux 9 in the coming months. This document outlines changes to the environment for all users of the interactive login nodes (ifarm), SLURM, and SWIF.<br>
<br>
<br>
Farm Upgrade Schedule and Worker Node Selection<br>
<br>
The farm is being upgraded in a series of steps. Between now and June, the farm composition will change from majority CentOS 7 to predominantly AlmaLinux 9. At the time of this writing, CentOS 7 is the default. This default will change at a later step in the
conversion process. Users may currently select which nodes run their jobs using Slurm features/constraints. This article<<a href="https://jlab.servicenowservices.com/kb?id=kb_article_view&sysparm_article=KB0015330" id="OWA3c43097a-2e4e-b958-8aea-b01713927b31" class="OWAAutoLink" data-auth="NotApplicable">https://jlab.servicenowservices.com/kb?id=kb_article_view&sysparm_article=KB0015330</a>>
provides details on feature-based node selection. SWIF can pass features through to Slurm. See the SWIF introduction<<a href="https://scicomp.jlab.org/docs/swif2" id="OWA87327f2d-a9c7-e921-cbed-0e599f717223" class="OWAAutoLink" data-auth="NotApplicable">https://scicomp.jlab.org/docs/swif2</a>>
and SWIF command line reference<<a href="https://scicomp.jlab.org/cli/swif.html" id="OWA0a4dc78e-32eb-7ce3-3f9f-a89504a556eb" class="OWAAutoLink" data-auth="NotApplicable">https://scicomp.jlab.org/cli/swif.html</a>> for details.<br>
<br>
The interactive (ifarm) nodes currently run CentOS 7. A new machine, ifarm9.jlab.org is available for AlmaLinux 9 use now. Two new ifarm machines that will run AlmaLinux 9 are on order. They will replace the existing ifarm machines and include more per-core
memory and temporary disk space.<br>
<br>
<br>
Software Environment and Filesystem Changes<br>
<br>
The use of /apps is deprecated and is not available on farm AlmaLinux 9 machines. CVMFS is now used to distribute software. It is rooted under OASIS and can be used with modulefiles<<a href="https://jlab.servicenowservices.com/kb_view.do?sysparm_article=KB0014671" id="OWAef12ccd0-66e8-1be0-619d-aa6c405d5cb4" class="OWAAutoLink" data-auth="NotApplicable">https://jlab.servicenowservices.com/kb_view.do?sysparm_article=KB0014671</a>>
as before. For questions about software package availability, please submit a ServiceNow incident. For hall-specific software distribution questions, contact your computing coordinator<<a href="https://jlab.servicenowservices.com/kb?id=kb_article_view&sysparm_article=KB0014686" id="OWAd4f9fec1-4a6e-f4c8-435e-782a1f9dd998" class="OWAAutoLink" data-auth="NotApplicable">https://jlab.servicenowservices.com/kb?id=kb_article_view&sysparm_article=KB0014686</a>>.<br>
<br>
The legacy /site area has been removed. The path to Jasmine (tape) and cache tools will change from /site/bin to /usr/local/bin. The CUE /u/scratch area has also been removed.<br>
<br>
<br>
Remote Access for Visual Studio Code and SSH<br>
<br>
If you use Visual Studio Code for development and connect it to the ifarm hosts using the Remote-SSH extension, you may be aware that the current version has dropped support for CentOS 7 remote ends. Since AlmaLinux 9 has the newer system software required,
you can use ifarm9 as the remote host instead. This guide to using SSH<<a href="https://jlab.servicenowservices.com/scicomp?id=kb_article&sysparm_article=KB0014918" id="OWAf1486372-3e42-3457-c10a-21746b7737de" class="OWAAutoLink" data-auth="NotApplicable">https://jlab.servicenowservices.com/scicomp?id=kb_article&sysparm_article=KB0014918</a>>
with the farm includes VS Code details at the end.<br>
<br>
</div>
</body>
</html>