Here is another similar suggestion, but this one creates a bond for a bridge using OVS balance-slb, which will use only one link in the bond for any particular VLAN at any given moment. It requires no special configuration on the switch, although I don't think it's been tested with Q-in-Q, so results might vary:
In theory, you could also place all 4 NICs in the same bond, and use DHCP as long as the primary NIC is the one that has the MAC address registered for the node.
Here is another similar suggestion, but this one creates a bond for a bridge using OVS balance-slb, which will use only one link in the bond for any particular VLAN at any given moment. It requires no special configuration on the switch, although I don't think it's been tested with Q-in-Q, so results might vary:
Controller:
- type: interface
- ip_netmask:
- ip_netmask: 169.254.169.254/32
- type: ovs_bridge
- type: ovs_bond
- type: interface
- type: interface
- type: interface
- type: vlan
- ip_netmask:
- default: true
Compute:
- type: interface
- ip_netmask:
- ip_netmask: 169.254.169.254/32
- default: true
- type: ovs_bridge
- type: ovs_bond
- type: interface
- type: interface
- type: interface
Then specify the proper bonding mode in network- environment. yaml:
parameter_defaults: kVLANRanges: "datacentre: <start> :<end>" Mappings: "datacentre:br-ex" OvsOptions: "bond_mode= balance- slb"
NeutronNetwor
NeutronBridge
BondInterface
In theory, you could also place all 4 NICs in the same bond, and use DHCP as long as the primary NIC is the one that has the MAC address registered for the node.