Vinícius Ferrão
84598e7c8c
The shared Ubuntu lists serve every release and architecture without a list of its own, and ospkgs hands the whole list to one apt-get install, so one unknown name loses every package on it. ntp and ntpdate are gone from 26.04. libodbc1 is the unixODBC runtime name up to 22.04. libvirt-bin is gone from 20.04 on and qemu-kvm from 22.04 on. The shared lists keep ntp and ntpdate, so releases up to 24.04 keep the daemon they had. 26.04 gets release lists that carry chrony. unixodbc replaces libodbc1 on every release, and the odbcsetup postscript keeps its runtime. The service lists add libdbd-pg-perl beside libdbd-mysql-perl, as a service node may run the xCAT database on PostgreSQL. libvirt-daemon-system with libvirt-clients replaces libvirt-bin from 18.04 on; 12.04, 14.04 and 16.04 keep kvm lists with the old names. qemu-kvm was a transitional name for the emulator of the host architecture, and no current release has one name for that. Per-architecture kvm lists name the native one: qemu-system-x86 on x86_64, qemu-system-ppc on ppc64el, qemu-system-misc on 24.04 riscv64, with ppc64le linked to ppc64el as the other lists do. The shared kvm lists fall back to qemu-system, which carries every emulator, so an architecture without a list of its own still gets one. On 26.04 riscv64 libvirt-daemon-system depends on qemu-kvm or qemu-system and nothing provides qemu-kvm, so apt installs that fallback there whatever the list names. Every kvm list names qemu-utils: ospkgs installs without recommends, and libvirt needs qemu-img for the qcow2 volumes kvm.pm creates.
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!