Daniel Hilst
994b47a947
The stop/disable sat below the `exec setupntp.traditional` that the ntpd path takes, and setupntp.traditional never mentions timesyncd, so on that path it was never reached: ntpd and timesyncd both ended up disciplining the clock. Hoist it above the hand-off so both backends get it, guarded on systemctl existing -- the ntpd path is taken precisely when systemctl may be absent. The comment justifying it was also wrong, and is corrected: chrony and ntpsec both Conflicts: time-daemon, so installing either already displaces timesyncd. That only helps when an install actually happens; on a re-run, or where the daemon was already present, timesyncd is still enabled, which is what this covers. The four timesyncd assertions in makentp_ntp_deps.t are dropped rather than repaired: they ran over the section from `check_exec_or_exit cp cat logger grep` onwards, which only the chrony path reaches, so the code they covered is no longer in their window. setupntp_timesyncd_both_backends.t drives both paths instead. 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!