Daniel Hilst
46fd59f26d
confignetwork_secondarynic_nicextraparams_updatenode fails on openEuler 20.03sp4, 22.03sp4 and 24.03sp4 and on el8, while its sibling confignetwork_secondarynic_updatenode passes everywhere. The only failing check is CONNECTED_MODE=yes, twice. The run log shows configeth receives the value -- "array_nic_params 0=CONNECTED_MODE=yes" -- and the profile NetworkManager reports, /etc/sysconfig/network-scripts/ifcfg-xcat-ens4-1, does not contain it afterwards. configeth writes nicextraparams in configipv4 and then activates the connection. The comment on the late persistence block states why that write does not survive: the nmcli con reload/up in the restart phase re-serializes the connection from NetworkManager's in-memory model and drops anything NetworkManager does not model. The block repairs it after activation, but its gate requires xcat_uses_nm_keyfile, so it runs for a keyfile store only. el8 never reaches that test, and openEuler reaches it and fails it because NetworkManager there reports an ifcfg file. Those are the two families on the ifcfg path and the two that fail. The block now runs for both stores. xcat_nm_conn_file asks NetworkManager which file holds the connection rather than composing the name, because NetworkManager suffixes it when a file of the plain name exists. xcat_persist_nic_extra_param writes the key as the profile spells it -- under [user] with an xcat. prefix in a keyfile, plain in an ifcfg file -- and appends only when the key is absent. xcatlib_nic_extra_param_persist.bats covers both stores with nmcli stubbed. Two behavioural mutants were run against it: restoring the keyfile-only behaviour fails the three ifcfg assertions and leaves the keyfile ones passing, and composing the filename fails only the resolution assertion. 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!