Vinícius Ferrão
cef02c6901
The two tests for this export never loaded the plugin. Each held a copy of the logic it checked. One copied the merge that builds the node and interface hashes. The other copied the payload the command sends. The only link to the plugin was a set of regular expressions over its source. The plugin could therefore change its merge or its payload while every assertion about behavior still passed. The expressions that were meant to catch that break when the source is only reformatted. Load the plugin and call makeconfluentcfg. The tables it reads and the client it sends to answer the calls the command makes. The driver disk test already does this for its own plugin. Every assertion now checks what the command emits. The reason recorded for the copy was wrong. The plugin loads with the library paths alone. It needs no management node and no database. The two files become one because they share that harness. Two files would put the same copy back in two places. 22 of the 37 assertions fail against the plugin as it was before this export existed.
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!