34ebd92cad
The fact that the Libvirt provider is using VMs is an implementation detail, so we should word Tenks such that it deploys clusters of nodes.
39 lines
1.3 KiB
Plaintext
39 lines
1.3 KiB
Plaintext
---
|
|
# Map physical network names to their source device. This can be either an
|
|
# existing interface or an existing bridge.
|
|
physnet_mappings: {}
|
|
|
|
system_requirements:
|
|
- python-virtualenv
|
|
|
|
# Path to virtualenv used to install Python requirements. If a virtualenv does
|
|
# not exist at this location, one will be created.
|
|
virtualenv_path: "{{ '/'.join([ansible_env['HOME'], 'tenks-venv']) }}"
|
|
|
|
# The URL of the upper constraints file to pass to pip when installing Python
|
|
# packages.
|
|
python_upper_constraints_url: >-
|
|
https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt
|
|
|
|
# Naming scheme for bridges created by tenks for physical networks is
|
|
# {{ bridge_prefix + i }}, where `i` is the index of the physical network in
|
|
# physnet_mappings (sorted alphabetically by key).
|
|
bridge_prefix: brtenks
|
|
|
|
# Prefix for all veth links.
|
|
veth_prefix: 'p-'
|
|
|
|
# Suffix for veth links attached to a Tenks OVS bridge.
|
|
veth_bridge_ovs_suffix: '-ovs'
|
|
# Suffix for veth links attached to a source Linux bridge.
|
|
veth_bridge_source_suffix: '-phy'
|
|
|
|
# Suffix for veth links attached to a Tenks OVS bridge.
|
|
veth_node_ovs_suffix: '-ovs'
|
|
# Suffix for veth links attached to a node. Nodes aren't physical so '-phy'
|
|
# doesn't seem right.
|
|
veth_node_source_suffix: '-tap'
|
|
|
|
# Directory in which to store Tenks logs.
|
|
log_directory: /var/log/tenks/
|