The xcat policy module granted httpd read of /tftpboot and let xcatws.cgi connect to the xcatd port. Five further accesses were measured denied on a management node and are not granted, so an enforcing node fails at them. httpd mmaps the per-node xnba boot config it serves out of /tftpboot. read_file_perms does not hold map, so the module now grants mmap_read_file_perms. Two sites recorded this denial three days apart, on xCAT 2.19.1 and 2.20. xdcp and "updatenode -F" copy /etc/shadow to the nodes and into a rootimg. rsync_export_all_ro holds that read and rsync_full_access does not grant it, because shadow_t is not in non_auth_file_type. rsync also writes a target it created at mode 0000, which needs CAP_DAC_OVERRIDE. Both rules are reached only where rsync runs in rsync_t, which needs a system-service caller. genimage installs packages into a rootimg with yum in a chroot, and useradd and groupadd read the rootimg /var/run symlink from the rpm scriptlets. The symlink carries public_content_t because the rootimg is under /install, and the base grant for that read names public_content_t nowhere. The module compiles at version 19 in the alma+epel-10-x86_64 mock root, and the five types reach the binary. 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!