2
0
mirror of https://github.com/xcat2/xcat-core.git synced 2026-11-19 08:52:15 +00:00
Daniel Hilst 0f0c2a1f94 feat(xcat-core): run xcatd and the xCAT clients in the xcat_t domain
xCAT had no process domain. xcatd ran in unconfined_service_t, where the
policy constrains nothing, and each client command ran in the domain of its
caller. The module could therefore only grant access to other services.

xcat.te declares the xcat_t domain, the xcatd_exec_t and xcat_client_exec_t
entrypoints, the transition from systemd, and the transition from
unconfined_t for a client command. xcat.fc labels /opt/xcat/sbin/xcatd and
the two xcatclient scripts, which 115 command names reach through a symlink.

xcat_t is permissive, and the policy source declares it. The host stays
enforcing, and the CI collects the accesses the domain needs. The module
grants the domain one access of its own: the execute of the interpreter that
its Perl entrypoint names. A confined user domain gets no transition, so it
keeps its own confinement.

The module compiles at version 19 in the alma+epel-10-x86_64 mock root, and
the binary carries (typepermissive xcat_t) and both type transitions.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-14 16:55:21 -03:00
2024-05-07 16:43:07 +02:00
2018-11-28 10:28:17 +08:00
2021-04-05 09:34:37 -04:00
2018-02-09 01:03:46 -05:00
2024-04-20 02:18:05 +02:00
2026-04-17 03:14:04 -03:00

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) Documentation Status
Stable (latest release) Documentation Status

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!

S
Description
No description provided
Readme EPL-1.0 238 MiB
Languages
Perl 75.9%
Shell 13.1%
JavaScript 5.2%
Python 2.3%
Go Template 2.1%
Other 0.9%