Daniel Hilst
1b40f59348
ipxe_secureboot_shim.sh reads every attribute and the nodeset state before the first mutation, refuses a state it cannot put back, and replays the saved state verbatim. read_attr keeps the exit status of lsdef instead of the status of the sed that follows it, so a lookup that failed no longer reads as an attribute that is unset. must_read ends the case on a failed lookup, before the chdef and the nodeset that change the node. This is what stops the restoration clearing a provmethod or a netboot method the node really had. The restoration replays the whole string nodeset stat reported, so a state that carries an argument goes back with it. A state the helper cannot replay ends the case while the node is untouched: install, netboot and statelite are deprecated and the restoring nodeset rejects them, and iscsiboot, image, winshell and sysclone read rows this case never saved. The restoring chdef also puts back nodetype.profile, which nodeset osimage= overwrites from the osimage row. xCAT-test/bats/ipxe_secureboot_shim_restore.bats covers it. Against the previous commit the four refusal cases exit 0 and print IPXE_SHIM_OK after calling nodeset osimage= on the node. 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!