mknb writes the network boot scripts of an unknown client from my_nets and my_hexnets, both of which skip inet6 on Linux, and it builds every xcatd= value by concatenation. No test covers either, so an IPv6 management node gets no script, and an address written as xcatd=2001:db8:177::1:3001 reads as a valid literal with no port. mknb_xcatd_address.t stubbed the whole of xCAT::NetworkUtils, so the formatting helpers were absent from the harness and could not be measured. The three harnesses now load the real module and replace only the probes that read the running host's interfaces. The new assertions cover the nets/ scripts, the UEFI and elilo entries, the POWER URLs, the s390x APPEND line and the grub2 roots for one IPv6 network, and networkutils_my_nets6.t covers my_nets6 and the prefix masking. 16 of the mknb assertions fail on this commit, and the my_nets6 file does not run at all for lack of the subroutine. 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!