SLOF, the open firmware of a PowerKVM guest and a PowerVM LPAR, identifies itself with an RFC 3315 DUID-LL built from the MAC of its interface, and it reports no UUID at all. makedhcp derives every DHCPv6 reservation from vpd.uuid, so the reservation of a ppc64le node can never match: measured on an IPv6-only node, SLOF sent 00:03:00:01:<mac> against the 00:04:<uuid> reservation xCAT wrote. The node gets no reserved address and no RFC 5970 option 59, and its firmware has nothing to load. dhcp6_client_duid now takes the MAC and the architecture. kea_duid_ll_from_mac builds the DUID-LL from the first address of mac.mac, which is the interface that netboots, and dhcp6_firmware_duid_is_link_layer says which architectures send one. A ppc64le node takes the DUID-LL with no attribute set, and the byte-order warning about vpd.uuid is not reported for it, because that firmware does not read the value. mac.duid gains ll, which selects the DUID-LL on any architecture. firmware and canonical are unchanged and still override. One reservation covers the whole netboot: the grub2 ieee1275 network stack builds its DUID from the same interface, so the loader sends what the firmware sent. That is why no second reservation is written, unlike a chainloading UEFI node. dhcp_dhcpv6_duid.t gains five cases. On the unfixed tree 15 of its 195 assertions fail, cn11 with the firmware-order DUID-UUID where the DUID-LL is expected. A mutation that gives every architecture the DUID-LL fails 42, naming the x86_64 cases that must keep the DUID-UUID. 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!