: Sunday, July 13, 2014 8:31 AM
To: Czesnowicz, Przemyslaw; OpenStack Development Mailing List (not for usage
questions)
Cc: Mooney, Sean K
Subject: RE: [openstack-dev] [Neutron][ML2] Support dpdk ovs with ml2 plugin
Hi,
For agent way to notify server regarding node specific info, you can leverage
, 2014 8:31 AM
To: Czesnowicz, Przemyslaw; OpenStack Development Mailing List (not for usage
questions)
Cc: Mooney, Sean K
Subject: RE: [openstack-dev] [Neutron][ML2] Support dpdk ovs with ml2 plugin
Hi,
For agent way to notify server regarding node specific info, you can leverage
the periodic
net i/o
Thanks
Przemek
-Original Message-
From: Mathieu Rohon [mailto:mathieu.ro...@gmail.com]
Sent: Friday, July 11, 2014 10:30 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][ML2] Support dpdk ovs with ml2 plugin
A simple
16, 2014 9:07 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][ML2] Support dpdk ovs with ml2 plugin
I don't think this is a usecase that could be supported right now.
There will be multiple issues with running two ovs instances on the node
List (not for usage
questions)
Cc: Mooney, Sean K
Subject: RE: [openstack-dev] [Neutron][ML2] Support dpdk ovs with ml2 plugin
Hi,
Thanks for Your answers.
Yep using binding:vif_details makes more sense. We would like to reuse
VIF_TYPE_OVS and modify the nova to use the userspace vhost when
] Support dpdk ovs with ml2 plugin
+1
It's totally different between ovs and userspace ovs.
also, there is strong need to keep ovs even we have a userspace ovs in the same
host
--
Intel Shannon Limited
Registered in Ireland
Registered
for running both ovs and userspace ovs
on the same host?
Thanks
Przemek
From: loy wolfe [mailto:loywo...@gmail.com]
Sent: Friday, July 11, 2014 3:17 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][ML2] Support dpdk ovs with ml2
the request.
Regards,
Irena
From: loy wolfe [mailto:loywo...@gmail.com]
Sent: Thursday, July 10, 2014 6:00 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Mooney, Sean K
Subject: Re: [openstack-dev] [Neutron][ML2] Support dpdk ovs with ml2 plugin
i think both a new vnic_type
I'd recommend adding this to the weekly Neutron ML2 meeting agenda [1]
and discussing it there. The ML2 sub-team leads (rkukura and Sukhdev)
are both at the Neutron mid-cycle meeting this week, so I'd suggest
next week's meeting.
Thanks!
Kyle
[1] https://wiki.openstack.org/wiki/Meetings/ML2
On
?
Regards
Przemek
From: Irena Berezovsky [mailto:ire...@mellanox.com]
Sent: Thursday, July 10, 2014 8:08 AM
To: OpenStack Development Mailing List (not for usage questions); Czesnowicz,
Przemyslaw
Cc: Mooney, Sean K
Subject: RE: [openstack-dev] [Neutron][ML2] Support dpdk ovs with ml2 plugin
Hi
: [openstack-dev] [Neutron][ML2] Support dpdk ovs with ml2 plugin
I'd recommend adding this to the weekly Neutron ML2 meeting agenda [1] and
discussing it there. The ML2 sub-team leads (rkukura and Sukhdev) are both at
the Neutron mid-cycle meeting this week, so I'd suggest next week's meeting.
Thanks
: [openstack-dev] [Neutron][ML2] Support dpdk ovs with ml2
plugin
Hi,
For passing information from neutron to nova VIF Driver, you should use
binding:vif_details dictionary. You may not require new VIF_TYPE, but can
leverage the existing VIF_TYPE_OVS, and add ‘use_dpdk’ in vif_details
Berezovsky [mailto:ire...@mellanox.com
ire...@mellanox.com]
*Sent:* Thursday, July 10, 2014 8:08 AM
*To:* OpenStack Development Mailing List (not for usage questions);
Czesnowicz, Przemyslaw
*Cc:* Mooney, Sean K
*Subject:* RE: [openstack-dev] [Neutron][ML2] Support dpdk ovs with ml2
plugin
Hi
We (Intel Openstack team) would like to add support for dpdk based userspace
openvswitch using mech_openvswitch and mech_odl from ML2 plugin.
The dpdk enabled ovs comes in two flavours one is netdev incorporated into
vanilla ovs the other is a fork of ovs with a dpdk datapath
i think both a new vnic_type and a new vif_type should be added. now vnic
has three types: normal, direct, macvtap, then we need a new type of
uservhost.
as for vif_type, now we have VIF_TYPE_OVS, VIF_TYPE_QBH/QBG, VIF_HW_VEB, so
we need a new VIF_TYPE_USEROVS
I don't think it's a good idea to
15 matches
Mail list logo