Add bridge_mtu config to docs
This commit is contained in:
parent
95e01f38d5
commit
4ed537ee3b
|
@ -450,6 +450,7 @@ pvc_nodes:
|
||||||
ipmi_password: "{{ passwd_ipmi_host }}"
|
ipmi_password: "{{ passwd_ipmi_host }}"
|
||||||
|
|
||||||
pvc_bridge_device: bondU
|
pvc_bridge_device: bondU
|
||||||
|
pvc_bridge_mtu: 1500
|
||||||
|
|
||||||
pvc_sriov_enable: True
|
pvc_sriov_enable: True
|
||||||
pvc_sriov_device:
|
pvc_sriov_device:
|
||||||
|
@ -907,6 +908,12 @@ The IPMI password for the node management controller. Unless a per-host override
|
||||||
|
|
||||||
The device name of the underlying network interface to be used for "bridged"-type client networks. For each "bridged"-type network, an IEEE 802.3q vLAN and bridge will be created on top of this device to pass these networks. In most cases, using the reflexive `networks['cluster']['raw_device']` or `networks['upstream']['raw_device']` from the Base role is sufficient.
|
The device name of the underlying network interface to be used for "bridged"-type client networks. For each "bridged"-type network, an IEEE 802.3q vLAN and bridge will be created on top of this device to pass these networks. In most cases, using the reflexive `networks['cluster']['raw_device']` or `networks['upstream']['raw_device']` from the Base role is sufficient.
|
||||||
|
|
||||||
|
#### `pvc_bridge_mtu`
|
||||||
|
|
||||||
|
* *required*
|
||||||
|
|
||||||
|
The MTU of the underlying network interface to be used for "bridged"-type client networks. This is the maximum MTU such networks can use.
|
||||||
|
|
||||||
#### `pvc_sriov_enable`
|
#### `pvc_sriov_enable`
|
||||||
|
|
||||||
* *optional*
|
* *optional*
|
||||||
|
|
|
@ -146,6 +146,7 @@ pvc:
|
||||||
console_log_lines: 1000
|
console_log_lines: 1000
|
||||||
networking:
|
networking:
|
||||||
bridge_device: ens4
|
bridge_device: ens4
|
||||||
|
bridge_mtu: 1500
|
||||||
sriov_enable: True
|
sriov_enable: True
|
||||||
sriov_device:
|
sriov_device:
|
||||||
- phy: ens1f0
|
- phy: ens1f0
|
||||||
|
@ -427,6 +428,13 @@ How many lines of VM console logs to keep in the Zookeeper database for each VM.
|
||||||
|
|
||||||
The network interface device used to create Bridged client network vLANs on. For most clusters, should match the underlying device of the various static networks (e.g. `ens4` or `bond0`), though may also use a separate network interface.
|
The network interface device used to create Bridged client network vLANs on. For most clusters, should match the underlying device of the various static networks (e.g. `ens4` or `bond0`), though may also use a separate network interface.
|
||||||
|
|
||||||
|
#### `system` → `configuration` → `networking` → `bridge_mtu`
|
||||||
|
|
||||||
|
* *optional*
|
||||||
|
* *requires* `functions` → `enable_networking`
|
||||||
|
|
||||||
|
The network interface MTU for the Bridged client network device. This is the maximum MTU a bridged client network can use.
|
||||||
|
|
||||||
#### `system` → `configuration` → `networking` → `sriov_enable`
|
#### `system` → `configuration` → `networking` → `sriov_enable`
|
||||||
|
|
||||||
* *optional*, defaults to `False`
|
* *optional*, defaults to `False`
|
||||||
|
|
Loading…
Reference in New Issue