dhcp6_bootfile_url_for_node drops the DHCPv6 boot file when the UEFI loader is not under the tftpdir of the node, and says nothing. makedhcp exits 0, the reservation is written with its address and its DUID, and the node then sits at a firmware timeout with no line on the management node that names the file it was looking for. upstream_loader_warnings does not cover this. It reads the SITE TFTP directory, and it runs on makedhcp -n and makedhcp -a only, so a node that carries its own noderes.tftpdir is never examined and makedhcp <node> warns about nothing at all. dhcp_dhcpv6_duid.t now asserts the warning reaches the caller for the node whose loader is absent, exactly once, attributed to the node and naming the full path. The node in the same run whose loader is present must not be reported. dhcp_ipxe_readiness.t asserts the decision itself for a present loader, an absent one, a trailing slash on the directory, and the three inputs that are not a missing file. These assertions fail on this tree: the three in dhcp_dhcpv6_duid.t report nothing in the collected warnings, while the assertion that the boot file is absent, and the control on the node whose loader is present, both still pass. 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!