Vinícius Ferrão
bf5e2bdb20
The packet test runs dhcpd and kea-dhcp4 in a network namespace with the rules that BootPolicy renders, and sends relayed DHCPDISCOVER packets from a second namespace. It checks the boot file of firmware PXE, xNBA and iPXE clients, with each iPXE feature present or missing, for an xnba node and an ipxe node that install, for both methods with a SAN disk, and for an unknown node. On ISC it also covers an iSCSI node of each method in the boot state, and repeats the node rows after a restart, when dhcpd reads the host statements back from dhcpd.leases. On Kea it repeats the rows of the ipxe nodes with a configuration that makedhcp upgraded, which keeps the xNBA global classes of the older makedhcp -n. It also checks that the UEFI clients of an xnba node get xNBA when the server lacks the xNBA UEFI file. The Kea validation test checks the x86 classes of xnba and ipxe nodes with kea-dhcp4 -t. XCAT::Test::DHCP builds the packets, and the integration case expects seven files.
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!