The selinux cases cover the management node and a compute node. A hierarchical cluster has a service node, which installs xCAT itself and serves /install and /tftpboot to its own nodes, and nothing measured it under SELinux. A statelite node was not measured either, although node_modes resolves it to disabled on purpose. selinux_sn_enforcing reads the provisioned service node: getenforce, the kernel command line, the xcat policy module, the labels of /install, /tftpboot, /opt/xcat and /xcatpost, a restorecon dry run that must find nothing to relabel, xcatd active, and no xCAT denial since boot. selinux_sn_per_node_switch sets noderes.selinux on the service node and reads the mode out of the kickstart that nodeset writes for it, in all three directions, and checks that a value on the compute node does not reach the service node. selinux_cn_statelite_disabled_by_design asks for enforcing on a statelite node and requires selinux=0 on its boot configuration, with nodeset saying why. selinux_bundle.t now keeps a service-node case out of the management-node bundle, the same way it keeps a compute-node case out. 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!