Vinícius Ferrão
128e7fe197
The global Kea classes give the upstream loader to an x86 client that cannot fetch its script, and the Etherboot class gives it the BIOS loader. The network classes and the ISC x86 lines give the Genesis script under xcat/ipxe/nets to a client with the iPXE features of its path, and the Kea subnet lists those classes. Without an upstream loader file on the server, neither backend names it or the second stage that it would fetch, and the ISC lines stop such a client before the fallback. The xNBA files name no global class. An xnba node gets xNBA from its own first-stage classes when the server has the xNBA BIOS file, and still xcat/xnba.efi without the local UEFI file. Without the xNBA BIOS file it has no first-stage classes, as it has no ISC host statements. An ipxe node without a SAN disk carries the upstream loader in its own first-stage classes. The ISC configuration test also checks these lines in configurations that makedhcp upgraded, one of them with indented declarations. The DHCP wire cases now expect the upstream loader for an x86 client with no reservation, and its network script for a second stage that reports the features in option 175. A second stage without them gets the loader again, and an xnba node still gets xNBA.
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!