Vinícius Ferrão
6660ca7a06
A node could not tell a damaged root image download from a good one, because packimage published nothing to check it against. packimage now writes rootimg.<suffix>.sha256 in sha256sum format next to the archive. It builds the checksum in the temporary directory with the archive, and publish_rootimg publishes both under the publication lock. A pack that fails before publication keeps the previous archive and checksum. When packimage removes the other formats, it keeps their checksums, so a node that already downloads one can still check it. Until the archive is replaced, the checksum file lists the new and the previous archive. publish_rootimg computes the line of a previous archive that has none. The published archive then matches a line of it at each step, also when the publisher is killed. The previous metainfo leaves first, so it never describes the new archive. publish_rootimg keeps a link to the previous archive, or a copy with its mode without hard links. When a step fails, the previous archive, checksum and metainfo stay or come back. When it can keep the previous archive in neither way, it publishes nothing. When it cannot put the previous archive back, it keeps it in a .rootimg-previous-* directory and names that directory in the error. The new site.rootimgchecksum attribute is yes by default, and the rootimgchecksum attribute of an osimage overrides it. They tell nodeset whether nodes check the archive. packimage publishes the checksum whatever their value, because nodes with older boot entries can still check.
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!