node_pingable asks ICMP up to PING_TRIES times and stops at the first answer, so a few seconds of loss after a node boots no longer forces a second full rinstall. A node that never answers still reports non-pingable, and the caller still vetoes it: the signal is kept, not removed. The probe is lifted into a function with a main-guard rather than left inline, so a bats test can drive it without running a provisioning loop or needing an xCAT database. Nothing sources this script -- all nine callers execute it -- so the guard changes no caller. The happy path is unchanged at one ask. A node that never answers now costs PING_TRIES asks before the verdict, which is under a minute against the six minutes of the reinstall it decides. retry_install_transient_icmp.bats passes 5 of 5. Removing the bounded retry fails assertions 2 and 4, which are the retry properties, and leaves assertion 3 passing -- a node that never answers is still not pingable. That assertion is the discriminator: without it the change could not be told apart from deleting the check, which would turn a flaky probe into one that cannot fail. xCAT-test/bats is 596 passed, 19 failed. All 19 are xcatroot_rootimg_checksum.bats, which reports 0 passed and 19 failed on upstream master with none of this branch applied. 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!