makedhcp wrote no boot file into a DHCPv6 reservation, so the firmware took the reserved address and had nothing to load. EDK2 reported "PXE-E21: Remote boot cancelled" and tried the next boot entry, which reads as a DHCP failure although the address was granted. Measured on openEuler 24.03: dhcpd6.conf carried no bootfile reference where the DHCPv4 configuration carried fifteen. addnode6 now emits option dhcp6.bootfile-url, which is RFC 5970 option 59, from the same helpers the Kea backend uses. Those two helpers read noderes and BootPolicy, not Kea, so they lose their kea_ prefix. Two further defects kept the same node from booting. The DHCPv6 daemon was never started: ISC runs it as a second service, the flag that recorded the need was assigned and never read, restart_dhcpd restarted only the DHCPv4 service, and the service map had no ISC DHCPv6 name. And makedhcp failed with "The file /etc/sysconfig/dhcpd6 doesn't exist" although no EL or openEuler dhcp package ships that file and dhcpd6 does not need it: with the file deleted the daemon still binds the provisioning NIC, because ISC dhcpd listens only on the interfaces its subnet declarations name. 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!