On an IPv6-only x86_64 node with netboot=ipxe the firmware fetches the shim and starts iPXE, and iPXE then prints "Nothing to boot: No such file or directory". The node falls through to "BdsDxe: No bootable option or device was found". The same node boots over IPv4. A UEFI node that chainloads is two DHCPv6 clients on one NIC and they send different DUIDs. EDK2 copies the SMBIOS UUID into its DUID-UUID in the order SMBIOS stores it, little-endian in the first three fields from SMBIOS 2.6 on, and iPXE converts the same bytes to RFC 4122 order first. Measured on xcat147-cn-tmp-333 with vpd.uuid 5d2df358-d529-11f1-9757-4233c0a89316: the firmware sends 00:04:58:f3:2d:5d:29:d5:... and iPXE sends 00:04:5d:2d:f3:58:d5:29:... kea_node_reservations6 and addnode6 write one reservation, keyed on the DUID that mac.duid selects, so the other client matches nothing and gets no RFC 5970 option 59. On IPv4 the reservation is keyed on the MAC and both clients share it. dhcp6_client_duid_list now returns every DUID the clients of a node send, and both backends reserve for each of them when the netboot method chainloads. The first entry keeps the address and the hostname: Kea refuses a second reservation for one address, and _reservation_matches treats a shared hostname as the same reservation. dhcp6_bootfile_url_for_node takes the client, because iPXE needs the boot script of the node and not the shim again, which is the split the DHCPv4 client classes make with the iPXE feature options. A MAC-keyed reservation was measured and rejected. Kea 2.4.1 derived no MAC for these clients even with mac-sources ipv6-link-local and the EUI-64 link-local on the wire: the lease kept an empty hwaddr column and the firmware took a pool address. ISC DHCP has no hardware-address match for DHCPv6 at all. Two reservations for one address are refused with "There's already reservation for this address/prefix", and one reservation cannot hold both identifiers: "the 'hw-address' and 'duid' are mutually exclusive". xCAT-test/unit/dhcp_dhcpv6_duid.t covers both backends. Seven of its cases fail without this change. 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!