nodeimport writes '00000000-0000-0000-0000-000000000000' to vpd.uuid for every PowerKVM node it creates (profilednodes.pm). That value is 32 valid hexadecimal digits, so kea_duid_from_uuid builds a DUID from it and returns 00:04:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 for all of them. makedhcp then keeps the reservation of the node it wrote last and reports nothing. kea_duid_from_uuid now refuses the nil UUID, which it reads through the new dhcp6_uuid_is_placeholder. A node whose vpd.uuid is the nil UUID is treated like a node with no vpd.uuid: with Kea DHCP the reservation falls back to the MAC address of the node, and with ISC DHCP addnode6 skips the node and names the reason. addnode6 carries a third message for the nil UUID, because the existing 'vpd.uuid is not a UUID.' is false for a value of the right form. The all-f UUID is left alone. Nothing in the tree writes it, and RFC 4122 names only the nil UUID. dhcp_dhcpv6_duid.t adds node cn09 and a block for two PowerKVM nodes. Dropping the one new line from kea_duid_from_uuid fails 15 assertions, among them 'two nodes with the nil vpd.uuid keep one reservation each', while the three neighbours that hold the limits of the check stay green. 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!