Daniel Hilst
26e8e277ef
siaddr comes from noderes, in an order neither backend had right. ISC read xcatmaster only for petitboot and onie, so every other node in a hierarchical cluster was sent to the management node rather than to its service node -- and even for those two the address went into the URL without going into siaddr, so one reply named two different machines. Kea read xcatmaster for every node, but when nothing named a server it used my_ip_facing rather than the subnet's value, which is a different answer whenever networks.tftpserver names a third machine. Both now read next_server_for_node: the node's tftpserver, then its xcatmaster, then -- only for the methods that build a URL and so need an address in hand -- the interface facing the node. A node that named none of them inherits the subnet's value, which ISC states in the subnet and Kea states by leaving next-server out of the reservation. An xcatmaster that does not resolve is now an error on both rather than silence on one: it is a misconfiguration, and sending the node somewhere else instead hides it. Appendix A rows 26 and 27. Unlike the rest, these two are not in xcat-internal#175 -- the wire cases found them.
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!