 | 1 | initial version |
Hello mario,
You could do the same on Hyper-V as you do on Linux. You have to add in neutronovsagent.conf the bridge_mappings under [ovs] group. Example:
[ovs]
bridge_mappings = public2:br-eth2
, where public2 is the name of the flat network from neutron and br-eth2 is the name of the bridge on the Hyper-V host. The only problem is that you have to use New-NetSwitchTeam to create a switch with the adapters that you'll use for OVS. Example:
New-NetSwitchTeam -Name team -TeamMembers "Ethernet1","Ethernet2"
New-VMSwitch -Name external -NetAdapterName team
After you created the switch in the way described above, you can issue the following (i.e.):
ovs-vsctl add-br br-port1
ovs-vsctl add-br br2
ovs-vsctl add-port br-port1 Ethernet1
ovs-vsctl add-port br2 Ethernet2
An example for bridge mapping for the above configuration is:
[ovs]
bridge_mappings = public2:br2
The bridge br-port1 is used for overlay network (tunneling ip) and br2 is used for flat network.
Thanks, Alin
© 2014-2023 Cloudbase Solutions Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.