Vinícius Ferrão
097554ba34
The findme handler of the blade plugin makes an inventory request for each node in the mp table. That table holds more than the blades of a chassis. lsslp writes a row for a Power BMC, for an FSP, for a BPA, for an HMC and for other hardware, and xCAT::PPCdb::add_systemX writes a row for a management module. None of that hardware answers a blade inventory. Keep a row that gives blade as its hardware type. Keep also a row that gives no hardware type but names a different node as its mpa, when that other node is a management module. The mp template in xCAT/templates/e1350 leaves the hardware type of a blade empty, so a test of the hardware type alone loses the blades of a chassis. Return when the table holds no blades. The work below the filter reads the arp table of the management node, and a site that has no chassis must not pay for that on each discovery request. Recovered from the lenovobuild branch, which tested the hardware type only.
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!