Two conflicts, both from xcat-core/#7978 landing on master. build-utils/lib/XCAT/BuildUtils.pm: both branches added a package_skip_reason, #7978 with a general @PACKAGE_SKIPS table and this branch with its own %EL_ONLY_PACKAGES and a second sub. git merges them as separate hunks because they sit apart in the file, and Perl takes the LAST definition, so keeping both silently deletes whichever rule came first. There is now one table and one sub. A rule names either the target prefixes that do NOT build the package, or, with `only`, the pattern of the targets that DO. The second form is what an EL-only package needs: naming the families that are not EL means a family added later tries to build it, which is how openSUSE reached xCAT-selinux and failed xcat-core-build-opensuse #42 on a missing selinux-policy-devel. buildrpms.pl: an empty build plan takes upstream's answer, a clean return rather than this branch's die. That is the decision #7978 exists for -- the dep pipeline asks for xCAT-genesis-base alone and no openSUSE target builds it -- so reinstating the die would fail a build that has nothing to do. selinux_el_only_scope.t is 37 of 37 and opensuse_no_legacy_genesis.t 22 of 22 on the merged tree, and the whole unit suite passes: 301 files, 9801 tests. 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!