Daniel Hilst
06cc43c863
Every service node defect in this change set was a generated artifact that was already wrong before any node booted: a repository file that enabled no builder repo, a template that resolved to the wrong installer, an exports line that was never written. The tests that caught them are one file per fix, so each knows one defect and together they know no defect class. A fix nobody has made yet is covered by none of them. service_node_artifacts_el.t renders the artifacts an EL service node needs from one fixture and asserts each: the builder repository per release and vendor, including that EL8 is powertools and not crb; the template the service profile resolves, which must not be a Subiquity one; and the export line for a local directory and for a re-exported mount, where an absent fsid is what made a service node export nothing. A missing module or sub fails rather than skips, and the file reports every gap instead of dying at the first, because on an unfixed tree this test is the gap report. Measured: 17 assertions pass on the branch, and the base fails two of them by name. It does not cover the boot half -- the lease, the tftp handover, the mount the installer performs -- so it replaces no end-to-end run. It replaces the 45 to 90 minutes those runs cost in the ROUNDS of a minimization. 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!