Daniel Hilst
f0944d3c7f
Ubuntu 18.04 and later render the network with netplan. ifupdown is not installed and /etc/network/interfaces.d/* is ignored entirely, so configeth's Debian branch -- which writes exactly there -- configures nothing at all on a modern Ubuntu node. It must write /etc/netplan/*.yaml and apply it instead. Issue #7454. Three properties a netplan writer has to hold, all of which an in-place YAML editor gets wrong. A VLAN interface (<parent>.<vid>) belongs under vlans: with id and link, or netplan never recreates it after a reboot. Multiple addresses on one NIC must keep the order they were added. And routes must be idempotent on the whole (to, via) pair, not on either field alone, or a second route sharing a gateway is swallowed. nicextraparams must survive as well: the ifupdown branch writes them into the interface stanza, so a netplan branch that drops them silently discards configuration the user asked for. Drive the real writers -- extracted from configeth and run against a temp NETPLAN_DIR -- and hand the result to `netplan generate` where netplan is installed. 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!