fuel-dev team mailing list archive

[Andrey Korolev <akorolev@xxxxxxxxxxxx>]

- vxlan has a very limited scope of deployment due to its nature - if one
want overlays, all the intermediate hw (or at least ToRs) should recognize
vxlan tag, so new hw must be bought :)

- as a tenant isolation solution inside shared L2 vlans should take place
just because they are more familiar to anyone and L2 will exhaust much
earlier vlan number

- veth pair and ovs patch connectors has very limited PPS performance which
can be reached at the node scope long before bandwidth ceiling on 10G

I`d recommend to NOT to use any Neutron topo in a performance-critical
environments just because OVS limitations in the stacked pie of bridges
Fuel is currently deploying with (even more, current state of vhost_net
limits single instance performance on some gigabits per second, it is most
fundamental ceiling right now). If you`ll be able to integrate DPDK (even
in current state, it should give awesome boost, taking one core for itself
:) ) or any other zerocopy solutions (closed-source or underbaked to date),
the topology will not matter any longer. Also there is no need to flatten
it by same reason - DPDK will receive wider adoption over time and
OpenStack eventually will be able to create complex topologies at node
scope without overhead at the wire speed.


On Tue, Jul 1, 2014 at 8:33 PM, Gregory Elkinbard <gelkinbard@xxxxxxxxxxxx>
wrote:

> Hi guys,
> the key features that I am looking for are actually
> 1) efficient operation at 40 gigabit/s throughput (2x10 gig ethernet
> links going in both directions). This will require 2-3 cores
> 2) partial mesh support. As I understand older ovs will retransmit all
> broadcasts and multicasts to all nodes regardless of whether they need
> them or not in GRE and VXLAN modes. Per Andrew W. this needs OVS 2.1
> or greater.
>
> + Alexander S. as the platform team is also looking at OVS and performance.
>
> Thanks
> Greg
>
>
> On Tue, Jul 1, 2014 at 7:45 AM, Vladimir Kuklin <vkuklin@xxxxxxxxxxxx>
> wrote:
> > Thank you, Andrey
> >
> > Roman, could you please consider at least building versions of OVS 2.1
> for
> > testing purposes to decide whether we will go with OVS 2.1 or stay with
> OVS
> > 1.10?
> >
> >
> > On Tue, Jul 1, 2014 at 6:27 PM, Andrey Korolev <akorolev@xxxxxxxxxxxx>
> > wrote:
> >>
> >> 2.1 has a lot of enhancements primarily for increasing multicore
> vswitchd
> >> performance. Kernel module had improved megaflow heuristic (and nice ip4
> >> tuples which helps to create wildcard flows based on endpoint ip4 header
> >> analysis), though it will be even better in upcoming 2.3.0. If you are
> not
> >> dealing with hundreds of thousands of unique flows per second, 2.0 vs
> 2.1 vs
> >> master makes no difference.
> >>
> >>
> >> On Tue, Jul 1, 2014 at 12:30 PM, Vladimir Kuklin <vkuklin@xxxxxxxxxxxx>
> >> wrote:
> >>>
> >>> I am not quite sure that 2.1.x OVS is going to work with older kernels.
> >>>
> >>> Andrey, can you comment on it? Is it worth adding 2.1 version of OVS or
> >>> may be it is reasonable to update, but to 1.11 or 2.0?
> >>>
> >>>
> >>> On Tue, Jul 1, 2014 at 3:27 AM, Gregory Elkinbard
> >>> <gelkinbard@xxxxxxxxxxxx> wrote:
> >>>>
> >>>> any chance we can update OVS to 2.10?
> >>>>
> >>>> Thanks
> >>>> Greg
> >>>>
> >>>>
> >>>> On Mon, Jun 30, 2014 at 3:36 PM, Roman Vyalov <rvyalov@xxxxxxxxxxxx>
> >>>> wrote:
> >>>> > For Centos:
> >>>> >
> >>>> > kernel: 2.6.32-431 and 3.10.30
> >>>> > OVS: 1.10.2
> >>>> >
> >>>> > For Ubuntu:
> >>>> >
> >>>> > kernel: 3.2.0 and 3.11.0
> >>>> > OVS: 1.10
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>> > On Tue, Jul 1, 2014 at 12:12 AM, Gregory Elkinbard
> >>>> > <gelkinbard@xxxxxxxxxxxx>
> >>>> > wrote:
> >>>> >>
> >>>> >> both for Ubuntu and Centos.
> >>>> >>
> >>>> >> Thanks
> >>>> >> Greg
> >>>> >>
> >>>> >> --
> >>>> >> Mailing list: https://launchpad.net/~fuel-dev
> >>>> >> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> >>>> >> Unsubscribe : https://launchpad.net/~fuel-dev
> >>>> >> More help   : https://help.launchpad.net/ListHelp
> >>>> >
> >>>> >
> >>>>
> >>>> --
> >>>> Mailing list: https://launchpad.net/~fuel-dev
> >>>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> >>>> Unsubscribe : https://launchpad.net/~fuel-dev
> >>>> More help   : https://help.launchpad.net/ListHelp
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> Yours Faithfully,
> >>> Vladimir Kuklin,
> >>> Fuel Library Tech Lead,
> >>> Mirantis, Inc.
> >>> +7 (495) 640-49-04
> >>> +7 (926) 702-39-68
> >>> Skype kuklinvv
> >>> 45bk3, Vorontsovskaya Str.
> >>> Moscow, Russia,
> >>> www.mirantis.com
> >>> www.mirantis.ru
> >>> vkuklin@xxxxxxxxxxxx
> >>
> >>
> >
> >
> >
> > --
> > Yours Faithfully,
> > Vladimir Kuklin,
> > Fuel Library Tech Lead,
> > Mirantis, Inc.
> > +7 (495) 640-49-04
> > +7 (926) 702-39-68
> > Skype kuklinvv
> > 45bk3, Vorontsovskaya Str.
> > Moscow, Russia,
> > www.mirantis.com
> > www.mirantis.ru
> > vkuklin@xxxxxxxxxxxx
>