Vinícius Ferrão
ac50225541
A Subiquity autoinstall installs what its user-data packages list names, and the templates could only name a fixed set, so the osimage pkglist reached an Ubuntu node through ospkgs after the first boot. The preseed token has no autoinstall form: the package list is YAML, one item per line. A list line that carries #INCLUDE_DEFAULT_PKGLIST_AUTOINSTALL# is now replaced by one item per pkglist package at the same indentation, with includes followed and without repeating the items the template lists above it. The line is replaced in the include pass of subvars, so a site template that includes the stock one is served too. A plain name and a task are installed this way, and a comment after them ends the record. A version pin or a target release stays with ospkgs, because the installer runs apt-get without --allow-downgrades and a pin can require one, and so does a name with an architecture qualifier, because a foreign architecture is enabled by a postscript that runs later. A record that begins with a removal or a group is left out whole, as ospkgs removes or installs it whole, and so are a removal written with a trailing hyphen, markers and preseed directives. A list that carries a #ENV: setting or an unreadable include is left to ospkgs whole. So is the list of an osimage with environvar, which mkinstall now hands over, and such an image's pkgdir mirrors stay out of the installer's sources as well: those variables reach apt-get only through ospkgs, and a mirror may need them. An osimage without a pkglist loses only the token line. The installer's apt configuration turns recommended packages off, as ospkgs installs the list without them; curtin writes that setting into the target, where the template removes it with the installer's sources. 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!