This video starts with saying web searches don't yield practical answers and then goes on to instantly fail on the very same thing. In most practical applications, you would not wire and LAG two host NICs into a single switch because that would not eliminate a single point of failure - the switch.
We had a great question asked to us on Twitter: "Mind elaborating on why bond0 was labeled "restricted to VLANs 1400-1599" throughout?" bond0 doesn't care about a limit, openstack enforces that limitation as specified in the ml2_conf.ini. See timestamp 9:30.
Very detailed explanation; need help in understanding the switch side and server side configuration of the bond0, all the 3 interfaces(bond0, bond0.1600 & bond0.1200) are set to manual, i have a connected both the nics of my compute node to a L2 Switch(Netgear GS324T) and configured a STATIC LAG, link is up but none of the interfaces receive an IP address as they are set to manual.... do i need to set the bond0 interface to static and assign an ip from the external network(router). Please suggest. I am setting up Openstack Victoria on a All-In-One Server manual configuration (not devstack or packstack).....
Great stuff and thanks a lot! Very helpful - all videos. My comments especially on the bonding-stuff (~ 1:30 and later on this video): Because of some network problems after implementing the bonding stuff in the /etc/network/interfaces, I had to modify two other config files on my Linux machines (Ubuntu 16.04.3 LTS and Openstack Newton): 1) /lib/systemd/system/networking.service line: ExecStart=/sbin/ifup -a --read-environment change to: ExecStart=/sbin/ifup -a --allow=bond --read-environment Otherwise my machines got problems during bringing up/raise the network IF's 2) /etc/network/interfaces I had to figure out the correct mtu size (Jumbo frames). Therefore I added the line 'mtu 9000' for the corresponding interfaces. You have to figure out for your environment, whats the correct size (e. g. take a look on your switches and routers). Just as an idea, perhaps someone will have similar problems...
I'm using Ubuntu 18.04 LTS, but for network, I switched back to /etc/network/interfaces as below. # sudo apt install ifupdown source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # HW NICs auto ens160 iface ens160 inet manual bond-master bond0 # Bonding auto bond0 iface bond0 inet manual bond-mode 802.3ad bond-miimon 200 bond-slaves none up ip link set dev $IFACE up down ip link set dev $IFACE down # This Overlay/Mgmt network auto bond0.178 iface bond0.178 inet static address 10.0.0.253 netmask 255.255.255.0 # For internet connectivity auto bond0.168 iface bond0.168 inet static address 161.5.168.253 netmask 255.255.255.0 gateway 161.5.168.254 When I do for the first two bridges it went but not for bond0. "ovs-ovctl add-port br-vlan bond0"
