> -Original Message-
> From: Nikola Đipanov [mailto:ndipa...@redhat.com]
> Sent: Thursday, September 04, 2014 4:22 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Nova][FFE] Feature freeze exception for virt-
> driver-numa-placement
>
> On 09/04/2014 04:51 PM,
Hi Ian,
Spec for “Support vhost-user in libvirt vif driver” [1] has been approved for
Kilo. We should have code available by EOW.
We are also working on a mechanism driver for Neutron as well [2]. We started
working on a 3rd party CI.
Regards
Przemek
[1] https://review.openstack.org/#/c/138
Hi,
I'd like to request an spec freeze exception for "Api add vnic_type support".
https://review.openstack.org/#/c/138808/
There is agreement in SRIOV community that this a very needed change.
This change will simplify using sriov (or other vnic_types) and make it more
flexible.
Thanks,
Przem
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
(https://github
?
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,
For
eeting.
Thanks!
Kyle
[1] https://wiki.openstack.org/wiki/Meetings/ML2
On Wed, Jul 9, 2014 at 10:08 AM, Czesnowicz, Przemyslaw
wrote:
> Hi
>
>
>
> We (Intel Openstack team) would like to add support for dpdk based
> userspace openvswitch using mech_openvswitch and mech_odl from
Can you explain whats the use case 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]
, 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
imple usecase could be to have a compute node able start VM with optimized
net I/O or standard net I/O, depending on the network flavor ordered for this
VM.
On Fri, Jul 11, 2014 at 11:16 AM, Czesnowicz, Przemyslaw
wrote:
>
>
> Can you explain whats the use case for running both ovs and us
Hi Nova Cores,
I would like to ask for spec approval deadline exception for:
https://review.openstack.org/#/c/95805/2
This feature allows using DPDK enabled Open vSwitch with Openstack.
This is an important feature for NFV workloads that require high performance
network I/O.
If the spec is appr
Hi Samta,
This usually means that the vSwitch is not running/has crashed.
Can you check in /opt/stack/logs/ovs-vswitchd.log ? There should be an error
msg there.
Regards
Przemek
> -Original Message-
> From: Samta Rangare [mailto:samtarang...@gmail.com]
> Sent: Monday, November 9, 2015 1
Hi Praveen,
There’s been some changes recently to networking-ovs-dpdk, it no longer host’s
a mech driver as the openviswitch mech driver in Neutron supports vhost-user
ports.
I guess something went wrong and the version of Neutron is not matching
networking-ovs-dpdk. Can you post commit ids of
> -Original Message-
> From: Nikola Đipanov [mailto:ndipa...@redhat.com]
> Sent: Thursday, March 24, 2016 4:34 PM
> To: Sergey Nikitin ; OpenStack Development Mailing
> List (not for usage questions)
> Cc: Czesnowicz, Przemyslaw
> Subject: Re: [openstack-dev]
Hi
> 1) If the device is a "normal" PCI device, but is a network card, am I still
> able to
> take advantage of the advanced syntax added circa Juno to define the
> relationship between that card and a given physical network so that the
> scheduler can place accordingly (and does this still use
Hi,
I would like to request FFE for vhostuser vif driver.
2 reviews :
https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/libvirt-vif-vhost-user,n,z
BP: https://blueprints.launchpad.net/nova/+spec/libvirt-vif-vhost-user
Spec: https://review.openstack.org/1
>There seemed to be two ways to create a VM via cli:
>
>1) use neutron command to create a port first and then use nova command to
>attach the vm to that port(neutron port-create.. >followed by nova boot --nic
>port-id=)
>2)Just use nova command and a port will implicitly be created for you(nova
16 matches
Mail list logo