Add bridge_device entry to config
Used to properly allow bridged networks to be formed. Ref parallelvirtualcluster/pvc#64
This commit is contained in:
parent
51ad136814
commit
cd7cdf2719
|
@ -80,6 +80,14 @@ pvc_nodes:
|
|||
ipmi_user: "{{ username_ipmi_host }}"
|
||||
ipmi_password: "{{ passwd_ipmi_host }}"
|
||||
|
||||
# Bridge device entry
|
||||
# This device is passed to PVC and is used when creating bridged networks. Normal managed networks are
|
||||
# created on top of the "cluster" interface defined below, however bridged networks must be created
|
||||
# directly on an underlying non-vLAN network device. This can be the same underlying device as the
|
||||
# upstream/cluster/storage networks (especially if the upstream network device is not a vLAN itself),
|
||||
# or a different device separate from the other 3 main networks.
|
||||
pvc_bridge_device: bondU # Replace based on your network configuration
|
||||
|
||||
# Configuration file networks
|
||||
# > Taken from base.yml's configuration; do not modify this section.
|
||||
pvc_upstream_device: "{{ networks['upstream']['device'] }}"
|
||||
|
|
|
@ -77,6 +77,7 @@ pvc:
|
|||
log_keepalive_storage_details: {{ pvc_log_keepalive_storage_details }}
|
||||
console_log_lines: {{ pvc_log_console_lines }}
|
||||
networking:
|
||||
bridge_device: {{ pvc_bridge_device }}
|
||||
upstream:
|
||||
device: {{ pvc_upstream_device }}
|
||||
mtu: {{ pvc_upstream_mtu }}
|
||||
|
|
Loading…
Reference in New Issue