Both Genesis images built a DUID-UUID from the nil SMBIOS UUID. makedhcp refuses that UUID, because nodeimport writes it to every PowerKVM node, and reserves the hardware address instead, so the client sent an identifier no reservation held and the node took a pool address with no boot file. genesis-duid and doxcat now keep the DUID-LL for it, which is what Kea reads the hardware address out of. getzonesfornet died on an IPv6 prefix that is not a multiple of 4, which took makedns and makedhcp with it for a /62 or a /126 network. A reverse zone is delegated on a nibble, so the prefix is rounded down and the enclosing zone is returned. Both copies of the routine are fixed. The test suite needs socat and jq, and five bats files skipped without them, so the workflow installs both. Template.pm drops the unused _is_el10, credentials.pm drops a repeated import, and two comments that recorded bug history are cut to the fact the code cannot show. Reverting any one fix fails named assertions: 1 of 8 and 1 of 3 bats cases for the two Genesis images, and 4 of 30 in ddns_ipv6.t, which traps the abort so the file still reports. Signed-off-by: Daniel Hilst <392820+dhilst@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!