Daniel Hilst
11848cafcc
The hierarchy cases had no assertion that could fail on a flat provision. Nothing in xcatinfo, in nodetype.status, in the mount type or in the synclist file records where the compute node fetched its kernel, initrd and root image. check_provisioning_source.sh answers that from the httpd access logs. The xNBA exchange hands out an http:// filename, so every part of the boot payload is a request logged against the compute node's address on the server that answered it. The script counts those requests on the management node and, through xdsh -e, on the service node. It fails unless the service node served the compute node and the management node served it nothing. It also fails when either log is unreadable or the management node log is empty, because a gate that cannot measure must not pass. It counts requests and not bytes: a 304 or a HEAD carries no body, so the management node can answer for the compute node and still log 0 bytes. The PXE ROM exchange stays outside the check. That branch hands out xcat/xnba.kpxe over TFTP, which httpd never sees, and the file is the same binary on both servers. check_provisioning_source.bats drives the script with the two logs and the xCAT commands stubbed. Removing any one of its guards makes the test that names that guard fail. 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!