Daniel Hilst
a4f970d9be
specs/dhcp-wire.md gained a feature for the name the cluster's DNS learns -- S-74 to S-78. Four of the five had nothing asserting them, and dhcptest could not send option 81 at all, so the scenario a client uses to claim a name could not be written. dhcptest gains a `fqdn` step field carrying option 81, with the RFC 4702 flags written as a prefix (`S:node01`, `N:node01`, `E` for wire format). It gains two targets: `fqdn_flags` for the flag letters, and `dns_name` for the name the reply says the node will be known by -- option 81 when the server sent one, option 12 otherwise, because Kea answers an option 81 request in option 81 and ISC under `ignore client-updates` answers in option 12 only. That is the same shape as `bootfile`. netboot-methods.conf asserts S-75 twice, once for a name claimed in option 12 and once in option 81. dhcp_ddns_policy.t asserts S-76, S-77 and S-78 on both backends. Checked against kea-dhcp4 2.4.1 and isc-dhcpd 4.4.3-P1 on xcat26-mn: both scenarios fail on a server with no per-node name and pass on one that has it. Four mutations of the code under dhcp_ddns_policy.t are each caught. 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!