Virtual bare metal cluster management
6a2fb44a78
If the ironic_config field is not present in a node definition, then that node should not be registered with ironic. In this case we also don't need to query glance for images or wait for resources to appear in placement. If nova_flavors is empty, we do not need to register flavors, so no need to install the client or check for OS_USERNAME. Also fixes an issue in the action plugin where it would fail if ironic_config field is not present in a node definition. Finally, in CI deploy/teardown tests, rather than skipping tasks, we now remove the ironic_config field from the node definition, and set nova_flavors to empty, such that we exercise these code paths. Change-Id: I29b42665f1609c99e80f12ab6f3815d0e0918dae Story: 2004412 Task: 28056 |
||
---|---|---|
ansible | ||
doc | ||
playbooks/tenks-deploy-teardown | ||
releasenotes | ||
roles | ||
tests | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
LICENSE | ||
README.rst | ||
requirements.txt | ||
requirements.yml | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
Tenks
Tenks is a utility that manages virtual bare metal clusters for development and testing purposes. It offers:
- Declarative definition of clusters using Ansible's familiar YAML syntax
- Automated creation and deletion of virtualised bare metal nodes across any number of hypervisors
- In-built management of Open vSwitch bridges for physical networks
- Registration of nodes and ports with OpenStack Ironic, and creation of OpenStack Nova flavors
- Simple cluster reconfiguration and tear-down
To get started with Tenks, see the documentation (linked below).
- Free software: Apache license
- Documentation: https://tenks.readthedocs.io/
- Source: https://github.com/stackhpc/tenks/
- Bugs: https://github.com/stackhpc/tenks/issues
- Known issues/limitations: refer to the documentation.