Daniel Hilst
0f708b96a6
check_provisioning_source.sh required the management node's httpd access log to gain lines after the baseline. The three hierarchy cases take the baseline after SN_setup_case has provisioned the service node. After that point a correct hierarchical provision leaves the management node serving nothing, so its log does not grow. On the xcat42 EL9 cell the service node served the compute node 252 boot-payload requests and the management node served 0, and the check still reported "no httpd access log with new entries could be read on xcat42-mn-dhilst". reg_linux_diskless_installation_hierarchy failed for that message. The guard now requires the log to hold lines, not to hold new ones. An empty log still fails, because it makes "the management node served nothing" a property of the file instead of a measurement. check_provisioning_source.bats asserted the removed behavior in "a management node log with nothing new fails the check instead of reading as silence". That case now asserts the opposite, and a second case covers the empty log. Both fail against the unfixed script. 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!