The SELinux page told the operator to run chcon -R -t public_content_t over the image root to repair a published artifact that kept an older type. That command walks into rootimg and rootimg-statelite, so it replaces the labels of the guest operating system with public_content_t. The xcat.fc comment carried the same advice. chcon also writes a type that no mapping selects, so the next relabel of a path that has a mapping reverts it: the repair held only until then. The page now maps each published artifact with semanage fcontext and applies the mapping with restorecon. Each expression names one regular file directly below the image root, so no path in either guest tree matches one, and both trees keep the <<none>> of the packaged mappings. The procedure reads the publication directory from site.installdir, and a site that moved it maps the configured directory and keeps both guest trees out of that mapping. The page says why a tree mapping over the image root is the same defect as the chcon. xCAT-test/native/selinux_image_repair.t passes 170 of 170 checks with the documented procedure. With the chcon of the previous page it fails 101, 36 of them guest labels. selinux_docs.t fails 7 of 26 on the parent commit. 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!