configdhcpv6duid always derived the DHCPv6 client identifier from the SMBIOS UUID in firmware byte order. makedhcp does that only when mac.duid is unset or holds 'firmware': 'canonical' reserves the order product_uuid prints, and a literal DUID is reserved as it stands. A node with either setting wrote an identifier that matched no reservation, so it took a pool address and had no boot file URL. mypostscript.tmpl now exports the attribute as DHCP6DUID, and the postscript reads it. 'canonical' keeps the order product_uuid printed. A literal is written as it stands for NetworkManager, which takes a whole DUID. systemd-networkd composes one from a named type, and only the UUID type can be expressed that way, so a literal of another type is written for NetworkManager alone and the reason is logged. A value that is neither keyword nor DUID writes nothing, which is what makedhcp refuses as well. The derived values are byte-identical to kea_duid_from_uuid for both orders. postscript_dhcpv6_duid.bats goes from 9 checks to 16; ignoring the attribute fails the five that name a setting and leaves the firmware default passing. 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!