Vinícius Ferrão
6dbc16c216
The original Lenovo SR635/SR655 (IPMI manufacturer 19046, product 1287) use an AMI "TSM" BMC reached over a LAN-over-USB interface, which needs OEM raw commands to bring the interface up, select the LAN channel, and restart TSM networking once configured. Add a dedicated vendor branch for it -- gated on the same IPMIMFG/XPROD check the script already uses for IBM, Dell, Supermicro, OpenPOWER and other Lenovo machines -- plus a udev rule and helper that bring up the USB NIC (169.254.0.120) so in-band ipmitool can reach the TSM. The user-slot auto-scan is skipped for these machines, which use a fixed slot. Everything is behind IPMIMFG=19046 && XPROD=1287 (or the 046b:ffb0 USB device), so no other BMC is affected. Recovered from the unmerged lenovobuild branch (922dfe18,42357f9d,02da8a6b,765e2ad3,408cf2b3), adapted to master's bmcsetup structure. The global MD5 LAN auth removal that rode along in42357f9dis intentionally left out -- SR635/SR655 IPMI authentication is already handled in master by #7586 (retry cipher suite 3 on a zero RAKP2 HMAC), so dropping MD5 for all BMCs is neither needed nor wanted here. Not lab-validated: this targets the original SR635/SR655 (product 1287); no such machine was available to test (an SR635 V3 reports product 1601 and uses a different, directly-reachable BMC). The code is gated so it cannot affect other hardware. Co-authored-by: Jarrod Johnson <10814490+jjohnson42@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!