Daniel Hilst
ad91ffee51
build_xmldesc reaches its UEFI path only for riscv64, so no test covers an x86_64 guest that asks for UEFI. The existing kvm unit tests cannot cover it either: they read kvm.pm, extract four routines with a regex and eval a copy, which keeps passing when the original changes. kvm_uefi_firmware.t loads the plugin itself, with Perl stubs for the database, the monitoring dispatcher, the thread helper and the libvirt binding. It calls build_xmldesc and reconfigvm, and reads the domain XML they return. process_request already set $parser, $node, $confdata and $updatetable before it called the domain builder. They are package variables now, so the test sets them the same way. The plugin reads them unchanged. Six checks fail on this commit. The guest states no firmware and no machine type, its disks stay on a bus q35 cannot carry, the rewritten guest asks for no firmware, and a firmware value libvirt cannot select is accepted in silence. 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!