Vinícius Ferrão
7836a2577a
A confluent attribute update keeps every attribute that the request does not name. The export only named the attributes that the switch table holds, so a switch row that is deleted stayed in confluent, and an interface that is renamed left the attributes of the old name beside the attributes of the new one. Confluent then holds two ports for one node, which defeats the discovery that this export exists for. Name the topology attributes that the switch table no longer holds, with no value, so that confluent removes them. Confluent removes the attributes that the request names with no value before it sets the rest of the request, and it accepts a wildcard for the attributes of every interface. The wildcard does not match the attributes that carry no interface, so those are named on their own. A node that confluent does not hold yet has nothing to remove, so the request that creates a node is unchanged. A confluent that accepts a wildcard in the name of an attribute arrived in 3.4.0. An older confluent reads the name as the name of one attribute, finds no attribute of that name and reports nothing. The topology of an interface that is gone then stays, as it does today.
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!