Vinícius Ferrão
005a32a721
The sudoer postscript created the xcat account with the fixed password rootpw. The rebased change from #6166 moved the password to the -p option, which shows it in ps on the node and spreads it over postscripts attributes. The postscript now asks the management node for the password field of the passwd row key=system,username=<sudoer> over getcredentials, the way remoteshell gets the root hash under secureroot, and applies it: the hash, or "!" when the table has no password for the account. sudo and the SSH key are granted only after that. A missing reply, a refused request, or a failed usermod fails the postscript and leaves the account unprivileged. -u still selects the user name and defaults to xcat. -p is rejected. An existing login account is kept, with the other keys in its authorized_keys. Root, accounts outside UID_MIN..UID_MAX, and accounts without a login shell are refused. The sudo rule lives in /etc/sudoers.d/xcat-sudoer, which records its account: a rerun with another name revokes the rule, the password, and the cluster key of the previous account, and the lines the old postscript appended to /etc/sudoers are moved out after visudo accepts the result. Every privilege write is checked, and a failed run removes the managed rule. Without sudoers.d the rule is appended once to /etc/sudoers.
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!