Virtual bare metal cluster management
c5c18ce04f
Adds support for setting node and volume name prefixes on a per-spec basis. This allows for different node specifications to use different names, e.g. 'controller' vs 'compute'. This change also fixes an issue where node names were not globally unique, only unique on a given hypervisor. This could cause issues if used with multiple hypervisors. This has been done by rewriting the scheduling logic, replacing the 'node index' concept with a more concrete reservation of IPMI ports (which are allocated per hypervisor), and decoupling this from generation of node names (which are allocated globally). Change-Id: I929b18918c2886f42c4d05b37c81f3e63c69a92f Story: 2004894 Task: 29201 Story: 31d2681 Task: 29248 |
||
---|---|---|
ansible | ||
doc | ||
playbooks/tenks-deploy-teardown | ||
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://git.openstack.org/cgit/openstack/tenks/
- Bugs: https://storyboard.openstack.org/#!/project/openstack/tenks
- Known issues/limitations: refer to the documentation.