Daniel Hilst
873ad1d41c
An administrator sets site.cleanupdiskfullxcatpost, deploys a diskfull node, and /xcatpost is empty. The next updatenode run downloads the postscripts again and leaves them there. /xcatpost is mode 0755 and most of what lands in it is world-readable, so material the administrator was told is gone comes back on every maintenance run and on every reboot. xcatdsklspost is the script that repopulates /xcatpost on all of those paths, and it reads only CLEANUPXCATPOST. CLEANUPDISKFULLXCATPOST reaches the node in the same mypostscript, exported by the site table, and no code reads it. Only xcatinstallpost does, and that runs once, at install. Read it in append_xcatpost_cleanup with the rule xcatinstallpost uses: remove the postscripts when the run returns 0, keep updateflag.awk, and leave everything in place after a failed run so the node can be examined. xCAT-test/bats/xcatdsklspost_xcatpost_cleanup.bats captures this. Three of its six tests fail on the previous commit. 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!