Daniel Hilst
a5cc24c18f
DHCP backend auto-selection fails hard when the backend it prefers is not installed. The xcat metapackage's "isc-dhcp-server | kea" Depends guarantees isc-dhcp-server, while auto-selection prefers kea on 22.04+, where kea arrives only through Recommends. An apt run that skips recommends therefore leaves a node with isc only, auto picks the absent kea, and makedhcp errors out on a freshly installed management node (#7710). makedhcp -q re-enters omshell on the very releases whose write paths avoid it. xCAT already records each reservation as a static host block in dhcpd.conf on Ubuntu's ISC-limited releases because their ISC DHCP 4.4 omshell can wedge at 100% CPU and never be reaped, but listnode still called _omshell_query_host unconditionally. Both host-block scans also match the node name loosely: /\Q$node\E\b.* start$/ matches at a hyphen, so "compute" matches the "compute-01" marker -- a query can answer with another node's address and a delete can remove another node's reservation. Cover all three: the auto-selection fallback, a query answered from dhcpd.conf without omshell, and exact node-name matching for both the query and the delete. 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!