Daniel Hilst
698bccf493
The bats stub returned one exit code for every "chdef netboot=", and the helper calls chdef twice: once to set the method to ipxe, and once to put the saved method back. With the stub failing both, "a netboot method that cannot be put back fails the case" passed on the FORWARD failure, so removing restore_rc=1 from the restoring branch left all 18 tests green. The test named a defect it could not detect. The stub now counts its netboot calls and fails the one the test names, so the forward chdef succeeds. The test asserts that forward call is in the call log, and matches the message only the restoring branch prints. Removing restore_rc=1 now fails test 8 and no other. docs/source/advanced/ipxe/index.rst said both methods run the same boot scripts, which stopped being true when the shim line became conditional on the method. It now says what differs, and states that Secure Boot reaches netboot=ipxe only: xnba.efi is unsigned, and grub2 nodes are out of scope. 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!