No major problem.
No problem with DC24 (so far).

Starting 01/29/2024 we noticed a sharp increase of cvmfs failing on worker nodes.
For a large fraction of issues ‘cvmfs_config probe’ would hang while checking the OSG section.
It often took one or two cvmfs restart (killall) attempts to recover the node.
On several occasion a reboot was needed to recover. This was most pronounced the first week,
and gradually quieted down over the next 2 weeks.  No issue noticed recently.

Two tickets about SLATE squid instance problems.
First ticket was sl-um-es2 instance hung.
Second ticket followed an update of the container for security update that may not have been succefully deployed.
Seemed to have had the wrong image tag (testing) for sl-um-es3 ?

dCache xrootd monitoring: configured but no reportsgoing to Kafka yet.
Waiting til end of DC24 to restart doors. 

We usually pool our MSUT2, UMT2 and UMT3 purchase to maximize discount.
But UM T3 has to spend DOE money now.
Selected: Compute R6625 with 32C AMD 9354 and 24x16G DIMMs (128 HT, 3G/HT).
Storage: Selected R760xd2 with 24x20T drives Intel CPU (1x Silver 4510 2.4G 12C) and 8x16G DIMMs.

EL9: both UM and MSU have RedHat site licenses.
UM has been able to provision RHEL9 nodes from RH Satellite. Not MSU.
Lots of work ahead.