Daniel Hilst
1df2861139
arch_loader branched on the running backend, so each backend was measured against its own behaviour and the two could disagree for ever with the case still green. That is the drift the case exists to catch. It now returns one loader per architecture. The backends do read one thing off the machine before deciding -- dhcp.pm:3469 keys the BIOS and UEFI classes on xnba.kpxe and xnba.efi being unpacked under tftpdir, and BootPolicy.pm:84 keys the riscv64 HTTP class on grub2.riscv64 -- while ISC names all three unconditionally. So setup places the three loaders it finds missing and teardown removes exactly those, and both backends are asked the same question. An empty file is enough: dhcptest asserts the name in the reply and never opens a TFTP session. Without that, a parity failure would only mean the runner had not unpacked a loader, which is a fact about the runner and not about xCAT. The chainload case loses a guard that can no longer fire, and run-arch loses the branch that skipped an architecture the backend "does not serve".
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!