Vinícius Ferrão
bef5bd5eef
The EL10 anaconda has no RISC-V EFI platform: on riscv64 it asks for the x86 UEFI boot loader packages (grub2-efi-x64, shim-x64), which do not exist, and registers the UEFI boot entry as \EFI\<distro>\shimx64.efi, so a kickstart install stops at the missing packages and, once tolerated, leaves a system the firmware cannot boot. Add riscv64 templates for the rocky10/rhels10 compute and service profiles that are the shared templates plus %packages --ignoremissing and a %post fix-up, riscv64 package lists that add grub2-efi-riscv64 and efibootmgr to the shared lists, and the fix-up itself (post.rhels10.riscv64): it copies \EFI\<distro>\grubriscv64.efi to the removable-media path \EFI\BOOT\BOOTRISCV64.EFI and re-points the UEFI boot entry at grubriscv64.efi, so the installed node boots from disk with or without usable NVRAM. Reinstalling a node replaces that entry instead of adding another one. The %post of a kickstart is a single shell script, into which xCAT splices every #INCLUDE, and post.rhels10/post.rhels8 end it with "exit 0"; the fix-up is therefore included ahead of them. The shared templates and other architectures are unchanged.
xCAT
xCAT is a toolkit for deployment and administration of clusters of all sizes.
The xCAT sunset was only a quick eclipse
Dear xCAT Community,
The xCAT sunset has changed course. VersatusHPC has been invited to join the xCAT Consortium, and future development will move toward direct upstream contributions coordinated with the Consortium and its existing member companies.
That matters most for Enterprise Linux 10 (EL10). EL10 support is coming to xCAT, restoring a future operating-system path for sites that still rely on xCAT. This is an important change from the previous sunset guidance, where the lack of an EL10 path was one of the strongest reasons to move away from xCAT.
The xCAT Consortium continues to recommend Confluent as the long-term successor to xCAT, and that remains the Consortium position. Users planning new cluster-management deployments should evaluate Confluent and its xCAT comparison documentation.
At the same time, xCAT is no longer sunsetted. The Consortium and participating companies will continue updating xCAT while there is community and user demand for it.
In summary:
- xCAT development is continuing upstream through the Consortium and participating companies.
- Enterprise Linux 10 support is coming.
- Confluent remains the Consortium-recommended successor and migration path.
- xCAT updates will continue while there is community and user demand.
We want to thank the xCAT Consortium and community for keeping this project moving. The sun went behind the moon for a moment, but xCAT is still here.
For more information on Confluent and how to get started, please visit the Confluent: Project Page, Documentation or Confluent vs xCAT comparison.
With thanks,
The xCAT Consortium
Documentation
xCAT Documentation is hosted on Read The Docs: https://xcat-docs.readthedocs.io
Status
| xCAT Version | Build Status |
|---|---|
| Latest (master branch) | |
| Stable (latest release) |
Looking for older versions?
Open Source License
xCAT is made available under the EPL license: https://opensource.org/licenses/eclipse-1.0.php
Developers
Want to help? Check out the developers guide!