The SELinux page carried the repair in two blocks. The first mapped the published artifacts and ran restorecon over the image root. The second mapped the publication directory and excluded both guest trees. An operator with site.installdir=/srv/xcat-install who reads the page in order therefore relabels before any mapping covers that tree, and rootimg/etc/shadow resolves to var_t. The exclusion added afterwards keeps the var_t it finds, because it only stops the next relabel from changing the label again. The order also cost the artifacts. file_contexts keeps the expressions in the order they are read and the last one that matches a path wins, so the exclusions of the second block beat the artifact mappings of the first. Where the image root carries a rootimg component in the middle, the exclusion matches the artifacts as well, and the five expressions with a wildcard, the initrds and the packed images, resolve <<none>>. kernel and hypervisor carry no wildcard and win either way, which is why the defect showed on a subset. The page is now one sequence: the publication directory, both guest exclusions, the artifact mappings, then one restorecon. It says what each step orders and why. xCAT-test/native/selinux_image_repair.t passes 381 of 381 checks on this sequence and fails 47 on the order of the parent commit. selinux_docs.t fails 3 of 30 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!