makedhcp reversed the first three fields of vpd.uuid to build the DUID-UUID, and the OpenEmbedded Genesis image reported product_uuid in the opposite order to the legacy image. Kea matched neither reservation, so an IPv6 node took a pool address with no bootfile-url. vpd.uuid holds the sixteen octets in the order the client sends them. kvm.pm swaps the first three SMBIOS fields to build the libvirt <uuid>, dodiscovery and doxcat swap product_uuid before they report or send it, and both DHCP backends on master use the column as the DUID payload unchanged. On xcat76-cn the firmware sent 00:04 followed by that column verbatim. kea_duid_from_uuid now colonises vpd.uuid and prefixes 00:04, and genesis-discover reports the DMI uuid in the same order as its legacy sibling. The s390x and device-tree paths read their uuid elsewhere and are untouched. Five assertions in dhcp_kea_plugin_intent.t and the genesis-discover assertion in genesis_openembedded_discovery.bats 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!