Over DHCPv6 a UEFI node that chainloads iPXE is two DHCP clients on one NIC, and the two 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. iPXE converts the same bytes to RFC 4122 order first. makedhcp reserves the address for one DUID, so iPXE matches nothing, receives no RFC 5970 option 59 and prints "Nothing to boot: No such file or directory". The second client also needs a different boot file. The shim loads ipxe.efi from the directory it came from, which iPXE cannot do, so a chainloaded iPXE given the shim again stops at "Failed to open ipxe.efi". This adds the cases to xCAT-test/unit/dhcp_dhcpv6_duid.t. They assert on the reservations that kea_build_node_reservations6 returns and on the omshell hosts that makedhcp creates on ISC DHCP. Seven fail against the unfixed plugin. One existing case moves from cn03 to cn01. It asserts that an ipxe node whose shim is absent gets no option 59, and cn03 asks for the canonical DUID order, which is the order iPXE sends, so the boot file of its first reservation is the boot script and not the shim. 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!