Daniel Hilst
2a5463659b
On a netplan-rendered node the reconfigure path takes the interface down unconditionally, while the `netplan apply` that brings it back is gated on reboot_nic_bool. In the diskful provision postscripts stage reboot_nic_bool is 0, so configeth downs the NIC and nothing brings it back until the node reboots -- over the very interface the postscripts are talking on. The other two arms pair their halves: the ifupdown arm answers `ifdown` with an unconditional `ifup`, and the redhat arm gates both the down and the up. Only the netplan arm takes one half. Nothing in the suite covers it. This drives the two blocks configeth actually executes -- the down-selection inside the modify branch and the restart block underneath it -- with `ip`, `ifdown`, `ifup` and `netplan` shadowed by shell functions, which bash resolves ahead of $PATH, so every call is recorded rather than run and the host's network is never touched. Six of the eight assertions pass already and are there to pin the arms that are correct: redhat gating both halves, ifupdown pairing its own, and the reboot_nic_bool=1 path doing the down before the apply. The two that fail are the bug. 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!