Standard Linux bridging. OVS doesn't use multicast for vxlan.
Simon Weller/615-312-6068
-Original Message-
From: Imran Ahmed [im...@eaxiom.net]
Received: Friday, 14 Apr 2017, 8:36PM
To: users@cloudstack.apache.org [users@cloudstack.apache.org]
Subject: RE: OVS Plugin
Hi Simon,
That’s ve
Hi Simon,
Thats very interesting. Do you use openvSwitch underneath on the
hypervisor or default Linux bridging ? Also what is your preference?
Thanks,
Imran
-Original Message-
From: Simon Weller [mailto:swel...@ena.com]
Sent: Saturday, April 15, 2017 1:35 AM
To: users@cloudstack.ap
We trunk a vlan down to the hosts, make it the KVM traffic label for the guest
network (we run VPCs in advanced mode) and allow ACS to build the VXLAN VNI
within the vlan.
The native VXLAN support in the linux kernel uses multicast, so you do need an
ip on the interface (we use a different netw
Hi Simon
Would you mind expanding a little more on your setup?
Specifically what is being used underneath.
thanks
ilya
On 4/14/17 9:11 AM, Simon Weller wrote:
> I'd strongly suggest you consider using the native VXLAN support for KVM. It
> works extremely well and we run it in production.
>
>
That's awesome. I will check this out.
-Original Message-
From: Simon Weller [mailto:swel...@ena.com]
Sent: Friday, April 14, 2017 10:54 PM
To: users@cloudstack.apache.org
Subject: Re: OVS Plugin
Just to be clear, your switches don't need to support VXLAN to utilize it.
The VR will term
Just to be clear, your switches don't need to support VXLAN to utilize it. The
VR will terminate the VXLAN network and translate to a VLAN for your external
traffic.
- Si
From: Imran Ahmed
Sent: Friday, April 14, 2017 12:49 PM
To: users@cloudstack.apache.org
S
Hi Si,
I agree. However we had to go for VLAN due to the physical switch
limitations and limited number of VLANs so far.
Thanks,
Imran
-Original Message-
From: Simon Weller [mailto:swel...@ena.com]
Sent: Friday, April 14, 2017 9:11 PM
To: users@cloudstack.apache.org
Subject: Re: OVS
Hi Dag,
Thank you for your response. I was consulting that documentation link as well.
As the documentation says, after selecting the GRE isolation type for guest
network, we have to enable the OVS plugin under the service providers list
inside cloudstack UI. I could not somehow find OVS in th
I'd strongly suggest you consider using the native VXLAN support for KVM. It
works extremely well and we run it in production.
- Si
From: Dag Sonstebo
Sent: Friday, April 14, 2017 10:57 AM
To: users@cloudstack.apache.org
Subject: Re: OVS Plugin
Hi Imran,
O
Hi Imran,
OVS is the same as GRE tunnelling, which you will have as an isolation method
for guest networking – see
http://docs.cloudstack.apache.org/en/latest/networking/ovs-plugin.html.
Please let us know how you get on – especially how your hypervisor nodes cope
with CPU load once the GRE tu
10 matches
Mail list logo
