The assertions added with this test required Socket6 and IO::Socket::INET6 on every RPM family, which contradicts xcat_server_inet6_optional_dependency.t and the reason it records: every call site loads the modules with an eval and keeps working on IPv4, so a hard dependency states a dependency the code does not have. The measurement that prompted the test still holds, and it is narrower than it looked. Both modules are absent on a Leap 15.6 management node because the openSUSE Minimal-VM image sets solver.onlyRequires = true in /etc/zypp/zypp.conf, so zypper installs no recommended package. dnf installs one, so EL and openEuler need no hard dependency. The test now reads requires and recommends separately per family: openSUSE requires both and recommends neither, EL and openEuler recommend both and require neither. The deb control files are read per package, since perl-xCAT has carried a hard dependency since before this rule. xcat_server_inet6_optional_dependency.t gains a pointer to the openSUSE exception so the two files do not disagree in prose. 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!