Vinícius Ferrão
8253a4882e
makedhcp does not write the configuration of a DHCP server that site.externaldhcpservers names, so an upgrade leaves it without the iPXE feature options. OMAPI removes a host before it adds it again, so a host statement that such a server rejects loses the reservation of the node. Before it updates netboot=ipxe nodes on that server, makedhcp creates a host of its own whose statement tests every iPXE feature option, reads it back in a second omshell run, and removes it. Only the server can return the address of that host, so the nodes are updated only when it does. Otherwise makedhcp reports the server and leaves the reservations of those nodes unchanged. Other nodes and a local server get no check. Each run uses its own host name and address, as other xCAT servers can check the same server at the same time. The check opens no host before the create, because the omshell of Ubuntu 20.04 and 22.04 can hang on a failed open.
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!