Daniel Hilst
980b7de169
Appendix A rows 15 to 18, the remaining spec decisions where the two backends answered the same client differently. Row 15, a loader that is not on disk is not named. The ISC architecture chain named every loader unconditionally, so a client whose loader was never built spent a full TFTP timeout it could not diagnose; the Kea side had always left the class out. The chain is now built from a list of gated branches rather than a literal block, because dropping a branch from a literal if/else if chain can leave a leading "} else if", which dhcpd rejects outright. Row 16, a *NOIP* interface draws no reply. Kea discards a packet assigned to the class named DROP, and only one such class may exist, so every dropped MAC in the cluster shares it and the user-context records which node each belongs to. Syncing one node merges into that list and removing one node prunes only its own entries, so makedhcp for a single node cannot bring another node's interface back. Row 17, a node that boots from disk, and row 18, a node deferring to proxydhcp, are decided per node. Kea host reservations outrank every client class, so the reservation has to fall silent -- an empty boot-file-name -- and let the class carry the answer. Rows 19 and 20 landed earlier and dictated the same shape: the reservation names nothing and two mutually exclusive classes, one for the vendor and one for "not the vendor", decide between them, because Kea evaluates every class independently and has no else.
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!