sles.pm matched ipv6 nowhere in 2801 lines and the SUSE templates wrote "<bootproto>dhcp</bootproto>" directly, so an IPv6-only SUSE node had no way to configure its installer: DHCP cannot serve it, and SUSE has no static handoff on the kernel command line. _autoyast_network6 builds the networking section of such a node, with a static interface, the address of the node and a prefix length, which is what AutoYaST takes for IPv6 instead of a netmask, and a default route carrying the IPv6 gateway. The #YAST2NET6# directive chooses between that and the DHCP block the templates carried. An IPv4 node gets that block unchanged, which is why the existing #YAST2NET# was not used: its DHCP arm renders something else, and leap15.6 is a gating cell. compute.leap15.tmpl and compute.sle15.tmpl take the directive. autoyast_ipv6_network.t covers the section. Emitting a netmask instead of a prefix length fails 2 of its 11 assertions. The IPv4 output of the directive was compared with the text it replaced and is identical. 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!