Daniel Hilst
f5e3f7775b
The CI run is now three phases in order: the perl and bash unit tests, the ci_test set, then the DHCP on-wire cases. The wire cases carry dhcp_wire and deliberately not ci_test. They are the only cases that do not leave the machine alone while they run -- a veth pair appears, site.dhcpinterfaces and site.dhcpbackend change, the DHCP daemon is stopped and started -- and although each one restores all of it from a trap, a ci_test case running in between would be sharing a management node that is mid-reconfiguration. Holding them out of the set is also what stops them being run twice. run_dhcp_wire_test runs the whole set once per backend installed: against ISC, then against Kea, each pass bracketed by `dhcpfixture.sh backend-setup` and `backend-teardown`. It reports separately from the fast regression test and counts case runs rather than cases, since each case is run once per backend and each failure carries the backend name. The phase writes its own xcattest configuration without a dhcpbackend key: xcattest applies [Table_site] before every case, so the regression conf's `dhcpbackend=isc` would have reset the backend case by case and left the run silently testing ISC twice.
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!