Daniel Hilst
abc45b1f74
The previous commit deleted the $effective_provmethod override on the grounds that %image_hash never carries a provmethod. That was wrong, and the review caught it: makescript builds %image_hash, calls getImage() on it, and then hands the SAME hashref to getScripts(), which fills provmethod for every osimage from the osimage table. getDisklessNet() already reads that key the same way. The override was live, not dead. Restore it and say what is actually true in the comment. nodetype.provmethod is frequently an osimage name rather than 'install', and resolving it is the point of the lookup. Also close the gap that made the wrong deletion so easy to ship: reverting mkinstall's subiquity branch to its pre-fix body left the whole unit suite green. debian_mkinstall_subiquity_branch.t lifts that branch out and drives it inside a real loop, so the `next` it performs is the one under test, with report_node_error and the getipaddr seam stood in for. It calls subiquity_boot_params with no injected resolver, exactly as production does. The branch is selected out of debian.pm by what it contains rather than by where it sits -- there are four `if (using_subiquity(...))` in that file, and an earlier draft of this test silently matched the wrong one and ran past its block. Now observable, each verified by mutation: swapping $pkgdir and $httpport at the call site reddens the nfsroot assertion; reverting the branch wholesale fails the extraction guard rather than passing. 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!