Daniel Hilst
9da497cac4
Three things the wire cases turned up, only the first of which is xCAT answering a client wrongly -- the other two never got as far as an answer. kea-dhcp4 would not start at all. The ONIE class named option "www-server", which xCAT's dhcpd.conf declares as code 114 = string but which means the standard option 72 to Kea -- a list of IPv4 addresses, so an installer URL in one is a configuration error and the whole Kea pass of the wire cases never ran. Naming the code instead says the same thing to both. ISC answered a request for an address on a network it has never heard of with silence, where the spec says DHCPNAK, because "authoritative" was written into each subnet declaration and read from the subnet the requested address belongs to -- which, for this case, is none of them. It is now global as well, which is what Kea's authoritative:true already covered. The remaining two were the cases asking the wrong question. ISC sends an option when the client asks for it, so an ONIE case that never put 114 in its parameter request list could not see it however the class was written; and the common-option case announced a PXEClient vendor class while asserting the cluster's lease time, which is the ten-minute firmware lease of S-51 rather than S-50. S-50 now says which clients it is about.
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!