Use Hyper-V with OpenStack and Open vSwitch

asked 2017-12-06 05:47:04 +0300

goldyfruit
31 ●3 ●3 ●3 https://blog.incloudus...

updated 2017-12-06 05:48:35 +0300

Hi,

We would like to use Hyper-V with OpenStack and Open vSwitch on our OpenStack Pike deployment using Cloudbase installer.

Our setup:

Windows 2012 R2
2 NICS
Teaming (bond0) with NIC1 and NIC2 using LACP
Multiple team VLAN interfaces on top of bond0 (bond0.70, bond0.73, etc...)
An IP address on each bond0.XX interfaces but not on the bond0 interface

All the VLAN are working, we are able to ping other nodes in the different networks.

We created the Hyper-V external virtual switch named vSwitch bind on our bond0 interface.

New-VMSwitch -Name vSwitch -NetAdapterName bond0 -AllowManagementOS $false

The "Cloudbase Open vSwitch Extension" has been enabled on "vSwitch" Hyper-V virtual switch.

Enable-VMSwitchExtension -VMSwitchName vSwitch -Name "Cloudbase Open vSwitch Extension"

Within Open vSwitch we have br-int and br-tun bridges, for br-tun we can see all the VxLAN tunnels created and for br-int we can see the instance ports with the tags perfectly created.

We are able to spawn instances on this Hyper-V compute but the instances don't have network connectivity, the network interface is there but there is no DHCP address on it.

What step are we missing ?

Thanks for your help !

edit retag flag offensive close merge delete

add a comment

answered 2017-12-06 19:40:57 +0300

goldyfruit
31 ●3 ●3 ●3 https://blog.incloudus...

updated 2017-12-07 00:40:15 +0300

Additional information:

PS C:\Users\Administrator> ovs-vsctl.exe show
bb1b487c-d35e-4789-8931-05389c4159d3
    Bridge br-int
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port br-int
            Interface br-int
                type: internal
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
    Bridge br-tun
        Controller "tcp:127.0.0.1:6633"
            is_connected: true
        fail_mode: secure
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port "vxlan-0aa04922"
            Interface "vxlan-0aa04922"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="10.160.73.70", out_key=flow, remote_ip="10.160.73.34"}
        Port "vxlan-0aa0491b"
            Interface "vxlan-0aa0491b"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="10.160.73.70", out_key=flow, remote_ip="10.160.73.27"}
        Port "vxlan-0aa04920"
            Interface "vxlan-0aa04920"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="10.160.73.70", out_key=flow, remote_ip="10.160.73.32"}
        Port "vxlan-0aa04902"
            Interface "vxlan-0aa04902"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="10.160.73.70", out_key=flow, remote_ip="10.160.73.2"}
        Port br-tun
            Interface br-tun
                type: internal
        Port "vxlan-0aa0491c"
            Interface "vxlan-0aa0491c"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="10.160.73.70", out_key=flow, remote_ip="10.160.73.28"}
        Port "vxlan-0aa04904"
            Interface "vxlan-0aa04904"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="10.160.73.70", out_key=flow, remote_ip="10.160.73.4"}
        Port "vxlan-0aa04918"
            Interface "vxlan-0aa04918"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="10.160.73.70", out_key=flow, remote_ip="10.160.73.24"}
        Port "vxlan-0aa04921"
            Interface "vxlan-0aa04921"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="10.160.73.70", out_key=flow, remote_ip="10.160.73.33"}
        Port "vxlan-0aa0491e"
            Interface "vxlan-0aa0491e"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="10.160.73.70", out_key=flow, remote_ip="10.160.73.30"}
        Port "vxlan-0aa04903"
            Interface "vxlan-0aa04903"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="10.160.73.70", out_key=flow, remote_ip="10.160.73.3"}
        Port "vxlan-0aa0491f"
            Interface "vxlan-0aa0491f"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="10.160.73.70", out_key=flow, remote_ip="10.160.73.31"}
        Port "vxlan-0aa0491a"
            Interface "vxlan-0aa0491a"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="10.160.73.70", out_key=flow, remote_ip="10.160.73.26"}
    Bridge br-data
        Port br-data
            Interface br-data
                type: internal
        Port "bond0"
            Interface "bond0"

PS C:\Users\Administrator> Get-NetLbfoTeam -Name bond0
Name                   : bond0
Members                : Nic1
TeamNics               : {bond0.72, bond0, bond0.53, bond0.73...}
TeamingMode            : Lacp
LoadBalancingAlgorithm : TransportPorts
Status                 : Up

PS C:\Users\Administrator> Get-NetAdapter
Name                      InterfaceDescription                    ifIndex Status       MacAddress             LinkSpeed
----                      --------------------                    ------- ------       ----------             ---------
bond0.53                  Microsoft Network Adapter Multiple...#3      32 Up           8C-DC-D4-B7-21-44        10 Gbps
Nic2                      Intel(R) 82599 10 Gigabit Dual Por...#2      13 Up         8C-DC-D4-B7-21-45          10 bps
Nic1                      Intel(R) 82599 10 Gigabit Dual Port ...      12 Up           8C-DC-D4-B7-21-44        10 Gbps
bond0.70                  Microsoft Network Adapter Multiple...#4      33 Up           8C-DC-D4-B7-21-44        10 Gbps
bond0.72                  Microsoft Network Adapter Multiple...#2      31 Up           8C-DC-D4-B7-21-44        10 Gbps
bond0.73                  Microsoft Network Adapter Multiple...#5      34 Up           8C-DC-D4-B7-21-44        10 Gbps
bond0                     Microsoft Network Adapter Multiplexo...      30 Up           8C-DC-D4-B7-21-44        10 Gbps

PS C:\Users\Administrator> Get-VMSwitch
Name    SwitchType NetAdapterInterfaceDescription
----    ---------- ------------------------------
vSwitch External   Microsoft Network Adapter Multiplexor Driver

Status of the Neutron OVS agent on Hyper-V compute:

# openstack ...

(more)

edit flag offensive delete link

Comments

I can see the instance traffic in br-int and then in br-tun bridges but it's like if the traffic is not forward to vSwitch.

goldyfruit ( 2017-12-06 22:27:39 +0300 )edit

Hey. Thanks for trying this type of setup :). I wouldn't recommend mixing the MSFT multiplexor with OVS because we don't test that scenario very often. I would recommend using OVS bonds together with LACP...

aserdean ( 2017-12-07 05:05:24 +0300 )edit

To setup the vSwitch you are missing this part: https://github.com/cloudbase/ovs/blob/branch-2.7-cloudbase/Documentation/intro/install/windows.rst#add-multiple-nics-to-be-managed-by-ovs And for setting up OVS bonds I recommend looking over:

aserdean ( 2017-12-07 05:07:29 +0300 )edit

<p>https://blog.scottlowe.org/2012/10/19/link-aggregation-and-lacp-with-open-vswitch/ . I'll try to post tomorrow a small snippet as an example.

aserdean ( 2017-12-07 05:09:10 +0300 )edit

Also please let me know which version of OVS you are running. Please ensure that you have the latest Windows updates if you are planning to use the MSFT multiplexor solution.

aserdean ( 2017-12-07 05:11:32 +0300 )edit

see more comments

Use Hyper-V with OpenStack and Open vSwitch

1 answer

Comments

Your Answer

Question Tools

Stats

Related questions

Use Hyper-V with OpenStack and Open vSwitch edit

1 answer

Comments

Your Answer

Question Tools

Stats

Related questions

Use Hyper-V with OpenStack and Open vSwitch