Sixteen assertions on this branch matched a regular expression against the source of the code they test. Such an assertion passes when the code is moved somewhere it never runs, and fails when the file is reformatted and nothing has changed: a perltidy respace of updatenode.pm:1606 turned updatenode_ipv6_endpoint.t red with the behaviour unchanged. updatenode_ipv6_endpoint.t now runs updatenoderunps and updatenodesoftware and reads the xdsh command each one dispatched. It also covers the service node name that has no usable endpoint, which the regular expressions could not reach. anaconda.pm built the debug syslog kernel arguments inline inside two large subs. Move each to its own sub, _netboot_syslog_kcmdline_args and _install_syslog_kcmdline_args, and render them in the test. An unusable server name now gives no syslog arguments, where it gave "syslog.server=" with nothing after it. pping is a program with no sub API, so the nmap and fping command building moves to xCAT::DSHCore as nmap_ping_command and fping_ping_command, and pping stays the caller that forks and execs the list. credentials_ipv6_callback.t read allowcred.awk as text, and ran gawk from a .t. The awk program is covered by xCAT-test/bats/ipv6_allowcred_awk.bats, which starts it and speaks the credential protocol to it over both families. Stubbing Socket6 and IO::Socket::INET6 in %INC also unskips the four _open_callback_socket assertions, which skipped where the suite runs. 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!