Daniel Hilst
bca12ca29d
Two ways the Subiquity install could fail without saying anything useful. The boot flip read from the install monitor with no timeout. A monitor that accepts the connection and then never answers -- which #7759 shows is a state it gets into -- blocked the read forever, and with it the Subiquity late-command and the install. The retry loop could not help: it never reached the retry. Both reads now take -t 10, so five attempts are bounded at roughly two minutes and end in the failure that is already logged. The regression test stands up a listener that accepts and holds the connection; removing the timeouts fails it. mkinstall resolved the install server for nfsroot and fell back to the name when that failed: "getipaddr($instserver) || $instserver". The name is the original defect -- klibc's nfsmount cannot resolve one -- so the node panicked "can't parse IP address" at boot, on the node, with nothing reported on the management node. The management node knows at template time, so it says so there and skips the node, as the other unrecoverable per-node conditions in this routine do. 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!