update main Merlin7 page with production status, remove dead links

This commit is contained in:
2026-01-07 11:35:23 +01:00
parent 5f759a629a
commit 3afcd052f4

View File

@@ -2,9 +2,9 @@
## About Merlin7
The Merlin7 cluster is moving toward **production** state since August 2024, this is expected latest by Q4 2025. Since January 2025 the system has been generally available,
but due to some remaining issues with the platform, the schedule of the migration of users and communities has been delayed. You will be notified well in advance
regarding the migration of data.
PSI's Merlin7 cluster is run on top of an IaaS (Infrastructure as a Service) *vCluster* on the [CSCS Alps infrastructure](https://www.cscs.ch/computers/alps). It is fully integrated with the PSI service landscape was designed to provide the same end user experience as its PSI-local predecessor clusters.
Merlin7 has been in **production** since beginning of June 2025.
All PSI users can request access to Merlin7, please go to the [Requesting Merlin Accounts](requesting-accounts.md) page and complete the steps given there.
@@ -26,8 +26,7 @@ The Merlin7 cluster contains the following node specification:
### Network
The Merlin7 cluster builds on top of HPE/Cray technologies, including a high-performance network fabric called Slingshot. This network fabric is able
to provide up to 200 Gbit/s throughput between nodes. Further information on Slignshot can be found on at [HPE](https://www.hpe.com/psnow/doc/PSN1012904596HREN) and
at <https://www.glennklockwood.com/garden/slingshot>.
to provide up to 200 Gbit/s throughput between nodes. Further information on Slignshot can be found on at [HPE](https://www.hpe.com/psnow/doc/PSN1012904596HREN).
Through software interfaces like [libFabric](https://ofiwg.github.io/libfabric/) (which available on Merlin7), application can leverage the network seamlessly.