A node that xCAT has not yet discovered has no DUID, so kea_node_reservations6 writes no reservation for it. Option 59, bootfile-url, is written only inside a reservation, so Kea answers the node with an address from the dynamicrange and no boot file. The node boots nothing, and sequential discovery over IPv6 cannot start: xCAT learns the DUID from the Genesis image, and the image needs a boot file to run. DHCPv4 answers an unknown client from client classes keyed on option 93, the client system architecture. RFC 5970 gives DHCPv6 the same registry in option 61 and the boot file URL in option 59, so the same shape applies. Two places dropped it: render_dhcp6_config did not render client-classes, which render_dhcp4_config has always done. _render_subnet6 did not render the additional-class list, which _render_subnet4 renders. Both now render them. kea_client_classes6 builds one class per architecture: the signed iPXE shim for a UEFI x86_64 client when the loader is on disk, and the grub2 loader for aarch64, riscv64 and ppc64. kea_subnet6_intent builds them per network, because option 59 carries a server and that server is the management node facing that network, and names them per subnet so two provisioning networks cannot collide. A node with a reservation keeps the boot file the reservation carries. The classes answer only what no reservation matched. 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!