Daniel Hilst
5570a4c64a
reg_linux_diskfull_installation_flat fails on ubuntu-22-ppc64le-devel and ubuntu-24-ppc64le-devel in build #121 of xcat-core-devel-ubuntu-cd. The Subiquity installer starts, errors in its early-commands, tars /var/log/installer to port 8080 and reboots, nine times in 75 minutes. No system is ever installed, so the address answers from the live installer and the case ends on "root@xcat25-cn: Permission denied (publickey,password)". mkinstall in xCAT-server/lib/xcat/plugins/debian.pm selected pre.ubuntu.subiquity and then replaced it with pre.ubuntu.ppc64 for every ppc64 node, whichever installer was in use. pre.ubuntu.ppc64 writes a partman recipe, and the early-commands append it to /autoinstall.yaml, which Subiquity cannot parse. pre.ubuntu.subiquity offered a UEFI branch and a BIOS branch, so a ppc64el node took the BIOS branch and was given a bios_grub partition. POWER firmware loads the boot loader from a PReP partition. install_prescript now returns the script from the installer and the architecture together, and the ppc64 script is reached only on the debian-installer path. pre.ubuntu.subiquity gains a PReP branch, taken when uname reports a POWER machine, which flags an 8M first partition prep and makes that partition the grub device. debian_install_prescript.t and the PReP case of ubuntu_subiquity_storage.t fail without these changes. 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!