Vinícius Ferrão
8816ea47f1
The test packs cpio and tar archives with gzip, xz and pigz, and squashfs images, on the Red Hat path. A wrapper around the compressor, mksquashfs, cpio or find records the file under the final name while the pack runs, and then runs the real tool or fails. It checks that nodes get the previous archive during the pack, that a pack whose compressor, cpio or file listing fails keeps the previous archive, metainfo and other formats, that a successful pack replaces them, and that no temporary file is left. The next pack removes a temporary file or directory that an interrupted pack on the same host left, and keeps one that another host is writing. For a StateLite tree, it checks that a pack that fails while listing the files, compressing them or creating the temporary directory restores the files that packimage switched, and that a retry keeps them. When a file cannot be moved back, the original and the previous archive must stay, and the next pack must refuse to run. A pack must wait while another host holds .packimage-publish. When a pack that did not finish left the lock, the next pack must fail, name the holder, and keep the previous archive and the lock. With --tracker, ctorrent must build the metainfo from the new archive under its final name before the archive is replaced. A ctorrent failure must keep the previous archive and metainfo, and so must a previous metainfo that cannot be removed.
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!