Vinícius Ferrão
63470e4fe0
Each packed format must publish the SHA-256 checksum of the new archive next to it, readable by nodes. The checksums of other formats must stay, for nodes that already download them. A pack that fails while it compresses, lists or reads the files must keep the previous checksum. A pack must publish the checksum also when the image and the site turn the check off. An image that turns the check on overrides the site, and 'no' and '0' both turn it off. While the archive is replaced, the checksum file must list the new and the previous archive, also one packed before the check. The previous metainfo must be gone by then. Then the checksum file must list only the new archive. A failed rename of the checksum list, the archive or the metainfo must leave the previous archive, checksum and metainfo, also without hard links. When the previous archive can be neither linked nor copied, nothing must change. A copy under umask 0077 must keep the mode of the previous archive. A checksum file that keeps the previous line must not fail the publication. A pack whose previous metainfo cannot be moved aside must keep the previous archive and checksum. A previous archive that cannot be put back must be kept outside the staging directory, with its metainfo and checksum.
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!