Vinícius Ferrão
38cad9c5bb
For the RHEL 7/8 NFS path, enablekdump created var/crash and a dummy proc file at the root of the shared dump export, from every node, at deploy. It also mounted the export over a general-purpose directory such as /mnt. kdump checks that the dump path exists on the target when it builds the initrd, so the path has to exist at deploy time. Create only this node's own subdirectory, $NODE/var/crash, and point kdump.conf at path /$NODE/var/crash. Each node now writes only under its own subdir, so nodes no longer share or collide at the export root, and the dump lands in the node's directory. The setup mounts a dedicated /mnt/kdumpsetup rather than a general-purpose directory. The dummy proc file only ever mattered to the RHEL 7 dracut check, which wants root= to look like a real filesystem. Keep it for RHEL 7, per node, and point root= at $KDIP:$KDPATH/$NODE. RHEL 8 no longer writes it. This design was identified by a lenovobuild change and validated on a running node: a real kernel panic saved the vmcore under the node's own directory, and nothing was written to the export root.
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!