Virtual bare metal cluster management
eb34860069
We name veth pairs using up to the first 6 characters from the nodes names. If the node name prefixes are longer than this then the node index will not be included, and the interface names will not be unique. e.g. prefix compute, 2 nodes: compute0 & compute1 Link names are all p-comput-0-tap Note that the 0 here is the index of the physnet, node the node. This patch includes any trailing digits to keep link names unique, e.g. p-compu0-0-tap. Change-Id: I35c3da1d00030d8a270ac1a09e88e22098594f20 Story: 2007431 Task: 39058 |
||
---|---|---|
ansible | ||
doc | ||
playbooks | ||
releasenotes | ||
roles | ||
tenks | ||
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).
- License: Apache License, Version 2.0
- Documentation: https://docs.openstack.org/tenks/
- Source: https://opendev.org/openstack/tenks/
- Bugs: https://storyboard.openstack.org/#!/project/openstack/tenks
- Known issues/limitations: refer to the documentation.