8df4a68fb1
If Ansible hostvars contain a pipe (|) character, this can cause problems during scheduling as Ansible fails during Jinja templating. This is probably a bug in Ansible/Jinja. The particular case where this was hit was when using screen, the TERMCAP environment variable gets set to something beginning with 'SC|screen|VT'. This change addresses the issue by moving the capture of hostvars inside the tenks_update_state action plugin rather than evaluating them in a playbook. Change-Id: Ibef91d9ef499c8741b61a170672a23f530a600bb
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.