dhcp6_bootfile_url_for_node writes RFC 5970 option 59 for grub2 alone, so a node with netboot=ipxe takes its reserved IPv6 address and has nothing to load. Its firmware then releases the address and solicits again. grub2 was the only loader an IPv6 node could use. The iPXE build xCAT ships does speak DHCPv6: snponly.efi, the UEFI loader of ipxe-xcat 2.0.0, carries dhcpv6, ipv6 and four IPv6 strings, against a control of 26 iPXE and dhcp strings in the same binary. The firmware that solicits over DHCPv6 is UEFI, so the UEFI loader is the only one such a client can ask for. An ipxe node now gets tftp://<bracketed server>/<UEFI loader>, and the loader name comes from BootPolicy->x86_loader, which is the one place it is chosen. No URL is written when that file is not on disk, because naming a file the TFTP server does not have costs the client a timeout it cannot diagnose; the Kea client classes already refuse it for the same reason. xnba keeps its exclusion. Its loader reports one ipv6 string against a control of five, where the iPXE loader reports five against 26, so there is no evidence it reads option 59. Captured by xCAT-test/unit/dhcp_dhcpv6_duid.t. Removing ipxe from the gate fails the first assertion; removing the on-disk check fails the second. 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!