Vinícius Ferrão
539486b7c8
An osimage pkgdir can name mirrors after the install media, and ospkgs installs from all of them, but the autoinstall apt configuration offered the installer only the archive mirror and the otherpkgs repositories. A package that only a pkgdir mirror carries could not be installed before the first boot. The mirrors now join the installer's apt sources, next to the otherpkgs ones, in every form the configuration takes. An entry written as URL, suite and components is an apt source line, as ospkgs writes it, and a suite that is an exact path needs no component. A local directory that is a flat repository is served by the management node and trusted, as an otherpkgdir is. An entry that names an Ubuntu archive mirror the installer already has a source for, the configured one or a default one, carries that source's signing key, the archive keyring on the Deb822 releases and none before them, because apt rejects a second source for the same suite whose signing key differs. For the same reason a repository is offered once, whether pkgdir names it twice, as a directory and as its URL, or the otherpkgdir names it too. Anything else is no apt source for ospkgs either and is left out. Signed-off-by: Vinícius Ferrão <2031761+viniciusferrao@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!