mknetboot excluded a statelite node from the static IPv6 address with no reason recorded, and mksysclone had no IPv6 code at all. Both reach the same dracut networking as a diskless node, so both asked DHCPv6 with the identifier their initrd generates. A reservation matches one identifier, so the node took a pool address and no boot URL. Statelite now takes the same path as diskless, and mksysclone renders the address beside the Genesis kernel it boots. anaconda_ipv6_statelite_sysclone.t drives both commands against a SQLite fixture. Restoring the statelite guard fails one of its six assertions and removing the mksysclone block fails another, while the diskless assertion survives both, so the gate did not move for diskless. debian.pm records why the Ubuntu live filesystem is mounted over IPv4. The comment blamed casper, which passes nfsroot= through untouched; klibc nfsmount is what cannot read an IPv6 server. Measured on noble: "[2001:db8::1]:/export" and "2001:db8::1:/export" both answer "need a path", while "192.0.2.1:/export" is accepted. 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!