Daniel Hilst
a11bd9e43d
Fall back to an available DHCP backend on auto-selection. When the request is "auto" and the backend chosen for this OS is not installed, use the other one if it is, recording fallback_from so process_request can tell the operator which preferred backend is missing. A backend the admin forced through site.dhcpbackend still fails hard when absent, and "neither installed" still errors clearly. Fixes #7710. Answer makedhcp -q from the static host block on Ubuntu's ISC-limited releases. listnode now branches on _isc_static_host_fallback() before any omapi work and reads the node's fixed-address and hardware ethernet straight out of dhcpd.conf, so the query path never spawns the omshell its own write paths already avoid. A node with no reservation is now reported rather than answered with silence. Match the host-block markers exactly. _add_isc_static_host writes a fully determined pair -- "#xCAT host declaration for <node> aka host <hostname> start" and the "}" line carrying the matching end -- so both scans anchor on that whole shape through shared _isc_host_start_re/_isc_host_end_re helpers. The previous /\Q$node\E\b.*/ also matched at a hyphen, letting node "compute" act on "compute-01"'s block: the query could return another node's address and the delete could remove another node's reservation. _delete_isc_static_host also accepts an explicit line list now, so the scan is unit testable without file-scoped state. 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!