This branch is titled "provision a node over IPv6" and shipped one IPv6 xcattest case, makenetworks_ipv6_route_filter_unit, which is a unit-style check that no bundle names. Nothing ran against a management node to show that the DHCPv6 path works. makedhcp_dhcpv6_boot_intent builds its own state on the management node -- an IPv6 address on the provisioning NIC, a matching xCAT network, and a node that answers only on IPv6 with a fixed vpd.uuid -- and asserts four things a UEFI client depends on: makedhcp exits 0, kea-dhcp6 accepts the configuration it wrote, the reservation's DUID is the uuid with its first three fields reversed as the firmware sends them, and the bootfile-url is the RFC 5970 form with a bracketed authority. It then asserts the IPv4 configuration carries no reservation and no client class for that node. Every value is read out of Kea's JSON with python3 and compared for EQUALITY. A grep for bootfile-url passes on the key alone, and a check whose pattern appears in its own command cannot fail. The uuid is fixed rather than generated, because the expected DUID is derived from it. The case pre-cleans before it builds: xcattest stops a case at its first failed check, so the cleanup at the end does not run after a failure, and without the pre-clean a failed run would leave an address, a network and a node behind for the next run to measure. It needs no compute node and no image, so it runs wherever a management node is installed. ci/bundles/ipv6_dhcpv6.bundle and the el10-x86_64-ipv6 cell in xcat-core-ci-cd dispatch 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!