Daniel Hilst
dfa22e3650
Addresses three concurrency-safety defects raised in review of the parallel buildrpms.pl work: 1. Per-target build lock was released immediately. The flock filehandle was a lexical (my $blk) scoped to the guard block, so it was destroyed -- and the lock dropped -- as soon as that block exited, before any worker forked. The "intentionally leaked" comment did not match the code. Hold the handle in a file-scoped $BUILD_LOCK_FH so the fd (and the lock) live for the whole process; forked children inherit the fd but their exits never release it. 2. Build failures were silently swallowed. buildspkgs()/buildpkgs() called sh_retry() in void context, so a mock build that failed all retries returned non-zero into the void; the child then exited 0 and the parent's run_on_finish ignored the exit code. The parent could therefore index and GPG-sign a repo that was missing packages and still exit 0. Now sh_retry failures die in the child, run_on_finish records any non-zero child, and the run aborts before update_repo and again before signing if any child failed -- never publishing a partial core. 3. Abort cleanup unmounted unrelated builds. sweep_mock_mounts() lazy-unmounted every bind under /var/lib/mock, which on a shared host tears out the live chroots of concurrent, unrelated builds. Scope it to this run's own chroots (each chroot dir plus its -bootstrap sibling), passed in from abort_builds. 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!