configure_router_advertisements took the mgtifname of every IPv6 network in the networks table. site.dhcpinterfaces names the interfaces this server answers on, and the advertisement ignored it, so a management node restricted to eth1 still advertised itself on eth0. Every client on that LAN can then select it as a router, which is what restricting the interface was meant to prevent. The sub now takes the interface set the DHCP configuration was built from and skips a network whose interface is not in it. All three call sites already had the set: the ISC path in scope, and both Kea paths as a parameter. An empty or absent set is no restriction, so a cluster that sets no dhcpinterfaces keeps the behaviour it had. There are also two fixes to how radvd is started: - The service is examined on every call rather than only when the configuration file changed. A start that failed left the file already correct, so every later makedhcp returned on the file alone and never tried again while radvd stayed down. The call also moved out of the dhcpd6 restart branch of the ISC path, which a repeat makedhcp does not enter at all. - restartservice answers -1 when the service is not installed and the exit status of the command otherwise. Only the -1 was reported, so a radvd that failed to start was silent. Every nonzero result is now reported, and the message says which of the two it was. dhcp_dhcpv6_duid.t drives the sub directly for the service cases, because process_request reaches it only on some paths. Dropping the interface filter fails the check on an unserved network; restoring the early return on an unchanged file fails the restart check and leaves the one for a service that is already up passing; ignoring a positive exit status fails the two checks that name it. 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!