Every CentOS Linux 8 medium gives the same description, "CentOS Linux 8". The description gives no minor version. The .treeinfo file on the medium gives no minor version. Thus copycds gave the name centos8 to all of these media. Two CentOS Linux 8 media then wrote into the same /install/centos8 directory and made osimage definitions with the same names. The discinfo identifier table gives the minor version, but it contains only 8.1 and 8.5. The identifiers of an expanded tree are also different from the identifiers of the DVD. The release package in BaseOS/Packages is the only other record of the minor version on the medium. Read the version from the name of that package. CentOS changed the name of the package to centos-linux-release in 8.3, thus accept the two names. Accept only a major.minor version, because other packages start with the same centos-release prefix. Accept only the major version that the description gives, because a package for a different major version does not describe this medium. Accept the minor version only when the medium names one, because a medium that names more than one does not pin a minor version. Keep the version from the description in the other conditions. A medium that names no minor version keeps the name centos8, which is the behaviour before this change and the correct name for media that do not pin a minor version. CentOS Stream, Rocky Linux, AlmaLinux and Red Hat Enterprise Linux keep their own branches. CentOS Linux 7 gives a different description and has no BaseOS directory, thus it does not use this path. Recovered from the lenovobuild branch. Reimplemented against master: the original reads only centos-release, which CentOS renamed in 8.3, and its expression is not anchored.
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!