Vinícius Ferrão
0d8d1e60ff
Extract the secret set, the command maps and the redaction routines from xcatd.pm. Drive the real routines, because the module needs daemon dependencies that the test host does not have. Cover a multi-word value, a quoted value, spaces around the operator, the "+=", ",=", "^=", "!=", "=~" and "!~" operators, the community strings, a secret embedded in a compound argument with and without quotes, each Getopt::Long password option form with bundles, the "?" help letter, abbreviations, "+" prefixes and two-dash letters, values that hold another secret letter, non-secret compact values that a value option absorbs, long names that start with a secret letter, the mkvm case forms and compact values, the chvm positional passwords, the mkvm clone pw= operand, the vCenter cluster passwords, the snmpc site value through chdef and tabch with compound selectors, the authentication tokens, and the product keys. Assert that validate() redacts the argument vector, that the joined result runs through redact_password, and that the dispatch trace builds its text from redacted arguments. Keep every attribute and column pair from Schema.pm, so a removed table-qualified mapping fails the test.
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!