Daniel Hilst
7082fabe0b
ubuntu_subiquity_boot_flip.t bound 3002 on the loopback to check it was free and skip_all'd when it was not. 3002 is the install-monitor port, so on any management node xcatd is already listening there -- which is precisely where the suite runs. The CI log for #7761 reads ubuntu_subiquity_boot_flip.t ... skipped: port 3002 is not available on the loopback interface so all 139 lines and 12 assertions never executed once, and never would have. Coverage that reports as a skip is worse than none, because the gap is invisible. Take an ephemeral port from the kernel and rewrite the extracted command to use it, in both the /dev/tcp target and the log message. The port number is not what is under test -- the retry-and-log behaviour is. The template's own port is read out of the command rather than hard-coded, and asserted to be 3002, so moving the install-monitor still leaves the file covering something instead of silently testing a port nothing uses. 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!