dhcp6_bootfile_url_for_node in dhcp.pm returned nothing when the UEFI loader was not under the tftpdir of the node, and reported nothing. The reservation was still written with its address and its DUID, makedhcp exited 0, and the node reached a firmware timeout with no line anywhere naming the file it had asked for. On an IPv6 cell that is the whole boot: there is no second method to fall back to. BootPolicy gains dhcp6_missing_loader_warning, which takes the tftpdir of the node and the loader name and returns the sentence or nothing. dhcp6_bootfile_url_for_node reports it through the callback, once per node per makedhcp, and then drops the boot file as before. Naming the node matters because the path comes from noderes.tftpdir, which the reader cannot derive from the site value. The three assertions the previous commit added to dhcp_dhcpv6_duid.t now pass, and the nine in dhcp_ipxe_readiness.t with them. Blanking the file check in the new sub fails five of those nine and leaves the four controls passing. 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!