A node with netboot=ipxe and Secure Boot on fetches the shim of its install source over HTTP, and the server answers 403. EL media ships the EFI binaries of its boot loader mode 0700, copycds copies the media with the modes the media carries, and xCAT serves the install directory over HTTP. Measured on an AlmaLinux 10 tree: EFI/BOOT/grub.cfg is 0444 and answers 200, and BOOTX64.EFI, grubx64.efi and mmx64.efi are 0700 and answer 403. The node reports "Verification failed: Security Policy Violation" for its kernel and then "Operation not permitted" for the shim, and boots nothing. copycd gave the top directory of the copy mode 0755 and left every path under it as the media had it. Both copycd plugins now call xCAT::MediaPerms::make_readable on the copied tree, which adds read permission for the group and for others, and search permission on a directory. It adds no write permission, it adds no execute permission to a file, and it leaves a path that is already group and other readable alone, so a second call changes nothing. On the same AlmaLinux 10 tree it walks 5850 paths, 5835 files and 15 directories, and changes 3 of them: the three files above, each from 0700 to 0744. An install tree that is already copied keeps its modes until copycds runs again for that osimage, so an operator with an existing tree re-runs copycds or gives those files read permission. media_perms_readable.t covers the modes and the idempotence. Three mutations of the module each turn it red. Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
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!