An unknown client on an IPv6 provisioning network gets no network boot script. mknb builds its list of networks from my_nets and my_hexnets, and both skip inet6 on Linux, so nothing is written under xcat/ipxe/nets and the client has nothing to fetch. Where an address does reach a script it is written as "xcatd=" . $address . ":$port". For 2001:db8:177::1 that is xcatd=2001:db8:177::1:3001, which parses as an IPv6 literal with no port, so Genesis contacts a different address and reports nothing. The same concatenation builds the POWER HTTP URLs and the grub2 roots. xnba.pm and destiny.pm already bracket an IPv6 address through NetworkUtils::xcatd_cmdline_address and format_uri_host, so the node files were correct and the net files were not. NetworkUtils gains my_nets6, which returns the host's global IPv6 networks keyed the way my_nets keys its IPv4 ones, and ipv6_network_address, which masks an address to its prefix. my_nets keeps its IPv4-only behaviour: lsslp.pm and PPCdb.pm read its keys with dotted-quad arithmetic, so an IPv6 key there would be a wrong answer rather than a new one. my_hexnets keeps its own, because a hexnet is a PXELINUX file name built from a hexadecimal IPv4 prefix and DHCPv6 has no equivalent. mknb merges my_nets6 into the networks it writes nets/ scripts for, asks getipaddr for the IPv6 addresses of site.master as well, and takes every xcatd= value and every HTTP authority from the two formatting helpers. mknb_xcatd_address.t and networkutils_my_nets6.t fail without this change. 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!