A DHCPv6 reservation is keyed on the DUID, and a DUID names the machine, not the nic. 10-xcat-genesis.conf puts the DHCPv6 settings in [connection], which NetworkManager applies to every nic, so each nic of a node asks for the same reserved address and Kea gives it to the first REQUEST. Measured on xcat88-cn, which carries three nics on the provisioning bridge virbr-p88. Kea logged four solicits under one DUID in one boot, and granted 2001:db8:188::20 to whichever IA asked first; the others took pool addresses. The node then reported to xcatd from an address xcatd could not match to a node, so el10-x86_64-genesis-oe-ipv6 passed or failed by chance. genesis-bootnic reads BOOTIF and writes 16-xcat-genesis-bootnic.conf, which leaves DHCPv6 on the boot nic and puts every other nic on link-local. It follows genesis-duid, which already writes 15-xcat-genesis-duid.conf from the SMBIOS UUID before NetworkManager starts. The six cases pass with the file as committed, so the evidence is a mutation: writing ipv6.method=auto for the secondary nics, which is the behaviour before this change, reds only "the boot nic keeps DHCPv6 and every other nic does not ask for an address". 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!