Daniel Hilst
cfa3073da7
xCAT-test/unit/fips_policy_sources.t ran build-utils/sync-fips-policy as a subprocess, so a file in the unit directory measured a program rather than a routine, and it asserted on the diagnostics the script printed instead of on an answer. buildrpms.pl and builddebs.pl started the same script with system() to check the generated libraries before packaging xCAT or xCAT-genesis-scripts. XCAT::BuildUtils gains fips_policy_artifacts, fips_policy_plan and sync_fips_policy. fips_policy_plan reads the canonical policy and both runtime libraries and reports what generation would write, without writing. sync_fips_policy applies that plan in write mode and returns the stale paths, the paths it rewrote and the diagnostics for its caller to print. The two builders now call sync_fips_policy in their own process and print the diagnostics before they stop, which keeps the output xCAT-test/native/ fips_build_guard.t asserts on. build-utils/sync-fips-policy keeps its --check and --write contract and its exit status, and is now a thin caller. The unit test calls the sub in-process and asserts on the returned hash. It also covers a library holding two policy blocks and a library replaced by a symbolic link, which the subprocess form did not reach. Ten mutants of the module, one per guard, each fail the assertion that names that guard. xCAT-test/bats/fips_policy_artifacts.bats copies XCAT::BuildUtils into its fixture, because the script it runs now loads the module. 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!