The ISC host commands from makedhcp and the Kea reservations get the same DUID for each value of mac.duid: firmware or no value, canonical, a DUID in uppercase, an invalid value and a node without a usable vpd.uuid. An invalid value is reported, and the node gets no DHCPv6 reservation in either backend. A change of mac.duid replaces the reservation of the node and keeps its address and bootfile-url. Query and delete match only the selected DUID, so the other byte order of the same UUID stays with the node that holds it. When a node is given the DUID of another node, both backends give the reservation to the node that makedhcp updates, and makedhcp -d of that node removes it, as they do for a MAC that two nodes share. An IPv6 node keeps its reservation when an IPv4-only node has the same vpd.uuid. The DHCPv4 hosts and reservations, IPoIB included, do not change with mac.duid, and IPv4-only nodes with an invalid DUID get no error from either backend. Single-node requests in a cluster of a thousand nodes read the rows of the requested nodes only. (cherry picked from commit 9e5e5d90fe98891fda1e4e5ef8adec16a09a7f7f)
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!