Vinícius Ferrão
16c88d8966
makeconfluentcfg gives confluent the console settings, the credentials of the hardware manager, the location and the enclosure of each node. It does not give the switch and the port that the node is cabled to, which confluent uses to find a node by the port it answers on. Read the switch table and give confluent net.switch and net.switchport. A node has one row in that table for each of its interfaces, thus keep every row and not the first one. A row that names an interface gives net.<interface>.switch and net.<interface>.switchport, so a node with more than one interface keeps the port of each. A row that names no interface gives the names without an interface. Read the table with the node list when the command receives a node range and read the whole table when it does not, as the command already does for the other tables. A cluster whose switch table is empty receives the configuration that it receives today. Recovered from the lenovobuild branch, where this arrived as one commit and two repairs of it: the first keeps one row for each node, which loses every interface but one, and reads the switch columns from the nodepos table in the branch that takes no node range, where that table has no such columns and the feature does nothing.
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!