Vinícius Ferrão
5e4993255b
An x86 client without a node definition, such as a node in discovery, now gets xcat/ipxe/i386/undionly.kpxe for BIOS and xcat/ipxe/x86_64-sb/snponly-shim.efi for UEFI. Once it reports the iPXE features of its path, it gets the Genesis script of its network from xcat/ipxe/nets, which mknb writes. ISC and Kea apply the same test. As for xNBA, neither backend names a loader that the local TFTP directory lacks, or the second stage that the loader would fetch. Kea gave every x86 client its first-stage loader from the global classes, which now name the upstream loader. An xnba node therefore carries its own first-stage classes, which name xcat/xnba.kpxe and xcat/xnba.efi when the local xNBA BIOS file exists, as its ISC host statements do. An ipxe node carries its own classes for the upstream loader, because an upgrade keeps the global classes of an older makedhcp -n until the next makedhcp -n. The ISC host statements of a node do not change.
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!