parallelvirtualcluster/pvc
1
0
Fork 0
Code Issues 11 Pull Requests Projects Releases 114 Wiki Activity

Implement bridge_device for bridged VNIs

Browse Source 
Required due to #64. Bridged networks were being created on top of a
vLAN if the Cluster network was a vLAN device, rather than being created
on the underlying device. This came from a previous revision of the
cluster architecture guidelines where Cluster was supposed to be a raw
device rather than a vLAN. This fixed the problem by implementing a
configuration field for a "bridge_device", a NIC device that can then
have the bridged vLANs created on top of it.

Fixes #64
This commit is contained in:
Joshua Boniface
2020-01-06 14:44:56 -05:00
parent 17b6af3ee6
commit 7b3e267f7a
3 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
node-daemon/pvcd.sample.yaml
View File

@ -153,6 +153,8 @@ pvc:
# networking: PVC networking configuration
# OPTIONAL if enable_networking: False
networking:
# bridge_device: Underlying device to use for bridged vLAN networks; usually the device underlying <cluster>
bridge_device: ens4
# upstream: Upstream physical interface device
upstream:
# device: Upstream interface device name