Vinícius Ferrão
d5f882291d
The manual page and the usage message of nodestat give the option -f|--usefping. The preprocessor of the request knows no option f, and the handler of the request spells the long name useping, so --usefping does nothing. An administrator who follows the manual page gets the nmap path, and gets no message that says why. The two places also read different specifications, so an option that one place accepts can reach the other place and take a different meaning. Put the specification in one routine, and let both places read that routine. Give the name usefping to the option, and keep useping as a second name. That spelling has worked since 2.14.2, so a site can have it in a script. The long name of the fping option starts with the same letters as usemon, so --use and --us become names that Getopt::Long cannot decide. Those two abbreviations select usemon today. Keep them with usemon, or an administrator who monitors with them loses the monitoring and gets no message. The change has two other effects. The abbreviations --use and --us no longer select fping as well, which they did only because the two places read different specifications. The bundles -mf and -fm now select both options, which they did not do before. Recovered from the lenovobuild branch.
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!