Seven of the ported unit files drive shell: they run bash -n on a product script, cut a function out of it with a regex and eval the copy, or write a fake executable into PATH. A .t runs Perl in process, so each one tested its own scaffolding as much as the product, and a reformat of the script would break it while a move of the code would not. The five bats files replace them and use the existing shell_source helper. ipv6_endpoint_helpers drives the four separate copies of xcat_endpoint_host from one table, because the scripts carry a copy each -- xcatroot runs in the dracut initrd, xcatpostinit1.netboot before /xcatpost exists, xcatinstallpost in the installer root -- and the copies must agree. ipv6_xcatdsklspost_endpoints uses XCATDSKLSPOST_SOURCE_ONLY to load the real parsehttpserver and format_host_port and asserts a bracketed authority survives a round trip. ipv6_syslog_forwarding covers the rsyslog bracket and the syslog-ng udp6 driver. ipv6_configeth_install_nic drives discover_install_nic_ipv6 against recorded "ip -6 addr show" output and pins that a temporary, tentative, deprecated or dadfailed address is never chosen. ipv6_updateflag_awk runs updateflag.awk against a loopback listener of each family and pins the bracket stripping. Each assertion was run against the unfixed script and fails there. Two gaps stay: allowcred.awk has no coverage, and the /inet6/ prefix updateflag.awk chooses cannot be covered, because gawk 5.3.0 reaches an IPv6 literal through /inet/ as well. 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!