Stig Telfer b64f9adbc6 Preserve assigned MAC on subsequent invocations
Tenks/libvirt was not reusing the MAC address assigned when invoked
repeatedly, which was leading to errors and confusion when extending
an existing Tenks deployment.

Check Ansible facts for a pre-existing interface and reuse the
assigned MAC if one is found.  Any existing MAC is added to the
data structure returned by set_libvirt_interfaces.

Change-Id: If45516d06d41992e7142ca8071ddcb84160a13e5
2024-10-31 12:48:00 +00:00
2024-10-24 21:02:29 +09:00
2023-05-18 09:24:55 +01:00
2020-09-01 09:57:16 +02:00
2019-04-19 19:35:44 +00:00
2018-09-19 08:40:46 +00:00
2018-08-17 11:38:20 +01:00
2018-08-23 13:04:48 +00:00
2024-10-24 21:02:29 +09:00
2020-04-05 20:20:10 +02:00
2023-05-18 09:24:55 +01:00
2023-05-18 09:24:55 +01:00

Tenks

image

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).

Description
Virtual bare metal cluster management
Readme 2.4 MiB
Languages
Python 96.1%
Shell 2.4%
Jinja 1.5%