Vinícius Ferrão
1e5de1e476
A node that discovery finds over ethernet is known by its ethernet mac. When that node boots over IPoIB, the request carries the InfiniBand identity of the adapter and not the ethernet mac. dhcpd finds no host entry for that identity and answers nothing, thus the node does not boot and the log gives no reason. dhcp.pm already gives hardware type 32 to a node whose mac attribute holds an 8 or 9 byte fabric address, but that needs the fabric address before the node boots, and discovery records the ethernet mac. A Mellanox adapter makes its port GUID from the ethernet mac, by the insertion of 03:00 in the middle. Thus the InfiniBand identity of the node is already known. Write it as a second host entry with the -xcat-ib suffix and hardware type 32, so a request over either fabric finds the node and receives the same address. Remove that entry with the node. Write the second entry only for a node whose network an IPoIB interface serves. A cluster with no InfiniBand keeps the host entries that it has today. This is for the ISC backend. makedhcp returns into the Kea code before this routine when Kea is the backend, and a Kea server does not answer an IPoIB client, thus there is nothing there for a second entry to answer. Recovered from the lenovobuild branch. Reimplemented against master: the original writes the second entry for every ethernet node, which makes two host entries for each node of a cluster that has no InfiniBand.
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!