On an EL10 management node whose own name resolves to both families, xcatconfig writes a link-local IPv6 address into site.master and site.nameservers. Measured on an AlmaLinux 10.2 node: getent reports fe80::4054:ff:fec9:9ad2%2 before 192.168.201.154, and xCAT::NetworkUtils->getipaddr($hostname) answers fe80::4054:ff:fec9:9ad2%mgmt0, which xcatconfig stores. A node on another link cannot reach that address, and the %zone form is not a literal isIpv6addr or any consumer of site.master accepts. getipaddr resolves through Socket::getaddrinfo with AF_UNSPEC when no family is asked for, and returned the first entry getaddrinfo gave. prefer_routable_addresses orders address literals so a routable one comes before a link-local one and removes the zone identifier, and _addrinfo_routable_first applies the same order to the getaddrinfo entries before getipaddr reads the first. A link-local address is still returned when the host has no other. networkutils_linklocal_preference.t covers the order, the zone identifier and both link-local ranges. Removing the routable split fails 4 of its 10 assertions, removing the zone strip fails 3, and treating 169.254.0.0/16 as routable fails 1. 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!