This is Kaktus Kowabunga agent, for HCI nodes. Kaktus stands for Kowabunga Amazing KVM and TUrnkey Storage (!!), basically, our Hyper-Converged Infrastructure (HCI) node.
While large virtualization systems such as VMware usually requires you to dedicate servers as computing hypervisors (with plenty of CPU and memory) and associate them with remote, extensive NAS or vSAN, providing storage, Kowabunga follows the opposite approach. Modern hardware is powerful enough to handle both computing and storage.
This approach allows you to:
- use commodity hardware, if needed
- use heterogenous hardware, each member of the pool featuring more or less computing and storage resources.
| Project | Release Badge |
|---|---|
| Kaktus |  |
Kaktus development relies on pre-commit hooks to ensure proper commits.
Follow installation instructions here.
Local per-repository installation can be done through:
$ pre-commit install --install-hooksAnd system-wide global installation, through:
$ git config --global init.templateDir ~/.git-template
$ pre-commit init-templatedir ~/.git-templateKaktus development relies on Semantic Versioning and unscoped Conventional Commits for development.
Changelog is automatically triggered from commits summary from the following commits types: feat, fix, perf, chore, docs, e.g.
feat!: upgrade API version <- will increase version major number at release
feat: add new super nice feature <- will increase version minor number at release
fix: correct bug XYZ <- will increase version patch number at release
Versioning generally follows Semantic Versioning.
Kaktus is maintained by Kowabunga maintainers.
Licensed under Apache License, Version 2.0, see LICENSE.