Vinícius Ferrão
cb6483c866
A package upgrade keeps the DHCP configuration of an older makedhcp -n, which does not declare the iPXE feature options. makedhcp without -n then adds the rules of the upstream loader to it. dhcpd rejects a subnet or an OMAPI host statement that tests an undeclared option, and Kea never finds a sub-option of option 175 without its definition. makedhcp without -n now adds the missing declarations to an ISC configuration that xCAT wrote, after its gpxe option space, writes it and restarts dhcpd before it changes a subnet or a host. Declarations with any blanks count. It stops when the configuration declares no gpxe option space, or when it cannot write the file or restart dhcpd, because OMAPI removes a host before it adds it again. A missing configuration, or one that xCAT did not write, still gets a new one, which declares the options. A marker file beside the configuration records a restart that has not happened yet, so the next run restarts dhcpd before it changes a host when a run stopped before the restart or the restart failed. It adds the missing definitions to an existing Kea configuration, and Kea restarts, also when the Control Agent applies the host reservations. A site definition of option 175 without the gpxe encapsulation stays, because option data can name it, and makedhcp stops with an error that names the fix.
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!