fe3021fc37
So... We can't do this in a single patch, and we *actually* need to merge the vxlan fix before the subnode will ever pickup the configuration From the logs, I can observe the vxlan tunnel connects between the nodes. Awesome. Where things break is in the local setup of the local bridges used to wire everything together. setup_vxlan_network:3274 : sudo ovs-vsctl add-port sub1brbm phy-brbm-infra ovs-vsctl: Error detected while setting up 'phy-brbm-infra': could not open network device phy-brbm-infra (No such device). See ovs-vswitchd log for details. Basically, with the same change on a separate patch, we're able to observe the controller node work perfectly. It is the subnode connectivity which is just broken. So, activate the bridge interfaces seems ideal. This likely broke at some point due to behavior changes in OpenVSwitch. Change-Id: I11dbba1957d67187d859a1ef60563c0301da9812 |
||
|---|---|---|
| .. | ||
| files | ||
| lib | ||
| tools/ironic | ||
| upgrade | ||
| common_settings | ||
| plugin.sh | ||
| settings | ||