Daniel Hilst
32eb096bfe
mock_build_owner parsed chrootuid and chrootgid from the text of the rendered configuration. A value set in an included file, an assignment with an inline comment or a double-quoted key, and an include after an assignment all gave a uid that mock does not build as. Also, a root build that stopped part way left root-owned 0644 logs in the result directories, and the next build, as uid 1000, could not append to them. mock_build_owner now asks mock's own loader, mockbuild.config.load_config, for chrootuid and chrootgid of the chroot that buildrpms.pl passes to mock -r. It fails with a clear message when mock is not installed. prepare_mock_resultdirs moves to XCAT::BuildUtils. It also gives the files already in both result directories to that owner, so a retry can append to the old logs and replace a package of the same version. When mock builds as the caller, nothing changes owner. native/mock_resultdir_owner.t gave the wrong uid for four of its configuration cases, and failed the 11 retry checks, before this change. 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!