[openstack-dev] [networking-ovs-dpdk] networking_ovs_dpdk.agent.ovs_dpdk_firewall.OVSFirewallDriver

[Gangur, Hrushikesh]

Is this firewall drive 
'networking_ovs_dpdk.agent.ovs_dpdk_firewall.OVSFirewallDriver' OpenStack 
upstream supported? Any drawback of using this with our OVS-DPDK limitations?

It looks it is part of devstack and works w/ Mitaka
https://github.com/openstack/networking-ovs-dpdk/blob/stable/mitaka/doc/source/getstarted/devstack/ubuntu.rst

Regards~hrushi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [networking-ovs-dpdk] suggested devStack local.conf settings for OpenStack Mitaka with DPDK

[Montorsi, Francesco]

Hi,
I would like to install with DevStack (on a single node) OpenStack Mitaka with 
neutron using OVS+DPDK (so far I managed to create with devstack a Mitaka stack 
using neutron with "vanilla" OVS).
To be clear, I checked out the stable/mitaka devstack branch:
   git clone https://git.openstack.org/openstack-dev/devstack -b stable/mitaka

I'm wondering 3 things though:

1) Do you recommend any change to the networking-ovs-dpdk local.conf file 
advertised here:
   
https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/_downloads/local.conf.single_node
?
(it seems it was updated only 5 months ago, while Mitaka has been released in 
April, 2 months ago)

2) What's the syntax for ML2_VLAN_RANGES option? Is
 ML2_VLAN_RANGES=default:1000-1100
ok?

3) What happens to the bridges that get listed into OVS_BRIDGE_MAPPINGS ? 
I understand they will be bound to DPDK driver... but does this mean that VM 
traffic will use such bridge for exiting the devstack node (e.g., for Internet 
access)?


Thanks a lot for your help,
Francesco Montorsi



PS:
I noticed that the links to the local.conf files in the following webpages are 
out-of-date:
   
https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/usage.rst
   https://github.com/openstack/networking-ovs-dpdk 



Twitter: @Empirix
Website: http://www.empirix.com
Blog: http://blog.empirix.com

600 Technology Park Drive, Suite 100
Billerica, MA 01821
United States


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk] availability

[Martinx - ジェームズ]

On 3 January 2016 at 23:41, Palanisamy, Prabhakaran (Contractor)
 wrote:
> Hi,
>
>
>
> Is networking-ovs-dpdk package available non devstack installation ??
>
>
>
> Thanks,
>
> PP

Hi,

Don't know if it will help you but, Ubuntu Xenial (development
branch), have interesting packages:

root@xenial-1:~# apt-cache search ovs dpdk
openvswitch-switch-dpdk - DPDK enabled Open vSwitch switch implementation
python-networking-ovs-dpdk - OpenStack virtual network service - Open
vSwitch DPDK ML2 mechanism driver

Also, Xenial will support DPDK 2.2 natively, for at least, 5 years.

I'm trying to experiment Mitaka beta release on Xenial these days...

Best,
Thiago

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [networking-ovs-dpdk] Can this be used outside devstack?

[Palanisamy, Prabhakaran (Contractor)]

Hi All,

We already having a kilo openstack installed on 2 node setup(not devstack). is 
it possible to enable dpdk packages as additional to it?? If yes could you 
please let us know where we can find the same.

Thanks,
PP
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [networking-ovs-dpdk] availability

[Palanisamy, Prabhakaran (Contractor)]

Hi,

Is networking-ovs-dpdk package available non devstack installation ??

Thanks,
PP
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk] availability

[Mooney, Sean K]

Hi,
it is possible to install and configure networking-ovs-dpdk without 
Using the devstack plugin however we currently do not have documentation for 
this process.
The openstack configuration required to enable the ovs agent and ml2 driver 
provided by networking-ovs-dpdk
Is minimal. The compilation/installation/configuration and deamonisation of ovs 
with dpdk is significantly more involved
Which was the motivation for creating the devstack plugin originally. 

If a manual install guide is something you would like the best way to provide 
and track
Feature request is to simply open a bug 
https://bugs.launchpad.net/networking-ovs-dpdk 

A manual install guide is something we are considering adding  but we are 
currently prioritizing  adding support for deploying 
Via puppet. We are also working with others  in opnfv to integrate our puppet 
module based install with fuel via a new fuel plugin.
This work is aiming to support a liberty based install.

Regarding packaging one of the items I had hoped to do before the holiday break 
was
Releases the current tags of the networking-ovs-dpdk repo to pypi.

Before publishing to pypi I will be changing our tagging scheme form 
Openstack older date based versions to the newer semantic scheme.
I hope to publish the packages to pypi later this week and will also be
Tagging new releases of both the kilo and liberty stable branches in the next 
2-4 weeks.

In the new format the 1.X releases will correspond to kilo (2015.1 -> 1.0, 
2015.1.1 ->1.1)
2.X will correspond to liberty 
3.X will correspond to mitaka.

It should be noted that currently with mitaka the networking-ovs-dpdk is only 
require to provided
Security group support. Base support for booting vms with vhost-user and ovs 
with dpdk  has been merged into
Upstream neutron as part of the standard neutron ovs agent and ml2 driver. 
 
We hope to contribute the openflow security group driver to neutron before 
mitaka-2 for review.
If that is accepted in the mitaka cycle the networking-ovs-dpdk will only 
contain deployment code
As all runtime features will be upstream.

Regards
sean

-Original Message-
From: Martinx - ジェームズ [mailto:thiagocmarti...@gmail.com] 
Sent: Monday, January 4, 2016 2:00 AM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [networking-ovs-dpdk] availability

On 3 January 2016 at 23:41, Palanisamy, Prabhakaran (Contractor) 
<prabhakaran_palanis...@cable.comcast.com> wrote:
> Hi,
>
>
>
> Is networking-ovs-dpdk package available non devstack installation ??
>
>
>
> Thanks,
>
> PP

Hi,

Don't know if it will help you but, Ubuntu Xenial (development branch), have 
interesting packages:

root@xenial-1:~# apt-cache search ovs dpdk openvswitch-switch-dpdk - DPDK 
enabled Open vSwitch switch implementation python-networking-ovs-dpdk - 
OpenStack virtual network service - Open vSwitch DPDK ML2 mechanism driver

Also, Xenial will support DPDK 2.2 natively, for at least, 5 years.

I'm trying to experiment Mitaka beta release on Xenial these days...

Best,
Thiago

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

[yujie]

Hi Sean,
 I noticed that above talking using openstack with dpdk only in devstack.
 I already have kilo environment and want it to support dpdk. Could 
reinstalling ovs with dpdk will be work?

Thanks.
Yu


在 2015/11/27 20:38, Mooney, Sean K 写道:

For kilo we provided a single node all in one example config here
https://github.com/openstack/networking-ovs-dpdk/blob/stable/kilo/doc/source/_downloads/local.conf_example

I have modified that to be a controller with the interfaces and ips form your 
controller local.conf.
I do not have any kilo compute local.conf to hand but I modified an old compute 
local.conf to so that it should work
Using the ip and interface settings from your compute local.conf.


Regards
Sean.

From: Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com]
Sent: Friday, November 27, 2015 9:21 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with 
Unexpected vif_type=binding_failed

Hi Sean,

I have changed the hostname in both machines.
and tried again still i have the same error.

I am trying to configure ovs-dpdk with vlan now.
For the kilo version the getting started guide was missing in the repository.
But i have changed the repositories everywhere to kilo.

Please find the attached loal.conf for compute and controller.

one change i have made is i have added ml2 plusgin as vlan for compute config 
also.
because if i exactly use the local.confs as in example the controller was vlan 
and compute is taking as vxlan for the ml2 config.

And please find all the errors present in the compute and controller.

Thanks
Praveen

On Thu, Nov 26, 2015 at 5:58 PM, Mooney, Sean K 
<sean.k.moo...@intel.com<mailto:sean.k.moo...@intel.com>> wrote:
Openstack uses the hostname as a primary key in many of the project.
Nova and neutron both do this.
If you had two nodes with the same host name then it would cause undefined 
behavior.

Based on the error Andreas highlighted  are you currently trying to configure 
ovs-dpdk with vxlan/gre?

I also noticed that the getting started guide you linked to earlier was for the 
master branch(mitaka) but
You mentioned you were deploying kilo.
The local.conf settings will be different in both case.





-Original Message-
From: Andreas Scheuring 
[mailto:scheu...@linux.vnet.ibm.com<mailto:scheu...@linux.vnet.ibm.com>]
Sent: Thursday, November 26, 2015 1:43 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with 
Unexpected vif_type=binding_failed

Praveen,
there are many error in your q-svc log.
It says:

InvalidInput: Invalid input for operation: (u'Tunnel IP %(ip)s in use with host 
%(host)s', {'ip': u'10.81.1.150', 'host':
u'localhost.localdomain'}).\n"]


Did you maybe specify duplicated ips in your controllers and compute nodes 
neutron tunnel config?

Or did you change the hostname after installation

Or maybe the code has trouble with duplicated host names?

--
Andreas
(IRC: scheuran)



On Di, 2015-11-24 at 15:28 +0100, Praveen MANKARA RADHAKRISHNAN wrote:
> Hi Sean,
>
>
> Thanks for the reply.
>
>
> Please find the logs attached.
> ovs-dpdk is correctly running in compute.
>
>
> Thanks
> Praveen
>
> On Tue, Nov 24, 2015 at 3:04 PM, Mooney, Sean K
> <sean.k.moo...@intel.com<mailto:sean.k.moo...@intel.com>> wrote:
>  Hi would you be able to attach the
>
>  n-cpu log form the computenode  and  the
>
>  n-sch and q-svc logs for the controller so we can see if there
>  is a stack trace relating to the
>
>  vm boot.
>
>
>
>  Also can you confirm ovs-dpdk is running correctly on the
>  compute node by running
>
>  sudo service ovs-dpdk status
>
>
>
>  the neutron and networking-ovs-dpdk commits are from their
>  respective stable/kilo branches so they should be compatible
>
>  provided no breaking changes have been merged to either
>  branch.
>
>
>
>  regards
>
>  sean.
>
>
>
>  From: Praveen MANKARA RADHAKRISHNAN
>  [mailto:praveen.mank...@6wind.com<mailto:praveen.mank...@6wind.com>]
>      Sent: Tuesday, November 24, 2015 1:39 PM
>  To: OpenStack Development Mailing List (not for usage
>  questions)
>  Subject: Re: [openstack-dev] [networking-ovs-dpdk] VM creation
>  fails with Unexpected vif_type=binding_failed
>
>
>
>  Hi Przemek,
>
>
>
>
>  Thanks For the response,
>
>
>
>
>
>  Here are the commit ids for Neutron and networking-ovs-dpdk
>
>
>
>
>
>  [stack@localhost neutron]$ git log --format=

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

[Mooney, Sean K]

For kilo we provided a single node all in one example config here
https://github.com/openstack/networking-ovs-dpdk/blob/stable/kilo/doc/source/_downloads/local.conf_example

I have modified that to be a controller with the interfaces and ips form your 
controller local.conf.
I do not have any kilo compute local.conf to hand but I modified an old compute 
local.conf to so that it should work
Using the ip and interface settings from your compute local.conf.


Regards
Sean.

From: Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com]
Sent: Friday, November 27, 2015 9:21 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with 
Unexpected vif_type=binding_failed

Hi Sean,

I have changed the hostname in both machines.
and tried again still i have the same error.

I am trying to configure ovs-dpdk with vlan now.
For the kilo version the getting started guide was missing in the repository.
But i have changed the repositories everywhere to kilo.

Please find the attached loal.conf for compute and controller.

one change i have made is i have added ml2 plusgin as vlan for compute config 
also.
because if i exactly use the local.confs as in example the controller was vlan 
and compute is taking as vxlan for the ml2 config.

And please find all the errors present in the compute and controller.

Thanks
Praveen

On Thu, Nov 26, 2015 at 5:58 PM, Mooney, Sean K 
<sean.k.moo...@intel.com<mailto:sean.k.moo...@intel.com>> wrote:
Openstack uses the hostname as a primary key in many of the project.
Nova and neutron both do this.
If you had two nodes with the same host name then it would cause undefined 
behavior.

Based on the error Andreas highlighted  are you currently trying to configure 
ovs-dpdk with vxlan/gre?

I also noticed that the getting started guide you linked to earlier was for the 
master branch(mitaka) but
You mentioned you were deploying kilo.
The local.conf settings will be different in both case.





-Original Message-
From: Andreas Scheuring 
[mailto:scheu...@linux.vnet.ibm.com<mailto:scheu...@linux.vnet.ibm.com>]
Sent: Thursday, November 26, 2015 1:43 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with 
Unexpected vif_type=binding_failed

Praveen,
there are many error in your q-svc log.
It says:

InvalidInput: Invalid input for operation: (u'Tunnel IP %(ip)s in use with host 
%(host)s', {'ip': u'10.81.1.150', 'host':
u'localhost.localdomain'}).\n"]


Did you maybe specify duplicated ips in your controllers and compute nodes 
neutron tunnel config?

Or did you change the hostname after installation

Or maybe the code has trouble with duplicated host names?

--
Andreas
(IRC: scheuran)



On Di, 2015-11-24 at 15:28 +0100, Praveen MANKARA RADHAKRISHNAN wrote:
> Hi Sean,
>
>
> Thanks for the reply.
>
>
> Please find the logs attached.
> ovs-dpdk is correctly running in compute.
>
>
> Thanks
> Praveen
>
> On Tue, Nov 24, 2015 at 3:04 PM, Mooney, Sean K
> <sean.k.moo...@intel.com<mailto:sean.k.moo...@intel.com>> wrote:
> Hi would you be able to attach the
>
> n-cpu log form the computenode  and  the
>
> n-sch and q-svc logs for the controller so we can see if there
> is a stack trace relating to the
>
> vm boot.
>
>
>
> Also can you confirm ovs-dpdk is running correctly on the
> compute node by running
>
> sudo service ovs-dpdk status
>
>
>
> the neutron and networking-ovs-dpdk commits are from their
> respective stable/kilo branches so they should be compatible
>
> provided no breaking changes have been merged to either
> branch.
>
>
>
> regards
>
> sean.
>
>
>
> From: Praveen MANKARA RADHAKRISHNAN
> [mailto:praveen.mank...@6wind.com<mailto:praveen.mank...@6wind.com>]
>     Sent: Tuesday, November 24, 2015 1:39 PM
> To: OpenStack Development Mailing List (not for usage
> questions)
> Subject: Re: [openstack-dev] [networking-ovs-dpdk] VM creation
> fails with Unexpected vif_type=binding_failed
>
>
>
> Hi Przemek,
>
>
>
>
> Thanks For the response,
>
>
>
>
>
> Here are the commit ids for Neutron and networking-ovs-dpdk
>
>
>
>
>
> [stack@localhost neutron]$ git log --format="%H" -n 1
>
>
> 026bfc6421da796075f71a9ad4378674f619193d
>
>
> [stack@localhost neutron]$ cd ..
>
>
> [stack@localhost ~]$ cd networking-ovs-dpdk/
>
>
> [stack@localhost networking-ovs-dpdk]$  git log --format=

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

[Praveen MANKARA RADHAKRISHNAN]

Hi,

One thing i observed is there is no packets coming to the dpdk interface
(data network).
I have verified it with the tcpdump using mirror interface.
and if i assign ip address and ping each other the data network bridges
that is also not working.
could this be a possible cause for the nova exception? (NovaException:
Unexpected vif_type=binding_failed)

Thanks
Praveen

On Tue, Nov 24, 2015 at 3:28 PM, Praveen MANKARA RADHAKRISHNAN <
praveen.mank...@6wind.com> wrote:

> Hi Sean,
>
> Thanks for the reply.
>
> Please find the logs attached.
> ovs-dpdk is correctly running in compute.
>
> Thanks
> Praveen
>
> On Tue, Nov 24, 2015 at 3:04 PM, Mooney, Sean K <sean.k.moo...@intel.com>
> wrote:
>
>> Hi would you be able to attach the
>>
>> n-cpu log form the computenode  and  the
>>
>> n-sch and q-svc logs for the controller so we can see if there is a stack
>> trace relating to the
>>
>> vm boot.
>>
>>
>>
>> Also can you confirm ovs-dpdk is running correctly on the compute node by
>> running
>>
>> sudo service ovs-dpdk status
>>
>>
>>
>> the neutron and networking-ovs-dpdk commits are from their respective
>> stable/kilo branches so they should be compatible
>>
>> provided no breaking changes have been merged to either branch.
>>
>>
>>
>> regards
>>
>> sean.
>>
>>
>>
>> *From:* Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com]
>> *Sent:* Tuesday, November 24, 2015 1:39 PM
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails
>> with Unexpected vif_type=binding_failed
>>
>>
>>
>> Hi Przemek,
>>
>>
>>
>> Thanks For the response,
>>
>>
>>
>> Here are the commit ids for Neutron and networking-ovs-dpdk
>>
>>
>>
>> [stack@localhost neutron]$ git log --format="%H" -n 1
>>
>> 026bfc6421da796075f71a9ad4378674f619193d
>>
>> [stack@localhost neutron]$ cd ..
>>
>> [stack@localhost ~]$ cd networking-ovs-dpdk/
>>
>> [stack@localhost networking-ovs-dpdk]$  git log --format="%H" -n 1
>>
>> 90dd03a76a7e30cf76ecc657f23be8371b1181d2
>>
>>
>>
>> The Neutron agents are up and running in compute node.
>>
>>
>>
>> Thanks
>>
>> Praveen
>>
>>
>>
>>
>>
>> On Tue, Nov 24, 2015 at 12:57 PM, Czesnowicz, Przemyslaw <
>> przemyslaw.czesnow...@intel.com> wrote:
>>
>> 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 Neutron and
>> networking-ovs-dpdk.
>>
>>
>>
>> The other possibility is that the Neutron agent is not running/died on
>> the compute node.
>>
>> Check with:
>>
>> neutron agent-list
>>
>>
>>
>> Przemek
>>
>>
>>
>> *From:* Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com]
>> *Sent:* Tuesday, November 24, 2015 12:18 PM
>> *To:* openstack-dev@lists.openstack.org
>> *Subject:* [openstack-dev] [networking-ovs-dpdk] VM creation fails with
>> Unexpected vif_type=binding_failed
>>
>>
>>
>> Hi,
>>
>>
>>
>> Am trying to set up an open stack (kilo) installation using ovs-dpdk
>> through devstack installation.
>>
>>
>>
>> I have followed the "
>> https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/getstarted.rst
>> " documentation.
>>
>>
>>
>> I used the same versions as in documentation (fedora21, with right
>> kernel).
>>
>>
>>
>> My openstack installation is successful in both controller and compute.
>>
>> I have used example local.conf given in the documentation.
>>
>> But if i try to spawn the VM. I am having the following error.
>>
>>
>>
>> "NovaException: Unexpected vif_type=binding_failed"
>>
>>
>>
>> It would be really helpful if you can point out how to debug and fix this
>> error.
>>
>>
>>
>> Thanks
>>
>> Praveen
>>
>>
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

[Mooney, Sean K]

Am when you say dpdk interface do you mean dpdk physical interface is not 
reciving any packets or a vhost-user interface.

Can you provide the output of ovs-vsctl show.
And sudo /opt/stack/DPDK-v2.1.0/tools/dpdk_nic_bind.py –status

You should see an output similar to this.
Network devices using DPDK-compatible driver

:02:00.0 'Ethernet Controller XL710 for 40GbE QSFP+' drv=igb_uio unused=i40e

Network devices using kernel driver
===
:02:00.1 'Ethernet Controller XL710 for 40GbE QSFP+' if=ens785f1 drv=i40e 
unused=igb_uio
:02:00.2 'Ethernet Controller XL710 for 40GbE QSFP+' if=ens785f2 drv=i40e 
unused=igb_uio
:02:00.3 'Ethernet Controller XL710 for 40GbE QSFP+' if=ens785f3 drv=i40e 
unused=igb_uio
:06:00.0 'I350 Gigabit Network Connection' if=enp6s0f0 drv=igb 
unused=igb_uio
:06:00.1 'I350 Gigabit Network Connection' if=enp6s0f1 drv=igb 
unused=igb_uio

Other network devices
=



From: Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com]
Sent: Thursday, November 26, 2015 9:46 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with 
Unexpected vif_type=binding_failed

Hi,

One thing i observed is there is no packets coming to the dpdk interface (data 
network).
I have verified it with the tcpdump using mirror interface.
and if i assign ip address and ping each other the data network bridges that is 
also not working.
could this be a possible cause for the nova exception? (NovaException: 
Unexpected vif_type=binding_failed)

Thanks
Praveen

On Tue, Nov 24, 2015 at 3:28 PM, Praveen MANKARA RADHAKRISHNAN 
<praveen.mank...@6wind.com<mailto:praveen.mank...@6wind.com>> wrote:
Hi Sean,

Thanks for the reply.

Please find the logs attached.
ovs-dpdk is correctly running in compute.

Thanks
Praveen

On Tue, Nov 24, 2015 at 3:04 PM, Mooney, Sean K 
<sean.k.moo...@intel.com<mailto:sean.k.moo...@intel.com>> wrote:
Hi would you be able to attach the
n-cpu log form the computenode  and  the
n-sch and q-svc logs for the controller so we can see if there is a stack trace 
relating to the
vm boot.

Also can you confirm ovs-dpdk is running correctly on the compute node by 
running
sudo service ovs-dpdk status

the neutron and networking-ovs-dpdk commits are from their respective 
stable/kilo branches so they should be compatible
provided no breaking changes have been merged to either branch.

regards
sean.

From: Praveen MANKARA RADHAKRISHNAN 
[mailto:praveen.mank...@6wind.com<mailto:praveen.mank...@6wind.com>]
Sent: Tuesday, November 24, 2015 1:39 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with 
Unexpected vif_type=binding_failed

Hi Przemek,

Thanks For the response,

Here are the commit ids for Neutron and networking-ovs-dpdk

[stack@localhost neutron]$ git log --format="%H" -n 1
026bfc6421da796075f71a9ad4378674f619193d
[stack@localhost neutron]$ cd ..
[stack@localhost ~]$ cd networking-ovs-dpdk/
[stack@localhost networking-ovs-dpdk]$  git log --format="%H" -n 1
90dd03a76a7e30cf76ecc657f23be8371b1181d2

The Neutron agents are up and running in compute node.

Thanks
Praveen


On Tue, Nov 24, 2015 at 12:57 PM, Czesnowicz, Przemyslaw 
<przemyslaw.czesnow...@intel.com<mailto:przemyslaw.czesnow...@intel.com>> wrote:
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 Neutron and networking-ovs-dpdk.

The other possibility is that the Neutron agent is not running/died on the 
compute node.
Check with:
neutron agent-list

Przemek

From: Praveen MANKARA RADHAKRISHNAN 
[mailto:praveen.mank...@6wind.com<mailto:praveen.mank...@6wind.com>]
Sent: Tuesday, November 24, 2015 12:18 PM
To: openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [networking-ovs-dpdk] VM creation fails with 
Unexpected vif_type=binding_failed

Hi,

Am trying to set up an open stack (kilo) installation using ovs-dpdk through 
devstack installation.

I have followed the " 
https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/getstarted.rst
 " documentation.

I used the same versions as in documentation (fedora21, with right kernel).

My openstack installation is successful in both controller and compute.
I have used example local.conf given in the documentation.
But if i try to spawn the VM. I am having the following error.

"NovaException: Unexpected vif_type=binding_failed"

It

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

[Praveen MANKARA RADHAKRISHNAN]

compatible driver
>
> 
>
> :02:00.0 'Ethernet Controller XL710 for 40GbE QSFP+' drv=igb_uio
> unused=i40e
>
>
>
> Network devices using kernel driver
>
> ===
>
> :02:00.1 'Ethernet Controller XL710 for 40GbE QSFP+' if=ens785f1
> drv=i40e unused=igb_uio
>
> :02:00.2 'Ethernet Controller XL710 for 40GbE QSFP+' if=ens785f2
> drv=i40e unused=igb_uio
>
> :02:00.3 'Ethernet Controller XL710 for 40GbE QSFP+' if=ens785f3
> drv=i40e unused=igb_uio
>
> :06:00.0 'I350 Gigabit Network Connection' if=enp6s0f0 drv=igb
> unused=igb_uio
>
> :06:00.1 'I350 Gigabit Network Connection' if=enp6s0f1 drv=igb
> unused=igb_uio
>
>
>
> Other network devices
>
> =
>
> 
>
>
>
>
>
> *From:* Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com]
> *Sent:* Thursday, November 26, 2015 9:46 AM
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails
> with Unexpected vif_type=binding_failed
>
>
>
> Hi,
>
>
>
> One thing i observed is there is no packets coming to the dpdk interface
> (data network).
>
> I have verified it with the tcpdump using mirror interface.
>
> and if i assign ip address and ping each other the data network bridges
> that is also not working.
>
> could this be a possible cause for the nova exception? (NovaException:
> Unexpected vif_type=binding_failed)
>
>
>
> Thanks
>
> Praveen
>
>
>
> On Tue, Nov 24, 2015 at 3:28 PM, Praveen MANKARA RADHAKRISHNAN <
> praveen.mank...@6wind.com> wrote:
>
> Hi Sean,
>
>
>
> Thanks for the reply.
>
>
>
> Please find the logs attached.
>
> ovs-dpdk is correctly running in compute.
>
>
>
> Thanks
>
> Praveen
>
>
>
> On Tue, Nov 24, 2015 at 3:04 PM, Mooney, Sean K <sean.k.moo...@intel.com>
> wrote:
>
> Hi would you be able to attach the
>
> n-cpu log form the computenode  and  the
>
> n-sch and q-svc logs for the controller so we can see if there is a stack
> trace relating to the
>
> vm boot.
>
>
>
> Also can you confirm ovs-dpdk is running correctly on the compute node by
> running
>
> sudo service ovs-dpdk status
>
>
>
> the neutron and networking-ovs-dpdk commits are from their respective
> stable/kilo branches so they should be compatible
>
> provided no breaking changes have been merged to either branch.
>
>
>
> regards
>
> sean.
>
>
>
> *From:* Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com]
> *Sent:* Tuesday, November 24, 2015 1:39 PM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails
> with Unexpected vif_type=binding_failed
>
>
>
> Hi Przemek,
>
>
>
> Thanks For the response,
>
>
>
> Here are the commit ids for Neutron and networking-ovs-dpdk
>
>
>
> [stack@localhost neutron]$ git log --format="%H" -n 1
>
> 026bfc6421da796075f71a9ad4378674f619193d
>
> [stack@localhost neutron]$ cd ..
>
> [stack@localhost ~]$ cd networking-ovs-dpdk/
>
> [stack@localhost networking-ovs-dpdk]$  git log --format="%H" -n 1
>
> 90dd03a76a7e30cf76ecc657f23be8371b1181d2
>
>
>
> The Neutron agents are up and running in compute node.
>
>
>
> Thanks
>
> Praveen
>
>
>
>
>
> On Tue, Nov 24, 2015 at 12:57 PM, Czesnowicz, Przemyslaw <
> przemyslaw.czesnow...@intel.com> wrote:
>
> 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 Neutron and
> networking-ovs-dpdk.
>
>
>
> The other possibility is that the Neutron agent is not running/died on the
> compute node.
>
> Check with:
>
> neutron agent-list
>
>
>
> Przemek
>
>
>
> *From:* Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com]
> *Sent:* Tuesday, November 24, 2015 12:18 PM
> *To:* openstack-dev@lists.openstack.org
> *Subject:* [openstack-dev] [networking-ovs-dpdk] VM creation fails with
> Unexpected vif_type=binding_failed
>
>
>
> Hi,
>
>
>
> Am trying to set up an open stack (kilo) installation using ovs-dpdk
> through devstack installation.
>
>
>
> I have followed the "

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

[Andreas Scheuring]

Praveen, 
there are many error in your q-svc log.
It says:

InvalidInput: Invalid input for operation: (u'Tunnel IP %(ip)s in use
with host %(host)s', {'ip': u'10.81.1.150', 'host':
u'localhost.localdomain'}).\n"]


Did you maybe specify duplicated ips in your controllers and compute
nodes neutron tunnel config?

Or did you change the hostname after installation

Or maybe the code has trouble with duplicated host names?

-- 
Andreas
(IRC: scheuran)



On Di, 2015-11-24 at 15:28 +0100, Praveen MANKARA RADHAKRISHNAN wrote:
> Hi Sean, 
> 
> 
> Thanks for the reply. 
> 
> 
> Please find the logs attached. 
> ovs-dpdk is correctly running in compute.
> 
> 
> Thanks
> Praveen 
> 
> On Tue, Nov 24, 2015 at 3:04 PM, Mooney, Sean K
> <sean.k.moo...@intel.com> wrote:
> Hi would you be able to attach the
> 
> n-cpu log form the computenode  and  the
> 
> n-sch and q-svc logs for the controller so we can see if there
> is a stack trace relating to the
> 
> vm boot.
> 
>  
> 
> Also can you confirm ovs-dpdk is running correctly on the
> compute node by running 
> 
> sudo service ovs-dpdk status
> 
>  
> 
> the neutron and networking-ovs-dpdk commits are from their
> respective stable/kilo branches so they should be compatible
> 
> provided no breaking changes have been merged to either
> branch.
> 
>  
> 
> regards
> 
> sean.
> 
>  
> 
> From: Praveen MANKARA RADHAKRISHNAN
> [mailto:praveen.mank...@6wind.com] 
>     Sent: Tuesday, November 24, 2015 1:39 PM
> To: OpenStack Development Mailing List (not for usage
> questions)
> Subject: Re: [openstack-dev] [networking-ovs-dpdk] VM creation
> fails with Unexpected vif_type=binding_failed
> 
>  
> 
> Hi Przemek,
> 
>  
> 
> 
> Thanks For the response, 
> 
> 
>  
> 
> 
> Here are the commit ids for Neutron and networking-ovs-dpdk 
> 
> 
>  
> 
> 
> [stack@localhost neutron]$ git log --format="%H" -n 1
> 
> 
> 026bfc6421da796075f71a9ad4378674f619193d
> 
> 
> [stack@localhost neutron]$ cd ..
> 
> 
> [stack@localhost ~]$ cd networking-ovs-dpdk/
> 
> 
> [stack@localhost networking-ovs-dpdk]$  git log --format="%H"
> -n 1
> 
> 
> 90dd03a76a7e30cf76ecc657f23be8371b1181d2
> 
> 
>  
> 
> 
> The Neutron agents are up and running in compute node. 
> 
> 
>  
> 
> 
> Thanks 
> 
> 
> Praveen
> 
> 
>  
> 
> 
>  
> 
> On Tue, Nov 24, 2015 at 12:57 PM, Czesnowicz, Przemyslaw
> <przemyslaw.czesnow...@intel.com> wrote:
> 
> 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 Neutron and networking-ovs-dpdk.
> 
>  
> 
> The other possibility is that the Neutron agent is not
> running/died on the compute node.
> 
> Check with:
>     
>     neutron agent-list
> 
>  
> 
> Przemek
> 
>  
> 
> From: Praveen MANKARA RADHAKRISHNAN
> [mailto:praveen.mank...@6wind.com] 
> Sent: Tuesday, November 24, 2015 12:18 PM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [networking-ovs-dpdk] VM
> creation f

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

[Mooney, Sean K]

Openstack uses the hostname as a primary key in many of the project.
Nova and neutron both do this.
If you had two nodes with the same host name then it would cause undefined 
behavior. 

Based on the error Andreas highlighted  are you currently trying to configure 
ovs-dpdk with vxlan/gre?

I also noticed that the getting started guide you linked to earlier was for the 
master branch(mitaka) but
You mentioned you were deploying kilo.
The local.conf settings will be different in both case.





-Original Message-
From: Andreas Scheuring [mailto:scheu...@linux.vnet.ibm.com] 
Sent: Thursday, November 26, 2015 1:43 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with 
Unexpected vif_type=binding_failed

Praveen,
there are many error in your q-svc log.
It says:

InvalidInput: Invalid input for operation: (u'Tunnel IP %(ip)s in use with host 
%(host)s', {'ip': u'10.81.1.150', 'host':
u'localhost.localdomain'}).\n"]


Did you maybe specify duplicated ips in your controllers and compute nodes 
neutron tunnel config?

Or did you change the hostname after installation

Or maybe the code has trouble with duplicated host names?

--
Andreas
(IRC: scheuran)



On Di, 2015-11-24 at 15:28 +0100, Praveen MANKARA RADHAKRISHNAN wrote:
> Hi Sean, 
> 
> 
> Thanks for the reply. 
> 
> 
> Please find the logs attached. 
> ovs-dpdk is correctly running in compute.
> 
> 
> Thanks
> Praveen 
> 
> On Tue, Nov 24, 2015 at 3:04 PM, Mooney, Sean K
> <sean.k.moo...@intel.com> wrote:
> Hi would you be able to attach the
> 
> n-cpu log form the computenode  and  the
> 
> n-sch and q-svc logs for the controller so we can see if there
> is a stack trace relating to the
> 
> vm boot.
> 
>  
> 
> Also can you confirm ovs-dpdk is running correctly on the
> compute node by running 
> 
> sudo service ovs-dpdk status
> 
>  
> 
> the neutron and networking-ovs-dpdk commits are from their
> respective stable/kilo branches so they should be compatible
> 
> provided no breaking changes have been merged to either
> branch.
> 
>  
> 
> regards
> 
> sean.
> 
>  
> 
> From: Praveen MANKARA RADHAKRISHNAN
> [mailto:praveen.mank...@6wind.com] 
>     Sent: Tuesday, November 24, 2015 1:39 PM
> To: OpenStack Development Mailing List (not for usage
> questions)
> Subject: Re: [openstack-dev] [networking-ovs-dpdk] VM creation
> fails with Unexpected vif_type=binding_failed
> 
>  
> 
> Hi Przemek,
> 
>  
> 
> 
> Thanks For the response, 
> 
> 
>  
> 
> 
> Here are the commit ids for Neutron and networking-ovs-dpdk 
> 
> 
>  
> 
> 
> [stack@localhost neutron]$ git log --format="%H" -n 1
> 
> 
> 026bfc6421da796075f71a9ad4378674f619193d
> 
> 
> [stack@localhost neutron]$ cd ..
> 
> 
> [stack@localhost ~]$ cd networking-ovs-dpdk/
> 
> 
> [stack@localhost networking-ovs-dpdk]$  git log --format="%H"
> -n 1
> 
> 
> 90dd03a76a7e30cf76ecc657f23be8371b1181d2
> 
> 
>  
> 
> 
> The Neutron agents are up and running in compute node. 
> 
> 
>  
> 
> 
> Thanks 
> 
> 
> Praveen
> 
> 
>  
> 
> 
>  
> 
> On Tue, Nov 24, 2015 at 12:57 PM, Czesnowicz, Przemyslaw
> <przemyslaw.czesnow...@intel.com> wrote:
> 
> 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 Neutron and networking-ovs-dpdk.
> 
> 

[openstack-dev] [networking-ovs-dpdk]

[Samta Rangare]

Hello Everyone,

Now that we have installed ovs-dpdk along with all necessary prerequisite
repo (ovs,dpdk,libvirt etc) from devstack setup, we would like to install
it via *puppet*.

I see a puppet folder in networking-ovs (
https://github.com/openstack/networking-ovs-dpdk/tree/master/puppet) but
dont know how to use it, meaning that *how to use puppet manifest to
install netutron ovs-dpdk agent. *

Can somebody walk me through any guide or document available to use these
puppet module for installing agent and creating environment as we did it in
devstack ?

Thanks,
Samta Rangare
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk]

[Hui Xiang]

FYI,  bug 1513367 is opened for this apparmor problem to track when booting
vms failed with ovs-dpdk enabled.

https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1513367

On Tue, Nov 24, 2015 at 9:49 PM, Mooney, Sean K <sean.k.moo...@intel.com>
wrote:

> Out of interest
>
> Have you removed apparmor or placed all Libvirt apparmor profies into
> complain mode?
>
>
>
> If not you will get permission denied errors.
>
>
>
> You can confirm by checking dmesg to see if you have any permission denied
> messages from apparmor
>
> Or run aa-status and see if the the Libvirt profie is in enforce/complain
> mode.
>
>
>
> The  /tmp/qemu.orig file is just a file we write the original qemu command
> to for debugging. It is not needed
>
> But all uses should be able to read/write to /tmp.
>
>
>
> We wrap the qemu/kvm binary with a script that on Ubuntu can be found here
> /usr/bin/kvm
>
>
>
> If you comment out echo "qemu ${args[@]}" > /tmp/qemu.orig in this script
> it will silence that warning.
>
>
>
>
> https://github.com/openstack/networking-ovs-dpdk/blob/master/devstack/libs/ovs-dpdk#L104
>
>
>
> I may remove this from our wrapper script as we most never use it for
> debugging  anymore however in the past it was
>
> Useful to compare the original qemu command line and the update qemu
> command line.
>
>
>
> I don’t know if I have mentioned this before but we also have a Ubuntu
> version of our getting start guide that should merge shortly
>
>
>
> https://review.openstack.org/#/c/243190/6/doc/source/getstarted/ubuntu.rst
>
>
>
> Regards
>
> Sean.
>
>
>
> *From:* Prathyusha Guduri [mailto:prathyushaconne...@gmail.com]
> *Sent:* Tuesday, November 24, 2015 12:42 PM
> *To:* Mooney, Sean K
> *Cc:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [networking-ovs-dpdk]
>
>
>
> Hi All,
>
> I also found another error while launching an instance.
>
> libvirtError: internal error: process exited while connecting to monitor:
> /usr/bin/kvm-spice: line 42: /tmp/qemu.orig: Permission denied
>
> I dont want to change any permissions manually and again face the
> dependency issues. So kindly help
>
> Thanks,
>
> Prathyusha
>
>
>
>
>
>
>
> On Tue, Nov 24, 2015 at 4:02 PM, Prathyusha Guduri <
> prathyushaconne...@gmail.com> wrote:
>
> Hi Sean,
>
> Thanks for you kind help.
>
> I did the following.
>
> # apt-get install ubuntu-cloud-keyring
> # echo "deb http://ubuntu-cloud.archive.canonical.com/ubuntu
> <http://www.google.com/url?q=http%3A%2F%2Fubuntu-cloud.archive.canonical.com%2Fubuntu=D=1=AFQjCNGlCfoplf1zSbILNxCSVK23zRxa2A>"
> \
> "trusty-updates/kilo main" > /etc/apt/sources.list.d/cloudarchive-kilo.list
> # apt-get update && apt-get dist-upgrade
>
> and then uninstalled the libvirt and qemu that were installed manually and
> then ran stack.sh after cleaning and unstacking.
>
> Now fortunately libvirt and qemu satisfy minimum requirements.
>
> $ virsh --version
> 1.2.12
>
> $ kvm --version
> /usr/bin/kvm: line 42: /tmp/qemu.orig: Permission denied
> QEMU emulator version 2.2.0 (Debian 1:2.2+dfsg-5expubuntu9.3~cloud0),
> Copyright (c) 2003-2008 Fabrice Bellard
>
> Am using an ubuntu 14.04 system
> $ uname -a
> Linux ubuntu-Precision-Tower-5810 3.13.0-24-generic #46-Ubuntu SMP Thu Apr
> 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
>
> After stack.sh which was successful, tried creating a new instance - which
> gave an ERROR again.
>
> $ nova list
>
> +--++++-+---+
> | ID   | Name   | Status | Task
> State | Power State | Networks
> |
>
> +--++++-+---+
> | 31a7e160-d04c-4216-91cf-30ce86c2b1fa | demo-instance1 | ERROR  |
> -  | NOSTATE | private=10.0.0.3,
> fd34:f4c5:412:0:f816:3eff:fea4:b9fe |
>
> $ sudo service ovs-dpdk status
> sourcing config
> ovs alive
> VHOST_CONFIG: bind to /var/run/openvswitch/vhufb8052e5-d3
> 2015-11-24T10:23:25Z|00126|dpdk|INFO|Socket
> /var/run/openvswitch/vhufb8052e5-d3 created for vhost-user port
> vhufb8052e5-d3
> 2015-11-24T10:23:25Z|4|dpif_netdev(pmd18)|INFO|Core 2 processing port
> 'vhufb8052e5-d3'
> 2015-11-24T10:23:25Z|2|dpif_netdev(pmd19)|INFO|Core 8 processing port
> 'dpdk0'
> 2015-11-24T10:23:25Z|00127|

Re: [openstack-dev] [networking-ovs-dpdk]

[Prathyusha Guduri]

Thank you so much Sean,

It helped a lot and that I have VMs active running :) That's so kind of you
to spend your time. It would be nice if this apparmor thing is mentioned
somewhere in the documentation, will help newbies like me.

@Hui - Thank you for the info and the config file :)

Thanks,
Prathyusha


On Wed, Nov 25, 2015 at 7:28 AM, Hui Xiang <hui.xi...@canonical.com> wrote:

> FYI,  bug 1513367 is opened for this apparmor problem to track when
> booting vms failed with ovs-dpdk enabled.
>
> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1513367
>
> On Tue, Nov 24, 2015 at 9:49 PM, Mooney, Sean K <sean.k.moo...@intel.com>
> wrote:
>
>> Out of interest
>>
>> Have you removed apparmor or placed all Libvirt apparmor profies into
>> complain mode?
>>
>>
>>
>> If not you will get permission denied errors.
>>
>>
>>
>> You can confirm by checking dmesg to see if you have any permission
>> denied messages from apparmor
>>
>> Or run aa-status and see if the the Libvirt profie is in enforce/complain
>> mode.
>>
>>
>>
>> The  /tmp/qemu.orig file is just a file we write the original qemu
>> command to for debugging. It is not needed
>>
>> But all uses should be able to read/write to /tmp.
>>
>>
>>
>> We wrap the qemu/kvm binary with a script that on Ubuntu can be found
>> here /usr/bin/kvm
>>
>>
>>
>> If you comment out echo "qemu ${args[@]}" > /tmp/qemu.orig in this script
>> it will silence that warning.
>>
>>
>>
>>
>> https://github.com/openstack/networking-ovs-dpdk/blob/master/devstack/libs/ovs-dpdk#L104
>>
>>
>>
>> I may remove this from our wrapper script as we most never use it for
>> debugging  anymore however in the past it was
>>
>> Useful to compare the original qemu command line and the update qemu
>> command line.
>>
>>
>>
>> I don’t know if I have mentioned this before but we also have a Ubuntu
>> version of our getting start guide that should merge shortly
>>
>>
>>
>> https://review.openstack.org/#/c/243190/6/doc/source/getstarted/ubuntu.rst
>>
>>
>>
>> Regards
>>
>> Sean.
>>
>>
>>
>> *From:* Prathyusha Guduri [mailto:prathyushaconne...@gmail.com]
>> *Sent:* Tuesday, November 24, 2015 12:42 PM
>> *To:* Mooney, Sean K
>> *Cc:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [networking-ovs-dpdk]
>>
>>
>>
>> Hi All,
>>
>> I also found another error while launching an instance.
>>
>> libvirtError: internal error: process exited while connecting to monitor:
>> /usr/bin/kvm-spice: line 42: /tmp/qemu.orig: Permission denied
>>
>> I dont want to change any permissions manually and again face the
>> dependency issues. So kindly help
>>
>> Thanks,
>>
>> Prathyusha
>>
>>
>>
>>
>>
>>
>>
>> On Tue, Nov 24, 2015 at 4:02 PM, Prathyusha Guduri <
>> prathyushaconne...@gmail.com> wrote:
>>
>> Hi Sean,
>>
>> Thanks for you kind help.
>>
>> I did the following.
>>
>> # apt-get install ubuntu-cloud-keyring
>> # echo "deb http://ubuntu-cloud.archive.canonical.com/ubuntu
>> <http://www.google.com/url?q=http%3A%2F%2Fubuntu-cloud.archive.canonical.com%2Fubuntu=D=1=AFQjCNGlCfoplf1zSbILNxCSVK23zRxa2A>"
>> \
>> "trusty-updates/kilo main" >
>> /etc/apt/sources.list.d/cloudarchive-kilo.list
>> # apt-get update && apt-get dist-upgrade
>>
>> and then uninstalled the libvirt and qemu that were installed manually
>> and then ran stack.sh after cleaning and unstacking.
>>
>> Now fortunately libvirt and qemu satisfy minimum requirements.
>>
>> $ virsh --version
>> 1.2.12
>>
>> $ kvm --version
>> /usr/bin/kvm: line 42: /tmp/qemu.orig: Permission denied
>> QEMU emulator version 2.2.0 (Debian 1:2.2+dfsg-5expubuntu9.3~cloud0),
>> Copyright (c) 2003-2008 Fabrice Bellard
>>
>> Am using an ubuntu 14.04 system
>> $ uname -a
>> Linux ubuntu-Precision-Tower-5810 3.13.0-24-generic #46-Ubuntu SMP Thu
>> Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
>>
>> After stack.sh which was successful, tried creating a new instance -
>> which gave an ERROR again.
>>
>> $ nova list
>>
>> +--++++-+---

Re: [openstack-dev] [networking-ovs-dpdk]

[Prathyusha Guduri]

t; If you are on fedora 21 then the virt-preview repo packages the required
> Libvirt and qemu.
>
> On Ubuntu the kilo cloud archive also packages version that meet the
> minimum versions.
>
> Looking at the log I would agree that this error is probably related to
> manually installing Libvirt and
> not adding the appropriate libvirtd configuration options.
>
> Devstack does not have native support for installing a vhost-user
> compatible Libvirt or qemu.
> when using our networking-ovs-dpdk plugin we ask you to enable the
> virt-prevew or cloud archive
> Before stacking so that when devestack install Libvirt/qemu it get
> compatible versions.
> for centos as we have been unable to find an equivalent we explicitly
> install Libvirt/qemu.
>
> In general we don’t provide support for installing the required version
> Libvirt/qemu in
> the networking-ovs-dpdk devstack plugin.
>
> What os are you currently using? ubuntu?
> in your case enabling the kilo cloud archive, uinstalling Libvirt/qemu and
> then restacking
> should provide the appropriate packages.
>
> In liberty we use that standard neutron openvswich agent binary and set
> the agent type to DPDK OVS Agent to enable
> the ovsdpdk ml2 driver to manage the node. In mitaka the standard ovs
> neutron agent and standard openvswitch ml2 drivers will be used instead.
>
>
>
> To confirm if ovs-dpdk is running you can use the following command
>
> sudo service ovs-dpdk status
>
> this will check if ovs-dpdk is running by reading the pid files and
> checking if the ovsdb and ovs-vswitchd
> process are running and tail the last 20ish lines of the vswitchd log file.
>
> note this is not a systemd service so the systemd equivalent command will
> not work.
>
>
>
> Alternative you can user ps and grep
>
> ps aux | grep ovs
>
>
>
> regards
>
> sean.
>
>
>
>
>
>
>
> *From:* Prathyusha Guduri [mailto:prathyushaconne...@gmail.com]
> *Sent:* Monday, November 23, 2015 9:16 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [networking-ovs-dpdk]
>
>
>
> Hi Sean,
>
> Thanks for your help before. It would be great if you look into another
> issue too.
>
> Am able to run stack.sh successfully and all services are up. But,
>
> libvirt version was 1.2.2 and qemu version was 2.0.0
>
> To satisfy the minimum requirement of qemu- version >=2.1 and
> libvirt-version >= 1.2.10
>
> I manually installed qemu and libvirt from respective sources.
>
> Now
> $ kvm --version
>  /usr/bin/kvm: line 42: /tmp/qemu.orig: Permission denied
>  QEMU emulator version 2.1.3, Copyright (c) 2003-2008 Fabrice Bellard
>
> $ virsh --version
> 1.2.10
>
> So basic requirement is satisfied.
>
> Before creating an instance ran the below command,
> $ nova flavor-key m1.tiny set "hw:mem_page_size=large"
>
> Now created an instance
> $ nova boot --flavor m1.tiny --image cirros-0.3.4-x86_64-uec --nic
> net-id=445e2dc5-221b-48ea-aea4-d04dee12fc7f --security-group default
> demo-instance1
>
> It gives the ERROR :
>
> 2015-11-23 13:19:59.654 ERROR nova.virt.libvirt.host
> [req-2d9d060d-1934-4e9e-af1c-010e177bea11 None None] Connection to
> libvirt failed: error from service: CheckAuthorization: Did not receive a
> reply. Possible causes include: the remote application did not send a
> reply, the message bus security policy blocked the reply, the reply timeout
> expired, or the network connection was broken.
> 2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host Traceback (most
> recent call last):
> 2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host   File
> "/opt/stack/nova/nova/virt/libvirt/host.py", line 527, in get_connection
> 2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host conn =
> self._get_connection()
> 2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host   File
> "/opt/stack/nova/nova/virt/libvirt/host.py", line 514, in _get_connection
> 2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host wrapped_conn =
> self._get_new_connection()
> 2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host   File
> "/opt/stack/nova/nova/virt/libvirt/host.py", line 466, in
> _get_new_connection
> 2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host wrapped_conn =
> self._connect(self._uri, self._read_only)
> 2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host   File
> "/opt/stack/nova/nova/virt/libvirt/host.py", line 320, in _connect
> 2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host libvirt.openAuth,
> uri, auth, flags)
> 2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host   File
> "/usr/local/lib/

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

[Mooney, Sean K]

Hi would you be able to attach the
n-cpu log form the computenode  and  the
n-sch and q-svc logs for the controller so we can see if there is a stack trace 
relating to the
vm boot.

Also can you confirm ovs-dpdk is running correctly on the compute node by 
running
sudo service ovs-dpdk status

the neutron and networking-ovs-dpdk commits are from their respective 
stable/kilo branches so they should be compatible
provided no breaking changes have been merged to either branch.

regards
sean.

From: Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com]
Sent: Tuesday, November 24, 2015 1:39 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with 
Unexpected vif_type=binding_failed

Hi Przemek,

Thanks For the response,

Here are the commit ids for Neutron and networking-ovs-dpdk

[stack@localhost neutron]$ git log --format="%H" -n 1
026bfc6421da796075f71a9ad4378674f619193d
[stack@localhost neutron]$ cd ..
[stack@localhost ~]$ cd networking-ovs-dpdk/
[stack@localhost networking-ovs-dpdk]$  git log --format="%H" -n 1
90dd03a76a7e30cf76ecc657f23be8371b1181d2

The Neutron agents are up and running in compute node.

Thanks
Praveen


On Tue, Nov 24, 2015 at 12:57 PM, Czesnowicz, Przemyslaw 
<przemyslaw.czesnow...@intel.com<mailto:przemyslaw.czesnow...@intel.com>> wrote:
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 Neutron and networking-ovs-dpdk.

The other possibility is that the Neutron agent is not running/died on the 
compute node.
Check with:
neutron agent-list

Przemek

From: Praveen MANKARA RADHAKRISHNAN 
[mailto:praveen.mank...@6wind.com<mailto:praveen.mank...@6wind.com>]
Sent: Tuesday, November 24, 2015 12:18 PM
To: openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [networking-ovs-dpdk] VM creation fails with 
Unexpected vif_type=binding_failed

Hi,

Am trying to set up an open stack (kilo) installation using ovs-dpdk through 
devstack installation.

I have followed the " 
https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/getstarted.rst
 " documentation.

I used the same versions as in documentation (fedora21, with right kernel).

My openstack installation is successful in both controller and compute.
I have used example local.conf given in the documentation.
But if i try to spawn the VM. I am having the following error.

"NovaException: Unexpected vif_type=binding_failed"

It would be really helpful if you can point out how to debug and fix this error.

Thanks
Praveen


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

[Andreas Scheuring]

Please have a look at your neutron server log and neutron agent log and
provide this information if you have troubles interpreting the messages.

Probably you'll find the reason there!


-- 
Andreas
(IRC: scheuran)



On Di, 2015-11-24 at 12:17 +0100, Praveen MANKARA RADHAKRISHNAN wrote:
> Hi,
> 
> 
> Am trying to set up an open stack (kilo) installation using ovs-dpdk
> through devstack installation. 
> 
> 
> I have followed the "
> https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/getstarted.rst
>  " documentation. 
> 
> 
> I used the same versions as in documentation (fedora21, with right
> kernel). 
> 
> 
> My openstack installation is successful in both controller and
> compute. 
> I have used example local.conf given in the documentation. 
> But if i try to spawn the VM. I am having the following error. 
> 
> 
> "NovaException: Unexpected vif_type=binding_failed" 
> 
> 
> 
> It would be really helpful if you can point out how to debug and fix
> this error. 
> 
> 
> Thanks
> Praveen
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

[Praveen MANKARA RADHAKRISHNAN]

Hi,

Am trying to set up an open stack (kilo) installation using ovs-dpdk
through devstack installation.

I have followed the "
https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/getstarted.rst
" documentation.

I used the same versions as in documentation (fedora21, with right kernel).

My openstack installation is successful in both controller and compute.
I have used example local.conf given in the documentation.
But if i try to spawn the VM. I am having the following error.

"NovaException: Unexpected vif_type=binding_failed"

It would be really helpful if you can point out how to debug and fix this
error.

Thanks
Praveen
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

[Czesnowicz, Przemyslaw]

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 Neutron and networking-ovs-dpdk.

The other possibility is that the Neutron agent is not running/died on the 
compute node.
Check with:
neutron agent-list

Przemek

From: Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com]
Sent: Tuesday, November 24, 2015 12:18 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [networking-ovs-dpdk] VM creation fails with 
Unexpected vif_type=binding_failed

Hi,

Am trying to set up an open stack (kilo) installation using ovs-dpdk through 
devstack installation.

I have followed the " 
https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/getstarted.rst
 " documentation.

I used the same versions as in documentation (fedora21, with right kernel).

My openstack installation is successful in both controller and compute.
I have used example local.conf given in the documentation.
But if i try to spawn the VM. I am having the following error.

"NovaException: Unexpected vif_type=binding_failed"

It would be really helpful if you can point out how to debug and fix this error.

Thanks
Praveen

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk] VM creation fails with Unexpected vif_type=binding_failed

[Praveen MANKARA RADHAKRISHNAN]

Hi Przemek,

Thanks For the response,

Here are the commit ids for Neutron and networking-ovs-dpdk

[stack@localhost neutron]$ git log --format="%H" -n 1
026bfc6421da796075f71a9ad4378674f619193d
[stack@localhost neutron]$ cd ..
[stack@localhost ~]$ cd networking-ovs-dpdk/
[stack@localhost networking-ovs-dpdk]$  git log --format="%H" -n 1
90dd03a76a7e30cf76ecc657f23be8371b1181d2

The Neutron agents are up and running in compute node.

Thanks
Praveen


On Tue, Nov 24, 2015 at 12:57 PM, Czesnowicz, Przemyslaw <
przemyslaw.czesnow...@intel.com> wrote:

> 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 Neutron and
> networking-ovs-dpdk.
>
>
>
> The other possibility is that the Neutron agent is not running/died on the
> compute node.
>
> Check with:
>
> neutron agent-list
>
>
>
> Przemek
>
>
>
> *From:* Praveen MANKARA RADHAKRISHNAN [mailto:praveen.mank...@6wind.com]
> *Sent:* Tuesday, November 24, 2015 12:18 PM
> *To:* openstack-dev@lists.openstack.org
> *Subject:* [openstack-dev] [networking-ovs-dpdk] VM creation fails with
> Unexpected vif_type=binding_failed
>
>
>
> Hi,
>
>
>
> Am trying to set up an open stack (kilo) installation using ovs-dpdk
> through devstack installation.
>
>
>
> I have followed the "
> https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/getstarted.rst
> " documentation.
>
>
>
> I used the same versions as in documentation (fedora21, with right
> kernel).
>
>
>
> My openstack installation is successful in both controller and compute.
>
> I have used example local.conf given in the documentation.
>
> But if i try to spawn the VM. I am having the following error.
>
>
>
> "NovaException: Unexpected vif_type=binding_failed"
>
>
>
> It would be really helpful if you can point out how to debug and fix this
> error.
>
>
>
> Thanks
>
> Praveen
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk]

[Mooney, Sean K]

Out of interest
Have you removed apparmor or placed all Libvirt apparmor profies into complain 
mode?

If not you will get permission denied errors.

You can confirm by checking dmesg to see if you have any permission denied 
messages from apparmor
Or run aa-status and see if the the Libvirt profie is in enforce/complain mode.

The  /tmp/qemu.orig file is just a file we write the original qemu command to 
for debugging. It is not needed
But all uses should be able to read/write to /tmp.

We wrap the qemu/kvm binary with a script that on Ubuntu can be found here 
/usr/bin/kvm

If you comment out echo "qemu ${args[@]}" > /tmp/qemu.orig in this script it 
will silence that warning.

https://github.com/openstack/networking-ovs-dpdk/blob/master/devstack/libs/ovs-dpdk#L104

I may remove this from our wrapper script as we most never use it for debugging 
 anymore however in the past it was
Useful to compare the original qemu command line and the update qemu command 
line.

I don’t know if I have mentioned this before but we also have a Ubuntu version 
of our getting start guide that should merge shortly

https://review.openstack.org/#/c/243190/6/doc/source/getstarted/ubuntu.rst

Regards
Sean.

From: Prathyusha Guduri [mailto:prathyushaconne...@gmail.com]
Sent: Tuesday, November 24, 2015 12:42 PM
To: Mooney, Sean K
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [networking-ovs-dpdk]

Hi All,

I also found another error while launching an instance.

libvirtError: internal error: process exited while connecting to monitor: 
/usr/bin/kvm-spice: line 42: /tmp/qemu.orig: Permission denied
I dont want to change any permissions manually and again face the dependency 
issues. So kindly help
Thanks,
Prathyusha



On Tue, Nov 24, 2015 at 4:02 PM, Prathyusha Guduri 
<prathyushaconne...@gmail.com<mailto:prathyushaconne...@gmail.com>> wrote:
Hi Sean,
Thanks for you kind help.
I did the following.

# apt-get install ubuntu-cloud-keyring
# echo "deb 
http://ubuntu-cloud.archive.canonical.com/ubuntu<http://www.google.com/url?q=http%3A%2F%2Fubuntu-cloud.archive.canonical.com%2Fubuntu=D=1=AFQjCNGlCfoplf1zSbILNxCSVK23zRxa2A>"
 \
"trusty-updates/kilo main" > /etc/apt/sources.list.d/cloudarchive-kilo.list
# apt-get update && apt-get dist-upgrade
and then uninstalled the libvirt and qemu that were installed manually and then 
ran stack.sh after cleaning and unstacking.
Now fortunately libvirt and qemu satisfy minimum requirements.

$ virsh --version
1.2.12

$ kvm --version
/usr/bin/kvm: line 42: /tmp/qemu.orig: Permission denied
QEMU emulator version 2.2.0 (Debian 1:2.2+dfsg-5expubuntu9.3~cloud0), Copyright 
(c) 2003-2008 Fabrice Bellard

Am using an ubuntu 14.04 system
$ uname -a
Linux ubuntu-Precision-Tower-5810 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 
19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
After stack.sh which was successful, tried creating a new instance - which gave 
an ERROR again.

$ nova list
+--++++-+---+
| ID   | Name   | Status | Task State | 
Power State | Networks  |
+--++++-+---+
| 31a7e160-d04c-4216-91cf-30ce86c2b1fa | demo-instance1 | ERROR  | -  | 
NOSTATE | private=10.0.0.3, fd34:f4c5:412:0:f816:3eff:fea4:b9fe |

$ sudo service ovs-dpdk status
sourcing config
ovs alive
VHOST_CONFIG: bind to /var/run/openvswitch/vhufb8052e5-d3
2015-11-24T10:23:25Z|00126|dpdk|INFO|Socket /var/run/openvswitch/vhufb8052e5-d3 
created for vhost-user port vhufb8052e5-d3
2015-11-24T10:23:25Z|4|dpif_netdev(pmd18)|INFO|Core 2 processing port 
'vhufb8052e5-d3'
2015-11-24T10:23:25Z|2|dpif_netdev(pmd19)|INFO|Core 8 processing port 
'dpdk0'
2015-11-24T10:23:25Z|00127|bridge|INFO|bridge br-int: added interface 
vhufb8052e5-d3 on port 6
2015-11-24T10:23:25Z|5|dpif_netdev(pmd18)|INFO|Core 2 processing port 
'dpdk0'
2015-11-24T10:23:26Z|00128|connmgr|INFO|br-int<->unix: 1 flow_mods in the last 
0 s (1 deletes)
2015-11-24T10:23:26Z|00129|ofp_util|INFO|normalization changed ofp_match, 
details:
2015-11-24T10:23:26Z|00130|ofp_util|INFO| pre: in_port=5,nw_proto=58,tp_src=136
2015-11-24T10:23:26Z|00131|ofp_util|INFO|post: in_port=5
2015-11-24T10:23:26Z|00132|connmgr|INFO|br-int<->unix: 1 flow_mods in the last 
0 s (1 deletes)
2015-11-24T10:23:26Z|00133|connmgr|INFO|br-int<->unix: 1 flow_mods in the last 
0 s (1 deletes)
2015-11-24T10:23:29Z|00134|bridge|WARN|could not open network device 
vhufb8052e5-d3 (No such device)
VHOST_CONFIG: socket created, fd:52
VHOST_CONFIG: bind to /var/run/openvswitch/vhufb8052e5-d3
2015-11-24T10:23:29Z|00135|d

Re: [openstack-dev] [networking-ovs-dpdk]

[Prathyusha Guduri]

va.compute.resource_tracker
> [^[[01;36mreq-24fc3f16-ccd5-4e2d-b583-60ade23bc1ed ^[[00;36mNone
> None^[[00;36m] ^[[01;35m^[[00;36mAuditing locally available compute
> resources for node ubuntu-Precision-Tower-5810^[[00m
> 2015-11-24 15:47:28.087 ^[[00;32mDEBUG nova.compute.resource_tracker
> [^[[01;36mreq-24fc3f16-ccd5-4e2d-b583-60ade23bc1ed ^[[00;36mNone
> None^[[00;32m] ^[[01;35m^[[00;32mHypervisor: free VCPUs: 9^[[00m
> ^[[00;33mfrom (pid=7880) _report_hypervisor_resource_view
> /opt/stack/nova/nova/compute/resource_tracker.py:588^[[00m
>
> I dont understand where am I missing out now.
>
>
>
> On Mon, Nov 23, 2015 at 7:50 PM, Mooney, Sean K <sean.k.moo...@intel.com>
> wrote:
>
>> Hi
>>
>> qemu version was 2.0.0 does not support mapping hugepage as shared.
>> as a result the dpdk implementation of vhost-user cannot function with
>> this version.
>> Similarly libvirt 1.2.2 has no knowledge of vhost-user.
>>
>> If you are on fedora 21 then the virt-preview repo packages the required
>> Libvirt and qemu.
>>
>> On Ubuntu the kilo cloud archive also packages version that meet the
>> minimum versions.
>>
>> Looking at the log I would agree that this error is probably related to
>> manually installing Libvirt and
>> not adding the appropriate libvirtd configuration options.
>>
>> Devstack does not have native support for installing a vhost-user
>> compatible Libvirt or qemu.
>> when using our networking-ovs-dpdk plugin we ask you to enable the
>> virt-prevew or cloud archive
>> Before stacking so that when devestack install Libvirt/qemu it get
>> compatible versions.
>> for centos as we have been unable to find an equivalent we explicitly
>> install Libvirt/qemu.
>>
>> In general we don’t provide support for installing the required version
>> Libvirt/qemu in
>> the networking-ovs-dpdk devstack plugin.
>>
>> What os are you currently using? ubuntu?
>> in your case enabling the kilo cloud archive, uinstalling Libvirt/qemu
>> and then restacking
>> should provide the appropriate packages.
>>
>> In liberty we use that standard neutron openvswich agent binary and set
>> the agent type to DPDK OVS Agent to enable
>> the ovsdpdk ml2 driver to manage the node. In mitaka the standard ovs
>> neutron agent and standard openvswitch ml2 drivers will be used instead.
>>
>>
>>
>> To confirm if ovs-dpdk is running you can use the following command
>>
>> sudo service ovs-dpdk status
>>
>> this will check if ovs-dpdk is running by reading the pid files and
>> checking if the ovsdb and ovs-vswitchd
>> process are running and tail the last 20ish lines of the vswitchd log
>> file.
>>
>> note this is not a systemd service so the systemd equivalent command will
>> not work.
>>
>>
>>
>> Alternative you can user ps and grep
>>
>> ps aux | grep ovs
>>
>>
>>
>> regards
>>
>> sean.
>>
>>
>>
>>
>>
>>
>>
>> *From:* Prathyusha Guduri [mailto:prathyushaconne...@gmail.com]
>> *Sent:* Monday, November 23, 2015 9:16 AM
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [networking-ovs-dpdk]
>>
>>
>>
>> Hi Sean,
>>
>> Thanks for your help before. It would be great if you look into another
>> issue too.
>>
>> Am able to run stack.sh successfully and all services are up. But,
>>
>> libvirt version was 1.2.2 and qemu version was 2.0.0
>>
>> To satisfy the minimum requirement of qemu- version >=2.1 and
>> libvirt-version >= 1.2.10
>>
>> I manually installed qemu and libvirt from respective sources.
>>
>> Now
>> $ kvm --version
>>  /usr/bin/kvm: line 42: /tmp/qemu.orig: Permission denied
>>  QEMU emulator version 2.1.3, Copyright (c) 2003-2008 Fabrice Bellard
>>
>> $ virsh --version
>> 1.2.10
>>
>> So basic requirement is satisfied.
>>
>> Before creating an instance ran the below command,
>> $ nova flavor-key m1.tiny set "hw:mem_page_size=large"
>>
>> Now created an instance
>> $ nova boot --flavor m1.tiny --image cirros-0.3.4-x86_64-uec --nic
>> net-id=445e2dc5-221b-48ea-aea4-d04dee12fc7f --security-group default
>> demo-instance1
>>
>> It gives the ERROR :
>>
>> 2015-11-23 13:19:59.654 ERROR nova.virt.libvirt.host
>> [req-2d9d060d-1934-4e9e-af1c-010e177bea11 None None] Connection to
>> libvirt failed: error from service: CheckAuthorization: Did n

Re: [openstack-dev] [networking-ovs-dpdk]

[Prathyusha Guduri]

Hi Sean,

Thanks for your help before. It would be great if you look into another
issue too.

Am able to run stack.sh successfully and all services are up. But,
libvirt version was 1.2.2 and qemu version was 2.0.0

To satisfy the minimum requirement of qemu- version >=2.1 and
libvirt-version >= 1.2.10
I manually installed qemu and libvirt from respective sources.

Now
$ kvm --version
 /usr/bin/kvm: line 42: /tmp/qemu.orig: Permission denied
 QEMU emulator version 2.1.3, Copyright (c) 2003-2008 Fabrice Bellard

$ virsh --version
1.2.10

So basic requirement is satisfied.

Before creating an instance ran the below command,
$ nova flavor-key m1.tiny set "hw:mem_page_size=large"

Now created an instance
$ nova boot --flavor m1.tiny --image cirros-0.3.4-x86_64-uec --nic
net-id=445e2dc5-221b-48ea-aea4-d04dee12fc7f --security-group default
demo-instance1

It gives the ERROR :

2015-11-23 13:19:59.654 ERROR nova.virt.libvirt.host
[req-2d9d060d-1934-4e9e-af1c-010e177bea11 None None] Connection to libvirt
failed: error from service: CheckAuthorization: Did not receive a reply.
Possible causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout expired,
or the network connection was broken.
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host Traceback (most recent
call last):
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host   File
"/opt/stack/nova/nova/virt/libvirt/host.py", line 527, in get_connection
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host conn =
self._get_connection()
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host   File
"/opt/stack/nova/nova/virt/libvirt/host.py", line 514, in _get_connection
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host wrapped_conn =
self._get_new_connection()
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host   File
"/opt/stack/nova/nova/virt/libvirt/host.py", line 466, in
_get_new_connection
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host wrapped_conn =
self._connect(self._uri, self._read_only)
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host   File
"/opt/stack/nova/nova/virt/libvirt/host.py", line 320, in _connect
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host libvirt.openAuth,
uri, auth, flags)
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host   File
"/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 141, in
proxy_call
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host rv = execute(f,
*args, **kwargs)
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host   File
"/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 122, in
execute
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host six.reraise(c, e,
tb)
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host   File
"/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 80, in
tworker
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host rv = meth(*args,
**kwargs)
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host   File
"/usr/local/lib/python2.7/dist-packages/libvirt.py", line 105, in openAuth
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host if ret is
None:raise libvirtError('virConnectOpenAuth() failed')
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host libvirtError: error
from service: CheckAuthorization: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host
Traceback (most recent call last):

I suspect this is because, I manually installed libvirt and qemu. My doubt
is why devstack is not installing a correct version when it is supposed to.
why a version less than min requirement is being installed???
Now that because am installing manually, there might be a problem with
groups - devstack creates some group and installs but manual installation
doesn't bother about that groups.
Can you please suggest a way on how do avoid that???

Also, I just want to make sure that the agent running is
neutron-openvswitch only. No ovsdpdk agent running.
$ ps -Al | grep neutron
0 S  1000  8882  8859  3  80   0 - 49946 ep_pol pts/34   00:02:24
neutron-openvsw

But
$ neutron agent-list
3385a430-5738-43cb-b853-059add5ab602 | DPDK OVS Agent |
ubuntu-Precision-Tower-5810 | :-)   | True   |
neutron-openvswitch-agent

So this implies that dpdk agent is running right??? I remember reading in
launchpad bugs that ovsdpdk agent is removed and that now openvswitch takes
care of everything. Just wanted to confirm that my setup has ovs-dpdk
running.

Regards,
Prathyusha


On Wed, Nov 18, 2015 at 7:23 PM, James Page  wrote:

> Hi Sean
>
> On Wed, Nov 18, 2015 at 12:30 PM, Mooney, Sean K 
> wrote:
>
>> Hi james
>>
>> Yes we are planning on testing the packaged release to see if it is
>> compatible with our ml2 driver 

Re: [openstack-dev] [networking-ovs-dpdk]

[Mooney, Sean K]

Hi
qemu version was 2.0.0 does not support mapping hugepage as shared.
as a result the dpdk implementation of vhost-user cannot function with this 
version.
Similarly libvirt 1.2.2 has no knowledge of vhost-user.
If you are on fedora 21 then the virt-preview repo packages the required 
Libvirt and qemu.
On Ubuntu the kilo cloud archive also packages version that meet the minimum 
versions.
Looking at the log I would agree that this error is probably related to 
manually installing Libvirt and
not adding the appropriate libvirtd configuration options.
Devstack does not have native support for installing a vhost-user compatible 
Libvirt or qemu.
when using our networking-ovs-dpdk plugin we ask you to enable the virt-prevew 
or cloud archive
Before stacking so that when devestack install Libvirt/qemu it get compatible 
versions.
for centos as we have been unable to find an equivalent we explicitly install 
Libvirt/qemu.
In general we don’t provide support for installing the required version 
Libvirt/qemu in
the networking-ovs-dpdk devstack plugin.
What os are you currently using? ubuntu?
in your case enabling the kilo cloud archive, uinstalling Libvirt/qemu and then 
restacking
should provide the appropriate packages.
In liberty we use that standard neutron openvswich agent binary and set the 
agent type to DPDK OVS Agent to enable
the ovsdpdk ml2 driver to manage the node. In mitaka the standard ovs neutron 
agent and standard openvswitch ml2 drivers will be used instead.

To confirm if ovs-dpdk is running you can use the following command
sudo service ovs-dpdk status
this will check if ovs-dpdk is running by reading the pid files and checking if 
the ovsdb and ovs-vswitchd
process are running and tail the last 20ish lines of the vswitchd log file.
note this is not a systemd service so the systemd equivalent command will not 
work.

Alternative you can user ps and grep
ps aux | grep ovs

regards
sean.



From: Prathyusha Guduri [mailto:prathyushaconne...@gmail.com]
Sent: Monday, November 23, 2015 9:16 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [networking-ovs-dpdk]

Hi Sean,
Thanks for your help before. It would be great if you look into another issue 
too.
Am able to run stack.sh successfully and all services are up. But,
libvirt version was 1.2.2 and qemu version was 2.0.0
To satisfy the minimum requirement of qemu- version >=2.1 and libvirt-version 
>= 1.2.10
I manually installed qemu and libvirt from respective sources.
Now
$ kvm --version
 /usr/bin/kvm: line 42: /tmp/qemu.orig: Permission denied
 QEMU emulator version 2.1.3, Copyright (c) 2003-2008 Fabrice Bellard

$ virsh --version
1.2.10
So basic requirement is satisfied.
Before creating an instance ran the below command,
$ nova flavor-key m1.tiny set "hw:mem_page_size=large"
Now created an instance
$ nova boot --flavor m1.tiny --image cirros-0.3.4-x86_64-uec --nic 
net-id=445e2dc5-221b-48ea-aea4-d04dee12fc7f --security-group default 
demo-instance1
It gives the ERROR :

2015-11-23 13:19:59.654 ERROR nova.virt.libvirt.host 
[req-2d9d060d-1934-4e9e-af1c-010e177bea11 None None] Connection to libvirt 
failed: error from service: CheckAuthorization: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host Traceback (most recent 
call last):
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host   File 
"/opt/stack/nova/nova/virt/libvirt/host.py", line 527, in get_connection
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host conn = 
self._get_connection()
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host   File 
"/opt/stack/nova/nova/virt/libvirt/host.py", line 514, in _get_connection
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host wrapped_conn = 
self._get_new_connection()
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host   File 
"/opt/stack/nova/nova/virt/libvirt/host.py", line 466, in _get_new_connection
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host wrapped_conn = 
self._connect(self._uri, self._read_only)
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host   File 
"/opt/stack/nova/nova/virt/libvirt/host.py", line 320, in _connect
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host libvirt.openAuth, uri, 
auth, flags)
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host   File 
"/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 141, in 
proxy_call
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host rv = execute(f, *args, 
**kwargs)
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host   File 
"/usr/local/lib/python2.7/dist-packages/eventlet/tpool.py", line 122, in execute
2015-11-23 13:19:59.654 TRACE nova.virt.libvirt.host six.reraise(c, e, tb)
2015-11-23 13:1

Re: [openstack-dev] [networking-ovs-dpdk]

[James Page]

Hi All

Reading through this thread I thought participants might be interested to
know that Ubuntu now provides a DPDK enabled Open vSwitch package in Ubuntu
15.10 and for Ubuntu 14.04 using the Liberty UCA; you can use it as follows:

   sudo add-apt-repository cloud-archive:liberty  # not required for 15.10
   sudo apt-get update
   sudo apt-get install openvswitch-switch-dpdk
   sudo update-alternatives --set
ovs-vswitchd /usr/lib/openvswitch-switch-dpdk/ovs-vswitchd-dpdk
   sudo service openvswitch-switch restart

DPDK configuration is passed through OVS using
/etc/default/openvswitch-switch (read for details).  The dpdk package also
provides some basic configuration mechanisms for hugepages and binding
networking adapters to userspace in /etc/dpdk.

This is a first packaging release and is experimental - please do provide
feedback on what you do and don't like about it...

On Wed, Nov 18, 2015 at 6:12 AM, Prathyusha Guduri <
prathyushaconne...@gmail.com> wrote:

> Thanks a lot Sean, that was helpful.
>
> Changing the target from ivshmem to native-linuxapp removed the error and
> it doesn't hang at creating external bridge anymore.
> All processes(nova-api, neutron, ovs-vswitchd, etc) did start.
>
> Thanks,
> Prathyusha
>
> On Tue, Nov 17, 2015 at 7:57 PM, Mooney, Sean K <sean.k.moo...@intel.com>
> wrote:
>
>> We mainly test with 2M hugepages not 1G however our ci does use 1G pages.
>>
>> We recently noticed a different but unrelated related issue with using
>> the ivshmem target when building dpdk.
>>
>> (https://bugs.launchpad.net/networking-ovs-dpdk/+bug/1517032)
>>
>>
>>
>> Instead of modifying dpdk can you try
>>
>> Changing the default dpdk build target to x86_64-native-linuxapp-gcc.
>>
>>
>>
>> This can be done by  adding
>>
>>
>>
>> RTE_TARGET=x86_64-native-linuxapp-gcc to the local.conf
>>
>> And removing the following file to force a rebuild
>> “/opt/stack/ovs/BUILD_COMPLETE”
>>
>>
>>
>> I agree with your assessment though this appears to be a timing issue in
>> dpdk 2.0
>>
>>
>>
>>
>>
>>
>>
>> *From:* Prathyusha Guduri [mailto:prathyushaconne...@gmail.com]
>> *Sent:* Tuesday, November 17, 2015 1:42 PM
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [networking-ovs-dpdk]
>>
>>
>>
>> Here is stack.sh log -
>>
>>
>> 2015-11-17 13:38:50.010 | Loading uio module
>> 2015-11-17 13:38:50.028 | Loading DPDK UIO module
>> 2015-11-17 13:38:50.038 | starting ovs db
>> 2015-11-17 13:38:50.038 | binding nics
>> 2015-11-17 13:38:50.039 | starting vswitchd
>> 2015-11-17 13:38:50.190 | sudo RTE_SDK=/opt/stack/DPDK-v2.0.0
>> RTE_TARGET=build /opt/stack/DPDK-v2.0.0/tools/dpdk_nic_bind.py -b igb_uio
>> :07:00.0
>> 2015-11-17 13:38:50.527 | sudo ovs-vsctl --no-wait --may-exist add-port
>> br-eth1 dpdk0 -- set Interface dpdk0 type=dpdk
>> 2015-11-17 13:38:51.671 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:38:52.685 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:38:53.702 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:38:54.720 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:38:55.733 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:38:56.749 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:38:57.768 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:38:58.787 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:38:59.802 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:39:00.818 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:39:01.836 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:39:02.849 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:39:03.866 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:39:04.884 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:39:05.905 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:39:06.923 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:39:07.937 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:39:08.956 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:39:09.973 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:39:10.988 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:39:12.004 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:39:13.022 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:39:14.040 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:39:15.060 | Waiting for ovs-vswitchd to start...
>> 2015-11-17 13:39:16.073 | Waiting for ov

Re: [openstack-dev] [networking-ovs-dpdk]

[Mooney, Sean K]

Hi that is great to know.
I will internally report this behavior to our dpdk team
But I have already got a patch to change our default target to native-linuxapp
https://review.openstack.org/#/c/246375/ which should merge shortly.
Im glad it is now working for you.

From: Prathyusha Guduri [mailto:prathyushaconne...@gmail.com]
Sent: Wednesday, November 18, 2015 6:13 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [networking-ovs-dpdk]

Thanks a lot Sean, that was helpful.
Changing the target from ivshmem to native-linuxapp removed the error and it 
doesn't hang at creating external bridge anymore.
All processes(nova-api, neutron, ovs-vswitchd, etc) did start.
Thanks,
Prathyusha

On Tue, Nov 17, 2015 at 7:57 PM, Mooney, Sean K 
<sean.k.moo...@intel.com<mailto:sean.k.moo...@intel.com>> wrote:
We mainly test with 2M hugepages not 1G however our ci does use 1G pages.
We recently noticed a different but unrelated related issue with using the 
ivshmem target when building dpdk.
(https://bugs.launchpad.net/networking-ovs-dpdk/+bug/1517032)

Instead of modifying dpdk can you try
Changing the default dpdk build target to x86_64-native-linuxapp-gcc.

This can be done by  adding

RTE_TARGET=x86_64-native-linuxapp-gcc to the local.conf
And removing the following file to force a rebuild 
“/opt/stack/ovs/BUILD_COMPLETE”

I agree with your assessment though this appears to be a timing issue in dpdk 
2.0



From: Prathyusha Guduri 
[mailto:prathyushaconne...@gmail.com<mailto:prathyushaconne...@gmail.com>]
Sent: Tuesday, November 17, 2015 1:42 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [networking-ovs-dpdk]

Here is stack.sh log -

2015-11-17 13:38:50.010 | Loading uio module
2015-11-17 13:38:50.028 | Loading DPDK UIO module
2015-11-17 13:38:50.038 | starting ovs db
2015-11-17 13:38:50.038 | binding nics
2015-11-17 13:38:50.039 | starting vswitchd
2015-11-17 13:38:50.190 | sudo RTE_SDK=/opt/stack/DPDK-v2.0.0 RTE_TARGET=build 
/opt/stack/DPDK-v2.0.0/tools/dpdk_nic_bind.py -b igb_uio :07:00.0
2015-11-17 13:38:50.527 | sudo ovs-vsctl --no-wait --may-exist add-port br-eth1 
dpdk0 -- set Interface dpdk0 type=dpdk
2015-11-17 13:38:51.671 | Waiting for ovs-vswitchd to start...
2015-11-17 13:38:52.685 | Waiting for ovs-vswitchd to start...
2015-11-17 13:38:53.702 | Waiting for ovs-vswitchd to start...
2015-11-17 13:38:54.720 | Waiting for ovs-vswitchd to start...
2015-11-17 13:38:55.733 | Waiting for ovs-vswitchd to start...
2015-11-17 13:38:56.749 | Waiting for ovs-vswitchd to start...
2015-11-17 13:38:57.768 | Waiting for ovs-vswitchd to start...
2015-11-17 13:38:58.787 | Waiting for ovs-vswitchd to start...
2015-11-17 13:38:59.802 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:00.818 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:01.836 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:02.849 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:03.866 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:04.884 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:05.905 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:06.923 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:07.937 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:08.956 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:09.973 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:10.988 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:12.004 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:13.022 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:14.040 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:15.060 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:16.073 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:17.089 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:18.108 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:19.121 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:20.138 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:21.156 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:22.169 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:23.185 | Waiting for ovs-vswitchd to start...

On Tue, Nov 17, 2015 at 6:50 PM, Prathyusha Guduri 
<prathyushaconne...@gmail.com<mailto:prathyushaconne...@gmail.com>> wrote:
Hi Sean,
Here is ovs-vswitchd.log

2015-11-13T12:48:01Z|1|dpdk|INFO|User-provided -vhost_sock_dir in use: 
/var/run/openvswitch
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Detected lcore 4 as core 4 on socket 0
EAL: Detected lcore 5 as core 5 on socket 0
EAL: Detected lcore 6 as core 0 on socket 0
EAL: Detected lcore 7 as core 1 on socket 0
EAL: Detected lcore 8 as core 2 on socket 0
EAL: Detected lcore 9 as core 3 on socket 0
EAL: Detected 

Re: [openstack-dev] [networking-ovs-dpdk]

[Prathyusha Guduri]

Hi James,

Thanks for the information. Will experiment on it and share my
observations.

Sean - I guess this timing issue is fixed in DPDK 2.1. Will try with that
and let you know. Anyway, thanks for the help

Regards,
Prathyusha

On Wed, Nov 18, 2015 at 6:00 PM, Mooney, Sean K <sean.k.moo...@intel.com>
wrote:

> Hi james
>
> Yes we are planning on testing the packaged release to see if it is
> compatible with our ml2 driver and the
>
> Changes we are submitting upstream. If it is we will add a use binary flag
> to our devstack plugin to skip the
>
> Compilation step and use that instead on 15.10 or 14.04
> cloud-archive:liberty
>
>
>
> As part of your packaging did ye fix pciutils to correctly report the
> unused drivers when an interface is bound
>
> The dpdk driver? Also does it support both igb_uio and/or vfio-pci drivers
> for dpdk interface?
>
>
>
> Anyway yes I hope to check it out and seeing what ye have done. When
> ovs-dpdk starts getting packaged in more operating systems
>
> We will probably swap our default to the binary install though we will
> keep the source install option as it allows us to work on new features
>
> Before they are packaged and to have better performance.
>
>
>
> Regards
>
> sean
>
>
>
>
>
> *From:* James Page [mailto:james.p...@ubuntu.com]
> *Sent:* Wednesday, November 18, 2015 11:55 AM
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [networking-ovs-dpdk]
>
>
>
> Hi All
>
>
>
> Reading through this thread I thought participants might be interested to
> know that Ubuntu now provides a DPDK enabled Open vSwitch package in Ubuntu
> 15.10 and for Ubuntu 14.04 using the Liberty UCA; you can use it as follows:
>
>
>
>sudo add-apt-repository cloud-archive:liberty  # not required for 15.10
>
>sudo apt-get update
>
>sudo apt-get install openvswitch-switch-dpdk
>
>sudo update-alternatives --set
> ovs-vswitchd /usr/lib/openvswitch-switch-dpdk/ovs-vswitchd-dpdk
>
>sudo service openvswitch-switch restart
>
>
>
> DPDK configuration is passed through OVS using
> /etc/default/openvswitch-switch (read for details).  The dpdk package also
> provides some basic configuration mechanisms for hugepages and binding
> networking adapters to userspace in /etc/dpdk.
>
>
>
> This is a first packaging release and is experimental - please do provide
> feedback on what you do and don't like about it...
>
>
>
> On Wed, Nov 18, 2015 at 6:12 AM, Prathyusha Guduri <
> prathyushaconne...@gmail.com> wrote:
>
> Thanks a lot Sean, that was helpful.
>
> Changing the target from ivshmem to native-linuxapp removed the error and
> it doesn't hang at creating external bridge anymore.
>
> All processes(nova-api, neutron, ovs-vswitchd, etc) did start.
>
> Thanks,
>
> Prathyusha
>
>
>
> On Tue, Nov 17, 2015 at 7:57 PM, Mooney, Sean K <sean.k.moo...@intel.com>
> wrote:
>
> We mainly test with 2M hugepages not 1G however our ci does use 1G pages.
>
> We recently noticed a different but unrelated related issue with using the
> ivshmem target when building dpdk.
>
> (https://bugs.launchpad.net/networking-ovs-dpdk/+bug/1517032)
>
>
>
> Instead of modifying dpdk can you try
>
> Changing the default dpdk build target to x86_64-native-linuxapp-gcc.
>
>
>
> This can be done by  adding
>
>
>
> RTE_TARGET=x86_64-native-linuxapp-gcc to the local.conf
>
> And removing the following file to force a rebuild
> “/opt/stack/ovs/BUILD_COMPLETE”
>
>
>
> I agree with your assessment though this appears to be a timing issue in
> dpdk 2.0
>
>
>
>
>
>
>
> *From:* Prathyusha Guduri [mailto:prathyushaconne...@gmail.com]
> *Sent:* Tuesday, November 17, 2015 1:42 PM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [networking-ovs-dpdk]
>
>
>
> Here is stack.sh log -
>
>
> 2015-11-17 13:38:50.010 | Loading uio module
> 2015-11-17 13:38:50.028 | Loading DPDK UIO module
> 2015-11-17 13:38:50.038 | starting ovs db
> 2015-11-17 13:38:50.038 | binding nics
> 2015-11-17 13:38:50.039 | starting vswitchd
> 2015-11-17 13:38:50.190 | sudo RTE_SDK=/opt/stack/DPDK-v2.0.0
> RTE_TARGET=build /opt/stack/DPDK-v2.0.0/tools/dpdk_nic_bind.py -b igb_uio
> :07:00.0
> 2015-11-17 13:38:50.527 | sudo ovs-vsctl --no-wait --may-exist add-port
> br-eth1 dpdk0 -- set Interface dpdk0 type=dpdk
> 2015-11-17 13:38:51.671 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:38:52.685 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:38:53.702 | Waiting f

Re: [openstack-dev] [networking-ovs-dpdk]

[James Page]

Hi Sean

On Wed, Nov 18, 2015 at 12:30 PM, Mooney, Sean K 
wrote:

> Hi james
>
> Yes we are planning on testing the packaged release to see if it is
> compatible with our ml2 driver and the
>
> Changes we are submitting upstream. If it is we will add a use binary flag
> to our devstack plugin to skip the
>
> Compilation step and use that instead on 15.10 or 14.04
> cloud-archive:liberty
>

Excellent.


> As part of your packaging did ye fix pciutils to correctly report the
> unused drivers when an interface is bound
>
> The dpdk driver? Also does it support both igb_uio and/or vfio-pci drivers
> for dpdk interface?
>

Re pcituils, we've not done any work in that area - can you give an example
of what you would expect?

The dpdk package supports both driver types in /etc/dpdk/interfaces - when
you declare an adapter for use, you get to specify the module you want to
use as well; we're relying the in-tree kernel drivers (uio-pci-generic and
vfio-pci) right now.


>
>
> Anyway yes I hope to check it out and seeing what ye have done. When
> ovs-dpdk starts getting packaged in more operating systems
>
> We will probably swap our default to the binary install though we will
> keep the source install option as it allows us to work on new features
>
> Before they are packaged and to have better performance.
>

That sounds sensible; re 'better performance' - yeah we do have to baseline
the optimizations at compile time right now (ssse3 only right now) , but I
really hope that does change so that we can move to a runtime CPU feature
detection model, allowing the best possible performance through the
packages we have in Ubuntu (or any other distribution for that matter).
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk]

[Mooney, Sean K]

Can you provide the ovs-vswitchd log form ${OVS_LOG_DIR}/ovs-vswitchd.log
/tmp/ovs-vswitchd.log in your case.

If the vswitch fails to start we clean up by unmounting the hugepages.



From: Prathyusha Guduri [mailto:prathyushaconne...@gmail.com]
Sent: Tuesday, November 17, 2015 7:37 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [networking-ovs-dpdk]

Hi Sean,
I realised on debugging ovs-dpdk-init script that the main issue is with the 
following command

$ screen -dms ovs-vswitchd sudo sg $qemu_group -c "umask 002; 
${OVS_INSTALL_DIR}/sbin/ovs-vswitchd --dpdk -vhost_sock_dir $OVS_DB_SOCKET_DIR 
-c $OVS_CORE_MASK -n $OVS_MEM_CHANNELS  --proc-type primary  --huge-dir 
$OVS_HUGEPAGE_MOUNT --socket-mem $OVS_SOCKET_MEM $pciAddressWhitelist -- 
unix:$OVS_DB_SOCKET 2>&1 | tee ${OVS_LOG_DIR}/ovs-vswitchd.log"

which I guess is starting the ovs-vswitchd application. Before this command, 
huge pages is mounted and port binding is also done but still the screen 
command fails.
I verified the db.sock and conf.db files.
Any help is highly appreciated.
Thanks,
Prathyusha


On Mon, Nov 16, 2015 at 5:12 PM, Prathyusha Guduri 
<prathyushaconne...@gmail.com<mailto:prathyushaconne...@gmail.com>> wrote:
Hi Sean,
Thanks for your response.
in your case though you are using 1GB hugepages so I don’t think this is 
related to memory fragmentation
or a lack of free hugepages.

to use preallocated 1GB page with ovs you should instead set the following in 
your local.conf

OVS_HUGEPAGE_MOUNT_PAGESIZE=1G
OVS_ALLOCATE_HUGEPAGES=False

Added the above two parameters to the local.conf. The same problem again.
Basically it throws this error -
2015-11-16 11:31:44.741 | starting vswitchd
2015-11-16 11:31:44.863 | sudo RTE_SDK=/opt/stack/DPDK-v2.0.0 RTE_TARGET=build 
/opt/stack/DPDK-v2.0.0/tools/dpdk_nic_bind.py -b igb_uio :07:00.0
2015-11-16 11:31:45.169 | sudo ovs-vsctl --no-wait --may-exist add-port br-eth1 
dpdk0 -- set Interface dpdk0 type=dpdk
2015-11-16 11:31:46.314 | Waiting for ovs-vswitchd to start...
2015-11-16 11:31:47.442 | libvirt-bin stop/waiting
2015-11-16 11:31:49.473 | libvirt-bin start/running, process 2255
2015-11-16 11:31:49.477 | [ERROR] /etc/init.d/ovs-dpdk:563 ovs-vswitchd 
application failed to start

manually mounting /mnt/huge and then commenting that part from the 
/etc/init.d/ovs-dpdk script also throws the same error.
Using 1G hugepagesize should not give any memory related problem. I dont 
understand why it is not mounting then.
Here is the /opt/stack/networking-ovs-dpdk/devstack/ovs-dpdk/ovs-dpdk.conf

RTE_SDK=${RTE_SDK:-/opt/stack/DPDK}
RTE_TARGET=${RTE_TARGET:-x86_64-ivshmem-linuxapp-gcc}

OVS_INSTALL_DIR=/usr
OVS_DB_CONF_DIR=/etc/openvswitch
OVS_DB_SOCKET_DIR=/var/run/openvswitch
OVS_DB_CONF=$OVS_DB_CONF_DIR/conf.db
OVS_DB_SOCKET=OVS_DB_SOCKET_DIR/db.sock

OVS_SOCKET_MEM=2048,2048
OVS_MEM_CHANNELS=4
OVS_CORE_MASK=${OVS_CORE_MASK:-2}
OVS_PMD_CORE_MASK=${OVS_PMD_CORE_MASK:-4}
OVS_LOG_DIR=/tmp
OVS_LOCK_DIR=''
OVS_SRC_DIR=/opt/stack/ovs
OVS_DIR=${OVS_DIR:-${OVS_SRC_DIR}}
OVS_UTILS=${OVS_DIR}/utilities/
OVS_DB_UTILS=${OVS_DIR}/ovsdb/
OVS_DPDK_DIR=$RTE_SDK
OVS_NUM_HUGEPAGES=${OVS_NUM_HUGEPAGES:-5}
OVS_HUGEPAGE_MOUNT=${OVS_HUGEPAGE_MOUNT:-/mnt/huge}
OVS_HUGEPAGE_MOUNT_PAGESIZE=''
OVS_BOND_MODE=$OVS_BOND_MODE
OVS_BOND_PORTS=$OVS_BOND_PORTS
OVS_BRIDGE_MAPPINGS=eth1
OVS_PCI_MAPPINGS=:07:00.0#eth1
OVS_DPDK_PORT_MAPPINGS=''
OVS_TUNNEL_CIDR_MAPPING=''
OVS_ALLOCATE_HUGEPAGES=True
OVS_INTERFACE_DRIVER='igb_uio'
Verified the OVS_DB_SOCKET_DIR and all others. conf.db and db.sock exist. So 
why ovs-vswitchd is failing to start??? Am I missing something???


Thanks,
Prathyusha


On Mon, Nov 16, 2015 at 4:39 PM, Mooney, Sean K 
<sean.k.moo...@intel.com<mailto:sean.k.moo...@intel.com>> wrote:

Hi

Yes sorry for the delay in responding to you and samta.

In your case assuming you are using 2mb hugepages it is easy to hit dpdks 
default max memory segments

This can be changed by setting OVS_DPDK_MEM_SEGMENTS=
In the local.conf and recompiling. To do this simply remove the build complete 
file in /opt/stack/ovs
rm –f /opt/stack/BUILD_COMPLETE

in your case though you are using 1GB hugepages so I don’t think this is 
related to memory fragmentation
or a lack of free hugepages.

to use preallocated 1GB page with ovs you should instead set the following in 
your local.conf

OVS_HUGEPAGE_MOUNT_PAGESIZE=1G
OVS_ALLOCATE_HUGEPAGES=False

Regards
sean

From: Prathyusha Guduri 
[mailto:prathyushaconne...@gmail.com<mailto:prathyushaconne...@gmail.com>]
Sent: Monday, November 16, 2015 6:20 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [networking-ovs-dpdk]

Hi all,

I have a similar problem as Samta. Am also stuck at the same place. The 
following command

$sudo ovs-vsctl br-set-external-id br-ex bridge-id br-ex

hangs forever. As Sean said, it might be because of ovs-vswitchd proces.

Re: [openstack-dev] [networking-ovs-dpdk]

[Prathyusha Guduri]

3.287 | Zone 0: name:,
> phys:0x9b60, len:0xb0, virt:0x7fca8ea0, socket_id:0, flags:0
> 2015-11-17 11:26:53.287 | Zone 1: name:,
> phys:0x3660, len:0x2080, virt:0x7fcab360, socket_id:0, flags:0
> 2015-11-17 11:26:53.287 | Zone 2: name:, phys:0x9c10,
> len:0x28a0c0, virt:0x7fca8f50, socket_id:0, flags:0
> 2015-11-17 11:26:53.287 | Zone 3: name:,
> phys:0x36602080, len:0x1f400, virt:0x7fcab3602080, socket_id:0, flags:0
> 2015-11-17 11:26:53.287 | PMD: eth_em_tx_queue_setup():
> sw_ring=0x7fca8f4efd40 hw_ring=0x7fcab3621480 dma_addr=0x36621480
> 2015-11-17 11:26:53.287 | PMD: eth_em_rx_queue_setup():
> sw_ring=0x7fca8f4ebc40 hw_ring=0x7fcab3631480 dma_addr=0x36631480
> 2015-11-17 11:26:53.368 | PMD: eth_em_start(): <<
> 2015-11-17 11:26:53.368 | 2015-11-17T11:26:53Z|00012|dpdk|INFO|Port 0:
> 68:05:ca:1b:ca:c9
> 2015-11-17 11:26:53.405 | PMD: eth_em_tx_queue_setup():
> sw_ring=0x7fca8f4efe00 hw_ring=0x7fcab3621480 dma_addr=0x36621480
> 2015-11-17 11:26:53.405 | PMD: eth_em_rx_queue_setup():
> sw_ring=0x7fca8f4ebdc0 hw_ring=0x7fcab3631480 dma_addr=0x36631480
> 2015-11-17 11:26:53.486 | PMD: eth_em_start(): <<
> 2015-11-17 11:26:53.486 | 2015-11-17T11:26:53Z|00013|dpdk|INFO|Port 0:
> 68:05:ca:1b:ca:c9
> 2015-11-17 11:26:53.487 |
> 2015-11-17T11:26:53Z|00014|dpif_netdev|INFO|Created 1 pmd threads on numa
> node 0
> 2015-11-17 11:26:53.487 |
> 2015-11-17T11:26:53Z|1|dpif_netdev(pmd10)|INFO|Core 0 processing port
> 'dpdk0'
> 2015-11-17 11:26:53.488 |
> 2015-11-17T11:26:53Z|2|dpif_netdev(pmd10)|INFO|Core 0 processing port
> 'dpdk0'
> 2015-11-17 11:26:53.488 | 2015-11-17T11:26:53Z|00015|bridge|INFO|bridge
> br-eth1: added interface dpdk0 on port 1
> 2015-11-17 11:26:53.488 | 2015-11-17T11:26:53Z|00016|bridge|INFO|bridge
> br-int: added interface br-int on port 65534
> 2015-11-17 11:26:53.488 | 2015-11-17T11:26:53Z|00017|bridge|INFO|bridge
> br-eth1: using datapath ID 6805ca1bcac9
> 2015-11-17 11:26:53.488 | 2015-11-17T11:26:53Z|00018|connmgr|INFO|br-eth1:
> added service controller "punix:/var/run/openvswitch/br-eth1.mgmt"
> 2015-11-17 11:26:53.489 | 2015-11-17T11:26:53Z|00019|bridge|INFO|bridge
> br-int: using datapath ID 2ef7b66a8742
> 2015-11-17 11:26:53.489 | 2015-11-17T11:26:53Z|00020|connmgr|INFO|br-int:
> added service controller "punix:/var/run/openvswitch/br-int.mgmt"
> 2015-11-17 11:26:53.490 |
> 2015-11-17T11:26:53Z|00021|dpif_netdev|INFO|Created 2 pmd threads on numa
> node 0
> 2015-11-17 11:26:53.492 |
> 2015-11-17T11:26:53Z|00022|bridge|INFO|ovs-vswitchd (Open vSwitch) 2.4.90
> 2015-11-17 11:26:53.493 |
> 2015-11-17T11:26:53Z|1|dpif_netdev(pmd23)|INFO|Core 2 processing port
> 'dpdk0'
> 2015-11-17 11:27:03.494 | 2015-11-17T11:27:03Z|00023|memory|INFO|peak
> resident set size grew 93% in last 10.3 seconds, from 10680 kB to 20572 kB
> 2015-11-17 11:27:03.494 |
> 2015-11-17T11:27:03Z|00024|memory|INFO|handlers:4 ports:3 revalidators:2
> rules:10
>
> ubuntu@ubuntu-Precision-Tower-5810:/opt/stack/DPDK-v2.0.0/lib/librte_eal/linuxapp/eal$
> ps -Al | grep ovs
> 5 S 0  1681  2595  0  80   0 -  4433 poll_s ?00:00:00
> ovsdb-server
> 4 S 0  1716  1715  0  80   0 -  4636 wait   pts/300:00:00 ovs-dpdk
> 4 S 0  2124  1716 99  80   0 - 870841 poll_s pts/3   03:42:31
> ovs-vswitchd
>
> So now ovs-vswitchd runs unlike the last time.
>  I really dont understand where am missing out
>
> On Tue, Nov 17, 2015 at 5:14 PM, Mooney, Sean K <sean.k.moo...@intel.com>
> wrote:
>
>> Can you provide the ovs-vswitchd log form ${OVS_LOG_DIR}/ovs-vswitchd.log
>>
>> /tmp/ovs-vswitchd.log in your case.
>>
>>
>>
>> If the vswitch fails to start we clean up by unmounting the hugepages.
>>
>>
>>
>>
>> *From:* Prathyusha Guduri [mailto:prathyushaconne...@gmail.com]
>> *Sent:* Tuesday, November 17, 2015 7:37 AM
>>
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [networking-ovs-dpdk]
>>
>>
>>
>> Hi Sean,
>>
>> I realised on debugging ovs-dpdk-init script that the main issue is with
>> the following command
>>
>> $ screen -dms ovs-vswitchd sudo sg $qemu_group -c "umask 002;
>> ${OVS_INSTALL_DIR}/sbin/ovs-vswitchd --dpdk -vhost_sock_dir
>> $OVS_DB_SOCKET_DIR -c $OVS_CORE_MASK -n $OVS_MEM_CHANNELS  --proc-type
>> primary  --huge-dir $OVS_HUGEPAGE_MOUNT --socket-mem $OVS_SOCKET_MEM
>> $pciAddressWhitelist -- unix:$OVS_DB_SOCKET 2>&1 | tee
>> ${OVS_LOG_DIR}/ovs-vswitchd.log"
>>
>> which I guess is starting the ovs-vswitchd application. Before this
>> command, huge pages is 

Re: [openstack-dev] [networking-ovs-dpdk]

[Prathyusha Guduri]

 2015 at 5:14 PM, Mooney, Sean K <sean.k.moo...@intel.com>
wrote:

> Can you provide the ovs-vswitchd log form ${OVS_LOG_DIR}/ovs-vswitchd.log
>
> /tmp/ovs-vswitchd.log in your case.
>
>
>
> If the vswitch fails to start we clean up by unmounting the hugepages.
>
>
>
>
> *From:* Prathyusha Guduri [mailto:prathyushaconne...@gmail.com]
> *Sent:* Tuesday, November 17, 2015 7:37 AM
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [networking-ovs-dpdk]
>
>
>
> Hi Sean,
>
> I realised on debugging ovs-dpdk-init script that the main issue is with
> the following command
>
> $ screen -dms ovs-vswitchd sudo sg $qemu_group -c "umask 002;
> ${OVS_INSTALL_DIR}/sbin/ovs-vswitchd --dpdk -vhost_sock_dir
> $OVS_DB_SOCKET_DIR -c $OVS_CORE_MASK -n $OVS_MEM_CHANNELS  --proc-type
> primary  --huge-dir $OVS_HUGEPAGE_MOUNT --socket-mem $OVS_SOCKET_MEM
> $pciAddressWhitelist -- unix:$OVS_DB_SOCKET 2>&1 | tee
> ${OVS_LOG_DIR}/ovs-vswitchd.log"
>
> which I guess is starting the ovs-vswitchd application. Before this
> command, huge pages is mounted and port binding is also done but still the
> screen command fails.
> I verified the db.sock and conf.db files.
>
> Any help is highly appreciated.
>
> Thanks,
>
> Prathyusha
>
>
>
>
>
> On Mon, Nov 16, 2015 at 5:12 PM, Prathyusha Guduri <
> prathyushaconne...@gmail.com> wrote:
>
> Hi Sean,
>
> Thanks for your response.
>
> in your case though you are using 1GB hugepages so I don’t think this is
> related to memory fragmentation
> or a lack of free hugepages.
>
>
>
> to use preallocated 1GB page with ovs you should instead set the following
> in your local.conf
>
>
>
> OVS_HUGEPAGE_MOUNT_PAGESIZE=1G
>
> OVS_ALLOCATE_HUGEPAGES=False
>
> Added the above two parameters to the local.conf. The same problem again.
>
> Basically it throws this error -
> 2015-11-16 11:31:44.741 | starting vswitchd
> 2015-11-16 11:31:44.863 | sudo RTE_SDK=/opt/stack/DPDK-v2.0.0
> RTE_TARGET=build /opt/stack/DPDK-v2.0.0/tools/dpdk_nic_bind.py -b igb_uio
> :07:00.0
> 2015-11-16 11:31:45.169 | sudo ovs-vsctl --no-wait --may-exist add-port
> br-eth1 dpdk0 -- set Interface dpdk0 type=dpdk
> 2015-11-16 11:31:46.314 | Waiting for ovs-vswitchd to start...
> 2015-11-16 11:31:47.442 | libvirt-bin stop/waiting
> 2015-11-16 11:31:49.473 | libvirt-bin start/running, process 2255
> 2015-11-16 11:31:49.477 | [ERROR] /etc/init.d/ovs-dpdk:563 ovs-vswitchd
> application failed to start
>
> manually mounting /mnt/huge and then commenting that part from the
> /etc/init.d/ovs-dpdk script also throws the same error.
>
> Using 1G hugepagesize should not give any memory related problem. I dont
> understand why it is not mounting then.
>
> Here is the /opt/stack/networking-ovs-dpdk/devstack/ovs-dpdk/ovs-dpdk.conf
>
> RTE_SDK=${RTE_SDK:-/opt/stack/DPDK}
> RTE_TARGET=${RTE_TARGET:-x86_64-ivshmem-linuxapp-gcc}
>
> OVS_INSTALL_DIR=/usr
> OVS_DB_CONF_DIR=/etc/openvswitch
> OVS_DB_SOCKET_DIR=/var/run/openvswitch
> OVS_DB_CONF=$OVS_DB_CONF_DIR/conf.db
> OVS_DB_SOCKET=OVS_DB_SOCKET_DIR/db.sock
>
> OVS_SOCKET_MEM=2048,2048
> OVS_MEM_CHANNELS=4
> OVS_CORE_MASK=${OVS_CORE_MASK:-2}
> OVS_PMD_CORE_MASK=${OVS_PMD_CORE_MASK:-4}
> OVS_LOG_DIR=/tmp
> OVS_LOCK_DIR=''
> OVS_SRC_DIR=/opt/stack/ovs
> OVS_DIR=${OVS_DIR:-${OVS_SRC_DIR}}
> OVS_UTILS=${OVS_DIR}/utilities/
> OVS_DB_UTILS=${OVS_DIR}/ovsdb/
> OVS_DPDK_DIR=$RTE_SDK
> OVS_NUM_HUGEPAGES=${OVS_NUM_HUGEPAGES:-5}
> OVS_HUGEPAGE_MOUNT=${OVS_HUGEPAGE_MOUNT:-/mnt/huge}
> OVS_HUGEPAGE_MOUNT_PAGESIZE=''
> OVS_BOND_MODE=$OVS_BOND_MODE
> OVS_BOND_PORTS=$OVS_BOND_PORTS
> OVS_BRIDGE_MAPPINGS=eth1
> OVS_PCI_MAPPINGS=:07:00.0#eth1
> OVS_DPDK_PORT_MAPPINGS=''
> OVS_TUNNEL_CIDR_MAPPING=''
> OVS_ALLOCATE_HUGEPAGES=True
> OVS_INTERFACE_DRIVER='igb_uio'
>
> Verified the OVS_DB_SOCKET_DIR and all others. conf.db and db.sock exist.
> So why ovs-vswitchd is failing to start??? Am I missing something???
>
>
>
>
>
> Thanks,
>
> Prathyusha
>
>
>
>
>
> On Mon, Nov 16, 2015 at 4:39 PM, Mooney, Sean K <sean.k.moo...@intel.com>
> wrote:
>
>
>
> Hi
>
>
>
> Yes sorry for the delay in responding to you and samta.
>
>
>
> In your case assuming you are using 2mb hugepages it is easy to hit dpdks
> default max memory segments
>
>
>
> This can be changed by setting OVS_DPDK_MEM_SEGMENTS= number that you will never hit>
>
> In the local.conf and recompiling. To do this simply remove the build
> complete file in /opt/stack/ovs
>
> rm –f /opt/stack/BUILD_COMPLETE
>
&g

Re: [openstack-dev] [networking-ovs-dpdk]

[Mooney, Sean K]

We mainly test with 2M hugepages not 1G however our ci does use 1G pages.
We recently noticed a different but unrelated related issue with using the 
ivshmem target when building dpdk.
(https://bugs.launchpad.net/networking-ovs-dpdk/+bug/1517032)

Instead of modifying dpdk can you try
Changing the default dpdk build target to x86_64-native-linuxapp-gcc.

This can be done by  adding

RTE_TARGET=x86_64-native-linuxapp-gcc to the local.conf
And removing the following file to force a rebuild 
“/opt/stack/ovs/BUILD_COMPLETE”

I agree with your assessment though this appears to be a timing issue in dpdk 
2.0



From: Prathyusha Guduri [mailto:prathyushaconne...@gmail.com]
Sent: Tuesday, November 17, 2015 1:42 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [networking-ovs-dpdk]

Here is stack.sh log -

2015-11-17 13:38:50.010 | Loading uio module
2015-11-17 13:38:50.028 | Loading DPDK UIO module
2015-11-17 13:38:50.038 | starting ovs db
2015-11-17 13:38:50.038 | binding nics
2015-11-17 13:38:50.039 | starting vswitchd
2015-11-17 13:38:50.190 | sudo RTE_SDK=/opt/stack/DPDK-v2.0.0 RTE_TARGET=build 
/opt/stack/DPDK-v2.0.0/tools/dpdk_nic_bind.py -b igb_uio :07:00.0
2015-11-17 13:38:50.527 | sudo ovs-vsctl --no-wait --may-exist add-port br-eth1 
dpdk0 -- set Interface dpdk0 type=dpdk
2015-11-17 13:38:51.671 | Waiting for ovs-vswitchd to start...
2015-11-17 13:38:52.685 | Waiting for ovs-vswitchd to start...
2015-11-17 13:38:53.702 | Waiting for ovs-vswitchd to start...
2015-11-17 13:38:54.720 | Waiting for ovs-vswitchd to start...
2015-11-17 13:38:55.733 | Waiting for ovs-vswitchd to start...
2015-11-17 13:38:56.749 | Waiting for ovs-vswitchd to start...
2015-11-17 13:38:57.768 | Waiting for ovs-vswitchd to start...
2015-11-17 13:38:58.787 | Waiting for ovs-vswitchd to start...
2015-11-17 13:38:59.802 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:00.818 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:01.836 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:02.849 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:03.866 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:04.884 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:05.905 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:06.923 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:07.937 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:08.956 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:09.973 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:10.988 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:12.004 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:13.022 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:14.040 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:15.060 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:16.073 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:17.089 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:18.108 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:19.121 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:20.138 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:21.156 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:22.169 | Waiting for ovs-vswitchd to start...
2015-11-17 13:39:23.185 | Waiting for ovs-vswitchd to start...


On Tue, Nov 17, 2015 at 6:50 PM, Prathyusha Guduri 
<prathyushaconne...@gmail.com<mailto:prathyushaconne...@gmail.com>> wrote:
Hi Sean,
Here is ovs-vswitchd.log

2015-11-13T12:48:01Z|1|dpdk|INFO|User-provided -vhost_sock_dir in use: 
/var/run/openvswitch
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Detected lcore 4 as core 4 on socket 0
EAL: Detected lcore 5 as core 5 on socket 0
EAL: Detected lcore 6 as core 0 on socket 0
EAL: Detected lcore 7 as core 1 on socket 0
EAL: Detected lcore 8 as core 2 on socket 0
EAL: Detected lcore 9 as core 3 on socket 0
EAL: Detected lcore 10 as core 4 on socket 0
EAL: Detected lcore 11 as core 5 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 12 lcore(s)
EAL: VFIO modules not all loaded, skip VFIO support...
EAL: Searching for IVSHMEM devices...
EAL: No IVSHMEM configuration found!
EAL: Setting up memory...
EAL: Ask a virtual area of 0x18000 bytes
EAL: Virtual area found at 0x7f1e (size = 0x18000)
EAL: remap_all_hugepages(): mmap failed: Cannot allocate memory
EAL: Failed to remap 1024 MB pages
PANIC in rte_eal_init():
Cannot init memory
7: [/usr/sbin/ovs-vswitchd() [0x40b803]]
6: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f1fb52d3ec5]]
5: [/usr/sbin/ovs-vswitchd() [0x40a822]]
4: [/usr/sbin/ovs-vswitchd() [0x675432]]
3: [/usr/sbin/ovs-vswitchd() [0x442155]]
2: [/usr/sbin/ovs-vswitchd() [0x407c9f]]
1: [/usr/sbin/ovs-vswitchd() [0x447828]]
Before this hu

Re: [openstack-dev] [networking-ovs-dpdk]

[Prathyusha Guduri]

Thanks a lot Sean, that was helpful.

Changing the target from ivshmem to native-linuxapp removed the error and
it doesn't hang at creating external bridge anymore.
All processes(nova-api, neutron, ovs-vswitchd, etc) did start.

Thanks,
Prathyusha

On Tue, Nov 17, 2015 at 7:57 PM, Mooney, Sean K <sean.k.moo...@intel.com>
wrote:

> We mainly test with 2M hugepages not 1G however our ci does use 1G pages.
>
> We recently noticed a different but unrelated related issue with using the
> ivshmem target when building dpdk.
>
> (https://bugs.launchpad.net/networking-ovs-dpdk/+bug/1517032)
>
>
>
> Instead of modifying dpdk can you try
>
> Changing the default dpdk build target to x86_64-native-linuxapp-gcc.
>
>
>
> This can be done by  adding
>
>
>
> RTE_TARGET=x86_64-native-linuxapp-gcc to the local.conf
>
> And removing the following file to force a rebuild
> “/opt/stack/ovs/BUILD_COMPLETE”
>
>
>
> I agree with your assessment though this appears to be a timing issue in
> dpdk 2.0
>
>
>
>
>
>
>
> *From:* Prathyusha Guduri [mailto:prathyushaconne...@gmail.com]
> *Sent:* Tuesday, November 17, 2015 1:42 PM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [networking-ovs-dpdk]
>
>
>
> Here is stack.sh log -
>
>
> 2015-11-17 13:38:50.010 | Loading uio module
> 2015-11-17 13:38:50.028 | Loading DPDK UIO module
> 2015-11-17 13:38:50.038 | starting ovs db
> 2015-11-17 13:38:50.038 | binding nics
> 2015-11-17 13:38:50.039 | starting vswitchd
> 2015-11-17 13:38:50.190 | sudo RTE_SDK=/opt/stack/DPDK-v2.0.0
> RTE_TARGET=build /opt/stack/DPDK-v2.0.0/tools/dpdk_nic_bind.py -b igb_uio
> :07:00.0
> 2015-11-17 13:38:50.527 | sudo ovs-vsctl --no-wait --may-exist add-port
> br-eth1 dpdk0 -- set Interface dpdk0 type=dpdk
> 2015-11-17 13:38:51.671 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:38:52.685 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:38:53.702 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:38:54.720 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:38:55.733 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:38:56.749 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:38:57.768 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:38:58.787 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:38:59.802 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:00.818 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:01.836 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:02.849 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:03.866 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:04.884 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:05.905 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:06.923 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:07.937 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:08.956 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:09.973 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:10.988 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:12.004 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:13.022 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:14.040 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:15.060 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:16.073 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:17.089 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:18.108 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:19.121 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:20.138 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:21.156 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:22.169 | Waiting for ovs-vswitchd to start...
> 2015-11-17 13:39:23.185 | Waiting for ovs-vswitchd to start...
>
>
>
> On Tue, Nov 17, 2015 at 6:50 PM, Prathyusha Guduri <
> prathyushaconne...@gmail.com> wrote:
>
> Hi Sean,
>
> Here is ovs-vswitchd.log
>
>
> 2015-11-13T12:48:01Z|1|dpdk|INFO|User-provided -vhost_sock_dir in use:
> /var/run/openvswitch
> EAL: Detected lcore 0 as core 0 on socket 0
> EAL: Detected lcore 1 as core 1 on socket 0
> EAL: Detected lcore 2 as core 2 on socket 0
> EAL: Detected lcore 3 as core 3 on socket 0
> EAL: Detected lcore 4 as core 4 on socket 0
> EAL: Detected lcore 5 as core 5 on socket 0
> EAL: Detected lcore 6 as core 0 on socket 0
> EAL: Detected lcore 7 as core 1 on socket 0
> EAL: Detected lcore 8 as core 2 on socket 0
> EAL: Detected lcore 9 as core 3 on socket 0
> EAL: Detected lcore 10 as core 4 on socket 0
> EAL: Detected lcore 11

Re: [openstack-dev] [networking-ovs-dpdk] ovs-appctl doesn't function correctly

[Hui Xiang]

That is helpful, thanks Sean !

On Mon, Nov 16, 2015 at 7:12 PM, Mooney, Sean K <sean.k.moo...@intel.com>
wrote:

> To use the ovs-appctl application you have to specify the socket path to
> the ovs-vswitchd process.
>
> ovs-appctl -t /var/run/openvswitch/ list-commands
>
> e.g.
>
> ovs-appctl -t /var/run/openvswitch/ovs-vswitchd.10110.ctl list-commands
>
>
>
>
>
>
>
> *From:* Hui Xiang [mailto:hui.xi...@canonical.com]
> *Sent:* Monday, November 16, 2015 10:01 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* [openstack-dev] [networking-ovs-dpdk] ovs-appctl doesn't
> function correctly
>
>
>
> Hi all,
>
>
>
>   I have managed to setup ovs-dpdk on Ubuntu, commands
> 'ovs-vsctl/ovs-ofctl' all work well excep 'ovs-appctl', could anyone help
> me to figure it out? Thanks in advance.
>
>
>
>
>
> xianghui@xianghui:~$ sudo ovs-ofctl show br-int
>
> OFPT_FEATURES_REPLY (xid=0x2): dpid:264fa4e1f24f
>
> n_tables:254, n_buffers:256
>
> capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
>
> actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan mod_dl_src
> mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src mod_tp_dst
>
>  1(int-br-eth1): addr:2e:23:93:7f:54:14
>
>  config: 0
>
>  state:  0
>
>  speed: 0 Mbps now, 0 Mbps max
>
>  2(tap7a2317aa-90): addr:0c:52:ff:7f:00:00
>
>  config: PORT_DOWN
>
>  state:  LINK_DOWN
>
>  speed: 0 Mbps now, 0 Mbps max
>
>  12(vhu5392206b-dc): addr:00:00:00:00:00:00
>
>  config: PORT_DOWN
>
>  state:  LINK_DOWN
>
>  speed: 0 Mbps now, 0 Mbps max
>
>  LOCAL(br-int): addr:26:4f:a4:e1:f2:4f
>
>  config: PORT_DOWN
>
>  state:  LINK_DOWN
>
>  current:10MB-FD COPPER
>
>  speed: 10 Mbps now, 0 Mbps max
>
> OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0
>
>
>
> xianghui@xianghui:~$ sudo ovs-appctl vlog/set dbg
>
> 2015-11-16T09:50:28Z|1|daemon_unix|WARN|/var/run/openvswitch/ovs-vswitchd.pid:
> open: No such file or directory
>
> ovs-appctl: cannot read pidfile "/var/run/openvswitch/ovs-vswitchd.pid"
> (No such file or directory)
>
>
>
> Also tried as below, failed as well.
>
>
>
> xianghui@xianghui:~$ sudo ovs-appctl -t /opt/stack/logs/ovs-vswitchd.pid
> vlog/set dbg
>
> 2015-11-16T09:58:15Z|1|unixctl|WARN|failed to connect to
> /opt/stack/logs/ovs-vswitchd.pid
>
> ovs-appctl: cannot connect to "/opt/stack/logs/ovs-vswitchd.pid"
> (Connection refused)
>
> xianghui@xianghui:~$ sudo ovs-appctl -t /var/run/openvswitch/db.sock
> vlog/set dbg
>
> unknown methodovs-appctl: /var/run/openvswitch/db.sock: server returned an
> error
>
>
>
>
>
>
>
> --
>
> Best Regards.
>
> Hui.
>
>
>
> OpenStack Engineer
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Best Regards.
Hui.

OpenStack Engineer
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk]

[Prathyusha Guduri]

Hi Sean,

Thanks for your response.

in your case though you are using 1GB hugepages so I don’t think this is
related to memory fragmentation
or a lack of free hugepages.



to use preallocated 1GB page with ovs you should instead set the following
in your local.conf



OVS_HUGEPAGE_MOUNT_PAGESIZE=1G
OVS_ALLOCATE_HUGEPAGES=False


Added the above two parameters to the local.conf. The same problem again.
Basically it throws this error -
2015-11-16 11:31:44.741 | starting vswitchd
2015-11-16 11:31:44.863 | sudo RTE_SDK=/opt/stack/DPDK-v2.0.0
RTE_TARGET=build /opt/stack/DPDK-v2.0.0/tools/dpdk_nic_bind.py -b igb_uio
:07:00.0
2015-11-16 11:31:45.169 | sudo ovs-vsctl --no-wait --may-exist add-port
br-eth1 dpdk0 -- set Interface dpdk0 type=dpdk
2015-11-16 11:31:46.314 | Waiting for ovs-vswitchd to start...
2015-11-16 11:31:47.442 | libvirt-bin stop/waiting
2015-11-16 11:31:49.473 | libvirt-bin start/running, process 2255
2015-11-16 11:31:49.477 | [ERROR] /etc/init.d/ovs-dpdk:563 ovs-vswitchd
application failed to start


manually mounting /mnt/huge and then commenting that part from the
/etc/init.d/ovs-dpdk script also throws the same error.

Using 1G hugepagesize should not give any memory related problem. I dont
understand why it is not mounting then.
Here is the /opt/stack/networking-ovs-dpdk/devstack/ovs-dpdk/ovs-dpdk.conf

RTE_SDK=${RTE_SDK:-/opt/stack/DPDK}
RTE_TARGET=${RTE_TARGET:-x86_64-ivshmem-linuxapp-gcc}

OVS_INSTALL_DIR=/usr
OVS_DB_CONF_DIR=/etc/openvswitch
OVS_DB_SOCKET_DIR=/var/run/openvswitch
OVS_DB_CONF=$OVS_DB_CONF_DIR/conf.db
OVS_DB_SOCKET=OVS_DB_SOCKET_DIR/db.sock

OVS_SOCKET_MEM=2048,2048
OVS_MEM_CHANNELS=4
OVS_CORE_MASK=${OVS_CORE_MASK:-2}
OVS_PMD_CORE_MASK=${OVS_PMD_CORE_MASK:-4}
OVS_LOG_DIR=/tmp
OVS_LOCK_DIR=''
OVS_SRC_DIR=/opt/stack/ovs
OVS_DIR=${OVS_DIR:-${OVS_SRC_DIR}}
OVS_UTILS=${OVS_DIR}/utilities/
OVS_DB_UTILS=${OVS_DIR}/ovsdb/
OVS_DPDK_DIR=$RTE_SDK
OVS_NUM_HUGEPAGES=${OVS_NUM_HUGEPAGES:-5}
OVS_HUGEPAGE_MOUNT=${OVS_HUGEPAGE_MOUNT:-/mnt/huge}
OVS_HUGEPAGE_MOUNT_PAGESIZE=''
OVS_BOND_MODE=$OVS_BOND_MODE
OVS_BOND_PORTS=$OVS_BOND_PORTS
OVS_BRIDGE_MAPPINGS=eth1
OVS_PCI_MAPPINGS=:07:00.0#eth1
OVS_DPDK_PORT_MAPPINGS=''
OVS_TUNNEL_CIDR_MAPPING=''
OVS_ALLOCATE_HUGEPAGES=True
OVS_INTERFACE_DRIVER='igb_uio'

Verified the OVS_DB_SOCKET_DIR and all others. conf.db and db.sock exist.
So why ovs-vswitchd is failing to start??? Am I missing something???



Thanks,
Prathyusha


On Mon, Nov 16, 2015 at 4:39 PM, Mooney, Sean K <sean.k.moo...@intel.com>
wrote:

>
>
> Hi
>
>
>
> Yes sorry for the delay in responding to you and samta.
>
>
>
> In your case assuming you are using 2mb hugepages it is easy to hit dpdks
> default max memory segments
>
>
>
> This can be changed by setting OVS_DPDK_MEM_SEGMENTS= number that you will never hit>
>
> In the local.conf and recompiling. To do this simply remove the build
> complete file in /opt/stack/ovs
>
> rm –f /opt/stack/BUILD_COMPLETE
>
>
>
> in your case though you are using 1GB hugepages so I don’t think this is
> related to memory fragmentation
> or a lack of free hugepages.
>
>
>
> to use preallocated 1GB page with ovs you should instead set the following
> in your local.conf
>
>
>
> OVS_HUGEPAGE_MOUNT_PAGESIZE=1G
>
> OVS_ALLOCATE_HUGEPAGES=False
>
>
>
> Regards
>
> sean
>
>
>
> *From:* Prathyusha Guduri [mailto:prathyushaconne...@gmail.com]
> *Sent:* Monday, November 16, 2015 6:20 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [networking-ovs-dpdk]
>
>
>
> Hi all,
>
> I have a similar problem as Samta. Am also stuck at the same place. The
> following command
>
> $sudo ovs-vsctl br-set-external-id br-ex bridge-id br-ex
>
> hangs forever. As Sean said, it might be because of ovs-vswitchd proces.
>
> > The vswitchd process may exit if it  failed to allocate memory (due to
> memory fragmentation or lack of free hugepages)
> > if the ovs-vswitchd.log is not available can you check the the hugepage
> mount point was created in
> > /mnt/huge And that Iis mounted
> > Run
> > ls -al /mnt/huge
> > and
> > mount
> >
>
> $mount
>
> /dev/sda6 on / type ext4 (rw,errors=remount-ro)
> proc on /proc type proc (rw,noexec,nosuid,nodev)
> sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
> none on /sys/fs/cgroup type tmpfs (rw)
> none on /sys/fs/fuse/connections type fusectl (rw)
> none on /sys/kernel/debug type debugfs (rw)
> none on /sys/kernel/security type securityfs (rw)
> udev on /dev type devtmpfs (rw,mode=0755)
> devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
> tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
> none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,si

[openstack-dev] [networking-ovs-dpdk] ovs-appctl doesn't function correctly

[Hui Xiang]

Hi all,

  I have managed to setup ovs-dpdk on Ubuntu, commands
'ovs-vsctl/ovs-ofctl' all work well excep 'ovs-appctl', could anyone help
me to figure it out? Thanks in advance.


xianghui@xianghui:~$ sudo ovs-ofctl show br-int
OFPT_FEATURES_REPLY (xid=0x2): dpid:264fa4e1f24f
n_tables:254, n_buffers:256
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan mod_dl_src
mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src mod_tp_dst
 1(int-br-eth1): addr:2e:23:93:7f:54:14
 config: 0
 state:  0
 speed: 0 Mbps now, 0 Mbps max
 2(tap7a2317aa-90): addr:0c:52:ff:7f:00:00
 config: PORT_DOWN
 state:  LINK_DOWN
 speed: 0 Mbps now, 0 Mbps max
 12(vhu5392206b-dc): addr:00:00:00:00:00:00
 config: PORT_DOWN
 state:  LINK_DOWN
 speed: 0 Mbps now, 0 Mbps max
 LOCAL(br-int): addr:26:4f:a4:e1:f2:4f
 config: PORT_DOWN
 state:  LINK_DOWN
 current:10MB-FD COPPER
 speed: 10 Mbps now, 0 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0

xianghui@xianghui:~$ sudo ovs-appctl vlog/set dbg
2015-11-16T09:50:28Z|1|daemon_unix|WARN|/var/run/openvswitch/ovs-vswitchd.pid:
open: No such file or directory
ovs-appctl: cannot read pidfile "/var/run/openvswitch/ovs-vswitchd.pid" (No
such file or directory)

Also tried as below, failed as well.

xianghui@xianghui:~$ sudo ovs-appctl -t /opt/stack/logs/ovs-vswitchd.pid
vlog/set dbg
2015-11-16T09:58:15Z|1|unixctl|WARN|failed to connect to
/opt/stack/logs/ovs-vswitchd.pid
ovs-appctl: cannot connect to "/opt/stack/logs/ovs-vswitchd.pid"
(Connection refused)
xianghui@xianghui:~$ sudo ovs-appctl -t /var/run/openvswitch/db.sock
vlog/set dbg
unknown methodovs-appctl: /var/run/openvswitch/db.sock: server returned an
error



-- 
Best Regards.
Hui.

OpenStack Engineer
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk]

[Mooney, Sean K]

Hi

Yes sorry for the delay in responding to you and samta.

In your case assuming you are using 2mb hugepages it is easy to hit dpdks 
default max memory segments

This can be changed by setting OVS_DPDK_MEM_SEGMENTS=
In the local.conf and recompiling. To do this simply remove the build complete 
file in /opt/stack/ovs
rm –f /opt/stack/BUILD_COMPLETE

in your case though you are using 1GB hugepages so I don’t think this is 
related to memory fragmentation
or a lack of free hugepages.

to use preallocated 1GB page with ovs you should instead set the following in 
your local.conf

OVS_HUGEPAGE_MOUNT_PAGESIZE=1G
OVS_ALLOCATE_HUGEPAGES=False

Regards
sean

From: Prathyusha Guduri [mailto:prathyushaconne...@gmail.com]
Sent: Monday, November 16, 2015 6:20 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [networking-ovs-dpdk]

Hi all,

I have a similar problem as Samta. Am also stuck at the same place. The 
following command

$sudo ovs-vsctl br-set-external-id br-ex bridge-id br-ex

hangs forever. As Sean said, it might be because of ovs-vswitchd proces.

> The vswitchd process may exit if it  failed to allocate memory (due to memory 
> fragmentation or lack of free hugepages)
> if the ovs-vswitchd.log is not available can you check the the hugepage mount 
> point was created in
> /mnt/huge And that Iis mounted
> Run
> ls -al /mnt/huge
> and
> mount
>
$mount
/dev/sda6 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu type cgroup (rw,relatime,cpu)
cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,relatime,cpuacct)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,relatime,freezer)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,relatime,perf_event)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,relatime,hugetlb)
systemd on /sys/fs/cgroup/systemd type cgroup 
(rw,noexec,nosuid,nodev,none,name=systemd)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse 
(rw,nosuid,nodev,user=ubuntu)
/mnt/huge is my mount point. So no mounting happening.
ovs-vswitchd.log says

2015-11-13T12:48:01Z|1|dpdk|INFO|User-provided -vhost_sock_dir in use: 
/var/run/openvswitch
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Detected lcore 4 as core 4 on socket 0
EAL: Detected lcore 5 as core 5 on socket 0
EAL: Detected lcore 6 as core 0 on socket 0
EAL: Detected lcore 7 as core 1 on socket 0
EAL: Detected lcore 8 as core 2 on socket 0
EAL: Detected lcore 9 as core 3 on socket 0
EAL: Detected lcore 10 as core 4 on socket 0
EAL: Detected lcore 11 as core 5 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 12 lcore(s)
EAL: VFIO modules not all loaded, skip VFIO support...
EAL: Searching for IVSHMEM devices...
EAL: No IVSHMEM configuration found!
EAL: Setting up memory...
EAL: Ask a virtual area of 0x18000 bytes
EAL: Virtual area found at 0x7f1e (size = 0x18000)
EAL: remap_all_hugepages(): mmap failed: Cannot allocate memory
EAL: Failed to remap 1024 MB pages
PANIC in rte_eal_init():
Cannot init memory
7: [/usr/sbin/ovs-vswitchd() [0x40b803]]
6: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f1fb52d3ec5]]
5: [/usr/sbin/ovs-vswitchd() [0x40a822]]
4: [/usr/sbin/ovs-vswitchd() [0x675432]]
3: [/usr/sbin/ovs-vswitchd() [0x442155]]
2: [/usr/sbin/ovs-vswitchd() [0x407c9f]]
1: [/usr/sbin/ovs-vswitchd() [0x447828]]
I have given hugepages in /boot/grub/grub.cfg file. So there are free hugepages.


AnonHugePages:378880 kB
HugePages_Total:   6
HugePages_Free:6
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:1048576 kB
It failed to allocate memory because mounting was not done. Did not understand 
why mounting is not done when there are free hugepages.
And also dpdk binding did happen.

$../DPDK-v2.0.0/tools/dpdk_nic_bind.py --status

Network device

Re: [openstack-dev] [networking-ovs-dpdk] ovs-appctl doesn't function correctly

[Mooney, Sean K]

To use the ovs-appctl application you have to specify the socket path to the 
ovs-vswitchd process.
ovs-appctl -t /var/run/openvswitch/ list-commands
e.g.
ovs-appctl -t /var/run/openvswitch/ovs-vswitchd.10110.ctl list-commands



From: Hui Xiang [mailto:hui.xi...@canonical.com]
Sent: Monday, November 16, 2015 10:01 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [networking-ovs-dpdk] ovs-appctl doesn't function 
correctly

Hi all,

  I have managed to setup ovs-dpdk on Ubuntu, commands 'ovs-vsctl/ovs-ofctl' 
all work well excep 'ovs-appctl', could anyone help me to figure it out? Thanks 
in advance.


xianghui@xianghui:~$ sudo ovs-ofctl show br-int
OFPT_FEATURES_REPLY (xid=0x2): dpid:264fa4e1f24f
n_tables:254, n_buffers:256
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan mod_dl_src 
mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src mod_tp_dst
 1(int-br-eth1): addr:2e:23:93:7f:54:14
 config: 0
 state:  0
 speed: 0 Mbps now, 0 Mbps max
 2(tap7a2317aa-90): addr:0c:52:ff:7f:00:00
 config: PORT_DOWN
 state:  LINK_DOWN
 speed: 0 Mbps now, 0 Mbps max
 12(vhu5392206b-dc): addr:00:00:00:00:00:00
 config: PORT_DOWN
 state:  LINK_DOWN
 speed: 0 Mbps now, 0 Mbps max
 LOCAL(br-int): addr:26:4f:a4:e1:f2:4f
 config: PORT_DOWN
 state:  LINK_DOWN
 current:10MB-FD COPPER
 speed: 10 Mbps now, 0 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0

xianghui@xianghui:~$ sudo ovs-appctl vlog/set dbg
2015-11-16T09:50:28Z|1|daemon_unix|WARN|/var/run/openvswitch/ovs-vswitchd.pid:
 open: No such file or directory
ovs-appctl: cannot read pidfile "/var/run/openvswitch/ovs-vswitchd.pid" (No 
such file or directory)

Also tried as below, failed as well.

xianghui@xianghui:~$ sudo ovs-appctl -t /opt/stack/logs/ovs-vswitchd.pid 
vlog/set dbg
2015-11-16T09:58:15Z|1|unixctl|WARN|failed to connect to 
/opt/stack/logs/ovs-vswitchd.pid
ovs-appctl: cannot connect to "/opt/stack/logs/ovs-vswitchd.pid" (Connection 
refused)
xianghui@xianghui:~$ sudo ovs-appctl -t /var/run/openvswitch/db.sock vlog/set 
dbg
unknown methodovs-appctl: /var/run/openvswitch/db.sock: server returned an error



--
Best Regards.
Hui.

OpenStack Engineer

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk]

[Prathyusha Guduri]

Hi Sean,

I realised on debugging ovs-dpdk-init script that the main issue is with
the following command

$ screen -dms ovs-vswitchd sudo sg $qemu_group -c "umask 002;
${OVS_INSTALL_DIR}/sbin/ovs-vswitchd --dpdk -vhost_sock_dir
$OVS_DB_SOCKET_DIR -c $OVS_CORE_MASK -n $OVS_MEM_CHANNELS  --proc-type
primary  --huge-dir $OVS_HUGEPAGE_MOUNT --socket-mem $OVS_SOCKET_MEM
$pciAddressWhitelist -- unix:$OVS_DB_SOCKET 2>&1 | tee
${OVS_LOG_DIR}/ovs-vswitchd.log"


which I guess is starting the ovs-vswitchd application. Before this
command, huge pages is mounted and port binding is also done but still the
screen command fails.
I verified the db.sock and conf.db files.

Any help is highly appreciated.

Thanks,
Prathyusha



On Mon, Nov 16, 2015 at 5:12 PM, Prathyusha Guduri <
prathyushaconne...@gmail.com> wrote:

> Hi Sean,
>
> Thanks for your response.
>
> in your case though you are using 1GB hugepages so I don’t think this is
> related to memory fragmentation
> or a lack of free hugepages.
>
>
>
> to use preallocated 1GB page with ovs you should instead set the following
> in your local.conf
>
>
>
> OVS_HUGEPAGE_MOUNT_PAGESIZE=1G
> OVS_ALLOCATE_HUGEPAGES=False
>
>
> Added the above two parameters to the local.conf. The same problem again.
> Basically it throws this error -
> 2015-11-16 11:31:44.741 | starting vswitchd
> 2015-11-16 11:31:44.863 | sudo RTE_SDK=/opt/stack/DPDK-v2.0.0
> RTE_TARGET=build /opt/stack/DPDK-v2.0.0/tools/dpdk_nic_bind.py -b igb_uio
> :07:00.0
> 2015-11-16 11:31:45.169 | sudo ovs-vsctl --no-wait --may-exist add-port
> br-eth1 dpdk0 -- set Interface dpdk0 type=dpdk
> 2015-11-16 11:31:46.314 | Waiting for ovs-vswitchd to start...
> 2015-11-16 11:31:47.442 | libvirt-bin stop/waiting
> 2015-11-16 11:31:49.473 | libvirt-bin start/running, process 2255
> 2015-11-16 11:31:49.477 | [ERROR] /etc/init.d/ovs-dpdk:563 ovs-vswitchd
> application failed to start
>
>
> manually mounting /mnt/huge and then commenting that part from the
> /etc/init.d/ovs-dpdk script also throws the same error.
>
> Using 1G hugepagesize should not give any memory related problem. I dont
> understand why it is not mounting then.
> Here is the /opt/stack/networking-ovs-dpdk/devstack/ovs-dpdk/ovs-dpdk.conf
>
> RTE_SDK=${RTE_SDK:-/opt/stack/DPDK}
> RTE_TARGET=${RTE_TARGET:-x86_64-ivshmem-linuxapp-gcc}
>
> OVS_INSTALL_DIR=/usr
> OVS_DB_CONF_DIR=/etc/openvswitch
> OVS_DB_SOCKET_DIR=/var/run/openvswitch
> OVS_DB_CONF=$OVS_DB_CONF_DIR/conf.db
> OVS_DB_SOCKET=OVS_DB_SOCKET_DIR/db.sock
>
> OVS_SOCKET_MEM=2048,2048
> OVS_MEM_CHANNELS=4
> OVS_CORE_MASK=${OVS_CORE_MASK:-2}
> OVS_PMD_CORE_MASK=${OVS_PMD_CORE_MASK:-4}
> OVS_LOG_DIR=/tmp
> OVS_LOCK_DIR=''
> OVS_SRC_DIR=/opt/stack/ovs
> OVS_DIR=${OVS_DIR:-${OVS_SRC_DIR}}
> OVS_UTILS=${OVS_DIR}/utilities/
> OVS_DB_UTILS=${OVS_DIR}/ovsdb/
> OVS_DPDK_DIR=$RTE_SDK
> OVS_NUM_HUGEPAGES=${OVS_NUM_HUGEPAGES:-5}
> OVS_HUGEPAGE_MOUNT=${OVS_HUGEPAGE_MOUNT:-/mnt/huge}
> OVS_HUGEPAGE_MOUNT_PAGESIZE=''
> OVS_BOND_MODE=$OVS_BOND_MODE
> OVS_BOND_PORTS=$OVS_BOND_PORTS
> OVS_BRIDGE_MAPPINGS=eth1
> OVS_PCI_MAPPINGS=:07:00.0#eth1
> OVS_DPDK_PORT_MAPPINGS=''
> OVS_TUNNEL_CIDR_MAPPING=''
> OVS_ALLOCATE_HUGEPAGES=True
> OVS_INTERFACE_DRIVER='igb_uio'
>
> Verified the OVS_DB_SOCKET_DIR and all others. conf.db and db.sock exist.
> So why ovs-vswitchd is failing to start??? Am I missing something???
>
>
>
> Thanks,
> Prathyusha
>
>
> On Mon, Nov 16, 2015 at 4:39 PM, Mooney, Sean K <sean.k.moo...@intel.com>
> wrote:
>
>>
>>
>> Hi
>>
>>
>>
>> Yes sorry for the delay in responding to you and samta.
>>
>>
>>
>> In your case assuming you are using 2mb hugepages it is easy to hit dpdks
>> default max memory segments
>>
>>
>>
>> This can be changed by setting OVS_DPDK_MEM_SEGMENTS=> number that you will never hit>
>>
>> In the local.conf and recompiling. To do this simply remove the build
>> complete file in /opt/stack/ovs
>>
>> rm –f /opt/stack/BUILD_COMPLETE
>>
>>
>>
>> in your case though you are using 1GB hugepages so I don’t think this is
>> related to memory fragmentation
>> or a lack of free hugepages.
>>
>>
>>
>> to use preallocated 1GB page with ovs you should instead set the
>> following in your local.conf
>>
>>
>>
>> OVS_HUGEPAGE_MOUNT_PAGESIZE=1G
>>
>> OVS_ALLOCATE_HUGEPAGES=False
>>
>>
>>
>> Regards
>>
>> sean
>>
>>
>>
>> *From:* Prathyusha Guduri [mailto:prathyushaconne...@gmail.com]
>> *Sent:* Monday, November 16, 2015 

Re: [openstack-dev] [networking-ovs-dpdk]

[Prathyusha Guduri]

t; > Can you  check which interface are bound to the dpdk driver by running
> the following command
> >
> > /opt/stack/DPDK-v2.0.0/tools/dpdk_nic_bind.py --status
> >
> /opt/stack/DPDK-v2.0.0/tools/dpdk_nic_bind.py --status
>
> Network devices using DPDK-compatible driver
> 
> 
>
> Network devices using kernel driver
> ===
> :01:00.0 'Ethernet Controller 10-Gigabit X540-AT2' if=p1p1 drv=ixgbe
> unused=igb_uio
> :02:00.0 'Ethernet Controller XL710 for 40GbE QSFP+' if=p4p1 drv=i40e
> unused=igb_uio
> :03:00.0 'Ethernet Controller XL710 for 40GbE QSFP+' if=p2p1 drv=i40e
> unused=igb_uio
> :06:00.0 'I350 Gigabit Network Connection' if=em1 drv=igb
> unused=igb_uio *Active*
> :06:00.1 'I350 Gigabit Network Connection' if=em2 drv=igb
> unused=igb_uio
>
> Other network devices
> =====
> :01:00.1 'Ethernet Controller 10-Gigabit X540-AT2' unused=igb_uio
>
> >
> > Finally can you confim that ovs-dpdk compiled successfully by either
> check the xstack.log or
> > Checking for the BUILD_COMPLETE file in /opt/stack/ovs
> BUILD_COMPLETE exist in /opt/stack/ovs though its empty.
> >
> > Regards
> > sean
> >
> >
> >
> >
> > -Original Message-
> > From: Samta Rangare [mailto:samtarang...@gmail.com]
> > Sent: Monday, November 9, 2015 2:31 PM
> > To: Czesnowicz, Przemyslaw
> > Cc: OpenStack Development Mailing List (not for usage questions)
> > Subject: Re: [openstack-dev] [networking-ovs-dpdk]
> >
> > Thanks for replying Przemyslaw, there is no ovs-vswitchd.log in
> /opt/stack/logs/. This is all contains inside (ovsdb-server.pid, screen).
> >
> > When I cancel stack .sh (ctr c), and try to rerun this $sudo ovs-vsctl
> br-set-external-id br-ex bridge-id br-ex it didnt hang, that means vSwitch
> was running isn't it ?
> >
> > But rerunning stack.sh after unstack hangs again.
> >
> > Thanks,
> > Samta
> >
> > On Mon, Nov 9, 2015 at 7:50 PM, Czesnowicz, Przemyslaw <
> przemyslaw.czesnow...@intel.com> wrote:
> >> 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:51 PM
> >>> To: OpenStack Development Mailing List (not for usage questions)
> >>> Subject: [openstack-dev] [networking-ovs-dpdk]
> >>>
> >>> Hello Everyone,
> >>>
> >>> I am installing devstack with networking-ovs-dpdk. The local.conf
> >>> exactly looks like the one is available in /opt/stack/networking-ovs-
> >>> dpdk/doc/source/_downloads/local.conf.single_node.
> >>> So I believe all the necessary configuration will be taken care.
> >>>
> >>> However I am stuck at place where devstack is trying to set
> >>> external-id ($ sudo ovs-vsctl br-set-external-id br-ex bridge-id
> >>> br-ex). As soon as it hits at this place it's just hangs forever. I
> >>> tried commenting this line from
> >>> lib/neutron_plugin/ml2 (I know this is wrong) and then all services
> >>> came up except ovs-dpdk agent and ovs agent.
> >>>
> >>> BTW I am deploying it in ubuntu 14.04. Any pointer will be really
> helpful.
> >>>
> >>> Thanks,
> >>> Samta
> >>>
> >>> __
> >>> 
> >>> OpenStack Development Mailing List (not for usage questions)
> >>> Unsubscribe: OpenStack-dev-
> >>> requ...@lists.openstack.org?subject:unsubscribe
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk]

[Samta Rangare]

-Gigabit X540-AT2' if=p1p1 drv=ixgbe
unused=igb_uio
:02:00.0 'Ethernet Controller XL710 for 40GbE QSFP+' if=p4p1 drv=i40e
unused=igb_uio
:03:00.0 'Ethernet Controller XL710 for 40GbE QSFP+' if=p2p1 drv=i40e
unused=igb_uio
:06:00.0 'I350 Gigabit Network Connection' if=em1 drv=igb
unused=igb_uio *Active*
:06:00.1 'I350 Gigabit Network Connection' if=em2 drv=igb
unused=igb_uio

Other network devices
=
:01:00.1 'Ethernet Controller 10-Gigabit X540-AT2' unused=igb_uio

>
> Finally can you confim that ovs-dpdk compiled successfully by either
check the xstack.log or
> Checking for the BUILD_COMPLETE file in /opt/stack/ovs
BUILD_COMPLETE exist in /opt/stack/ovs though its empty.
>
> Regards
> sean
>
>
>
>
> -Original Message-
> From: Samta Rangare [mailto:samtarang...@gmail.com]
> Sent: Monday, November 9, 2015 2:31 PM
> To: Czesnowicz, Przemyslaw
> Cc: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [networking-ovs-dpdk]
>
> Thanks for replying Przemyslaw, there is no ovs-vswitchd.log in
/opt/stack/logs/. This is all contains inside (ovsdb-server.pid, screen).
>
> When I cancel stack .sh (ctr c), and try to rerun this $sudo ovs-vsctl
br-set-external-id br-ex bridge-id br-ex it didnt hang, that means vSwitch
was running isn't it ?
>
> But rerunning stack.sh after unstack hangs again.
>
> Thanks,
> Samta
>
> On Mon, Nov 9, 2015 at 7:50 PM, Czesnowicz, Przemyslaw <
przemyslaw.czesnow...@intel.com> wrote:
>> 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:51 PM
>>> To: OpenStack Development Mailing List (not for usage questions)
>>> Subject: [openstack-dev] [networking-ovs-dpdk]
>>>
>>> Hello Everyone,
>>>
>>> I am installing devstack with networking-ovs-dpdk. The local.conf
>>> exactly looks like the one is available in /opt/stack/networking-ovs-
>>> dpdk/doc/source/_downloads/local.conf.single_node.
>>> So I believe all the necessary configuration will be taken care.
>>>
>>> However I am stuck at place where devstack is trying to set
>>> external-id ($ sudo ovs-vsctl br-set-external-id br-ex bridge-id
>>> br-ex). As soon as it hits at this place it's just hangs forever. I
>>> tried commenting this line from
>>> lib/neutron_plugin/ml2 (I know this is wrong) and then all services
>>> came up except ovs-dpdk agent and ovs agent.
>>>
>>> BTW I am deploying it in ubuntu 14.04. Any pointer will be really
helpful.
>>>
>>> Thanks,
>>> Samta
>>>
>>> __
>>> 
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: OpenStack-dev-
>>> requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [networking-ovs-dpdk]

[Samta Rangare]

Hello Everyone,

I am installing devstack with networking-ovs-dpdk. The local.conf
exactly looks like the one is available in
/opt/stack/networking-ovs-dpdk/doc/source/_downloads/local.conf.single_node.
So I believe all the necessary configuration will be taken care.

However I am stuck at place where devstack is trying to set external-id
($ sudo ovs-vsctl br-set-external-id br-ex bridge-id br-ex). As soon
as it hits at this place it's just hangs forever. I tried commenting
this line from lib/neutron_plugin/ml2 (I know this is wrong) and then
all services came up except ovs-dpdk agent and ovs agent.

BTW I am deploying it in ubuntu 14.04. Any pointer will be really helpful.

Thanks,
Samta

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk]

[Czesnowicz, Przemyslaw]

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:51 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [networking-ovs-dpdk]
> 
> Hello Everyone,
> 
> I am installing devstack with networking-ovs-dpdk. The local.conf exactly
> looks like the one is available in /opt/stack/networking-ovs-
> dpdk/doc/source/_downloads/local.conf.single_node.
> So I believe all the necessary configuration will be taken care.
> 
> However I am stuck at place where devstack is trying to set external-id ($
> sudo ovs-vsctl br-set-external-id br-ex bridge-id br-ex). As soon as it hits 
> at
> this place it's just hangs forever. I tried commenting this line from
> lib/neutron_plugin/ml2 (I know this is wrong) and then all services came up
> except ovs-dpdk agent and ovs agent.
> 
> BTW I am deploying it in ubuntu 14.04. Any pointer will be really helpful.
> 
> Thanks,
> Samta
> 
> __
> 
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-
> requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk]

[Samta Rangare]

Thanks for replying Przemyslaw, there is no ovs-vswitchd.log in
/opt/stack/logs/. This is all contains inside (ovsdb-server.pid,
screen).

When I cancel stack .sh (ctr c), and try to rerun this $sudo ovs-vsctl
br-set-external-id br-ex bridge-id br-ex
it didnt hang, that means vSwitch was running isn't it ?

But rerunning stack.sh after unstack hangs again.

Thanks,
Samta

On Mon, Nov 9, 2015 at 7:50 PM, Czesnowicz, Przemyslaw
<przemyslaw.czesnow...@intel.com> wrote:
> 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:51 PM
>> To: OpenStack Development Mailing List (not for usage questions)
>> Subject: [openstack-dev] [networking-ovs-dpdk]
>>
>> Hello Everyone,
>>
>> I am installing devstack with networking-ovs-dpdk. The local.conf exactly
>> looks like the one is available in /opt/stack/networking-ovs-
>> dpdk/doc/source/_downloads/local.conf.single_node.
>> So I believe all the necessary configuration will be taken care.
>>
>> However I am stuck at place where devstack is trying to set external-id ($
>> sudo ovs-vsctl br-set-external-id br-ex bridge-id br-ex). As soon as it hits 
>> at
>> this place it's just hangs forever. I tried commenting this line from
>> lib/neutron_plugin/ml2 (I know this is wrong) and then all services came up
>> except ovs-dpdk agent and ovs agent.
>>
>> BTW I am deploying it in ubuntu 14.04. Any pointer will be really helpful.
>>
>> Thanks,
>> Samta
>>
>> __
>> 
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-
>> requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk]

[Mooney, Sean K]

Hi
Can you provide some more information regarding your deployment?

Can you check which kernel you are using.

uname -a

If you are using a 3.19 kernel changes to some locking code in the kennel broke 
synchronization dpdk2.0 and requires dpdk 2.1 to be used instead.
In general it is not advisable to use a 3.19 kernel with dpdk as it can lead to 
non-deterministic behavior.

When devstack hangs can you connect with a second ssh session and run 
sudo service ovs-dpdk status
and 
ps aux | grep ovs


When the deployment hangs at sudo ovs-vsctl br-set-external-id br-ex bridge-id 
br-ex
It usually means that the ovs-vswitchd process has exited.

This can happen for a number of reasons.
The vswitchd process may exit if it  failed to allocate memory (due to memory 
fragmentation or lack of free hugepages)
if the ovs-vswitchd.log is not available can you check the the hugepage mount 
point was created in
/mnt/huge And that Iis mounted 
Run 
ls -al /mnt/huge 
and 
mount

then checkout how many hugepages are mounted

cat /proc/meminfo | grep huge


the vswitchd process may also exit if it  failed to initializes dpdk interfaces.
This can happen if no interface is  compatible with the igb-uio or vfio-pci 
drivers
(note in the vfio-pci case all interface in the same iommu group must be bound 
to the vfio-pci driver and
The iommu must be enabled in the kernel command line with VT-d enabled in the 
bios)

Can you  check which interface are bound to the dpdk driver by running the 
following command

/opt/stack/DPDK-v2.0.0/tools/dpdk_nic_bind.py --status


Finally can you confim that ovs-dpdk compiled successfully by either check the 
xstack.log or 
Checking for the BUILD_COMPLETE file in /opt/stack/ovs

Regards
sean




-Original Message-
From: Samta Rangare [mailto:samtarang...@gmail.com] 
Sent: Monday, November 9, 2015 2:31 PM
To: Czesnowicz, Przemyslaw
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [networking-ovs-dpdk]

Thanks for replying Przemyslaw, there is no ovs-vswitchd.log in 
/opt/stack/logs/. This is all contains inside (ovsdb-server.pid, screen).

When I cancel stack .sh (ctr c), and try to rerun this $sudo ovs-vsctl 
br-set-external-id br-ex bridge-id br-ex it didnt hang, that means vSwitch was 
running isn't it ?

But rerunning stack.sh after unstack hangs again.

Thanks,
Samta

On Mon, Nov 9, 2015 at 7:50 PM, Czesnowicz, Przemyslaw 
<przemyslaw.czesnow...@intel.com> wrote:
> 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:51 PM
>> To: OpenStack Development Mailing List (not for usage questions)
>> Subject: [openstack-dev] [networking-ovs-dpdk]
>>
>> Hello Everyone,
>>
>> I am installing devstack with networking-ovs-dpdk. The local.conf 
>> exactly looks like the one is available in /opt/stack/networking-ovs- 
>> dpdk/doc/source/_downloads/local.conf.single_node.
>> So I believe all the necessary configuration will be taken care.
>>
>> However I am stuck at place where devstack is trying to set 
>> external-id ($ sudo ovs-vsctl br-set-external-id br-ex bridge-id 
>> br-ex). As soon as it hits at this place it's just hangs forever. I 
>> tried commenting this line from
>> lib/neutron_plugin/ml2 (I know this is wrong) and then all services 
>> came up except ovs-dpdk agent and ovs agent.
>>
>> BTW I am deploying it in ubuntu 14.04. Any pointer will be really helpful.
>>
>> Thanks,
>> Samta
>>
>> __
>> 
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-
>> requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk]

[Prathyusha Guduri]

Thanks Mooney,

will correct my localrc and run again

On Thu, Nov 5, 2015 at 6:23 PM, Mooney, Sean K <sean.k.moo...@intel.com> wrote:
> Hello
> When set OVS_DPDK_MODE=controller_ovs
>
> You are disabling install of ovs-dpdk on the contoler node and only 
> installing mechanism driver.
>
> If you want to install ovs-dpdk on the controller node you should set this 
> value as follows
>
> OVS_DPDK_MODE=controller_ovs_dpdk
>
> See
> https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/_downloads/local.conf.single_node
>
> ovs with dpdk will be installed in /usr/bin not user local bin as it does a 
> system wide install not a local install.
>
> Installation documentation can be found here
> https://github.com/openstack/networking-ovs-dpdk/tree/master/doc/source
>
> the networking-ovs-dpdk repo has been recently moved from stackforge to the 
> openstack namespace following the
> retirement of stackforge.
>
> Some like in the git repo still need to be updated to reflect this change.
>
> Regards
> sean
> -Original Message-
> From: Prathyusha Guduri [mailto:prathyushaconne...@gmail.com]
> Sent: Thursday, November 5, 2015 11:02 AM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [networking-ovs-dpdk]
>
> Hello all,
>
> Trying to install openstack with ovs-dpdk driver from devstack.
>
> Following is my localrc file
>
> HOST_IP_IFACE=eth0
> HOST_IP=10.0.2.15
> HOST_NAME=$(hostname)
>
> DATABASE_PASSWORD=open
> RABBIT_PASSWORD=open
> SERVICE_TOKEN=open
> SERVICE_PASSWORD=open
> ADMIN_PASSWORD=open
> MYSQL_PASSWORD=open
> HORIZON_PASSWORD=open
>
>
> enable_plugin networking-ovs-dpdk
> https://github.com/stackforge/networking-ovs-dpdk master 
> OVS_DPDK_MODE=controller_ovs
>
> disable_service n-net
> disable_service n-cpu
> enable_service neutron
> enable_service q-svc
> enable_service q-agt
> enable_service q-dhcp
> enable_service q-l3
> enable_service q-meta
> enable_service n-novnc
>
> DEST=/opt/stack
> SCREEN_LOGDIR=$DEST/logs/screen
> LOGFILE=${SCREEN_LOGDIR}/xstack.sh.log
> LOGDAYS=1
>
> Q_ML2_TENANT_NETWORK_TYPE=vlan
> ENABLE_TENANT_VLANS=True
> ENABLE_TENANT_TUNNELS=False
>
> #Dual socket platform with 16GB RAM,3072*2048kB hugepages leaves ~4G for the 
> system.
> OVS_NUM_HUGEPAGES=2048
> #Dual socket platform with 64GB RAM,14336*2048kB hugepages leaves ~6G for the 
> system.
> #OVS_NUM_HUGEPAGES=14336
>
> OVS_DATAPATH_TYPE=netdev
> OVS_LOG_DIR=/opt/stack/logs
> OVS_BRIDGE_MAPPINGS=public:br-ex
>
> ML2_VLAN_RANGES=public:100:200
> MULTI_HOST=1
>
> #[[post-config|$NOVA_CONF]]
> #[DEFAULT]
> firewall_driver=nova.virt.firewall.NoopFirewallDriver
> novncproxy_host=0.0.0.0
> novncproxy_port=6080
> scheduler_default_filters=RamFilter,ComputeFilter,AvailabilityZoneFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,PciPassthroughFilter,NUMATopologyFilter
>
>
> After running ./stack.sh which was sucessful , I could see that in 
> ml2.conf.ini file ovsdpdk was added as the mechanism driver. But the agent 
> running was still openvswitch. Tried running ovsdpdk on q-agt screen, but 
> failed because ovsdpdk was not installed in /usr/local/bin, which I thought 
> devstack is supposed to do.
> Tried running setup.py in networking-ovs-dpdk folder, but that also did not 
> install ovs-dpdk in /usr/local/bin.
>
> Am stuck here. Please guide me how to proceed further. Also the Readme in 
> networking-ovs-dpdk folder says the instructions regarding installation are 
> available in below links - 
> http://git.openstack.org/cgit/stackforge/networking-ovs-dpdk/tree/doc/source/installation.rst
>
> But no repos found there. Kindly guide me to a doc or something on how to 
> build ovs-dpdk from devstack
>
> Thank you,
> Prathyusha
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk]

[Mooney, Sean K]

Hello
When set OVS_DPDK_MODE=controller_ovs

You are disabling install of ovs-dpdk on the contoler node and only installing 
mechanism driver.

If you want to install ovs-dpdk on the controller node you should set this 
value as follows

OVS_DPDK_MODE=controller_ovs_dpdk

See 
https://github.com/openstack/networking-ovs-dpdk/blob/master/doc/source/_downloads/local.conf.single_node

ovs with dpdk will be installed in /usr/bin not user local bin as it does a 
system wide install not a local install.

Installation documentation can be found here
https://github.com/openstack/networking-ovs-dpdk/tree/master/doc/source

the networking-ovs-dpdk repo has been recently moved from stackforge to the 
openstack namespace following the
retirement of stackforge.

Some like in the git repo still need to be updated to reflect this change.

Regards
sean
-Original Message-
From: Prathyusha Guduri [mailto:prathyushaconne...@gmail.com] 
Sent: Thursday, November 5, 2015 11:02 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [networking-ovs-dpdk]

Hello all,

Trying to install openstack with ovs-dpdk driver from devstack.

Following is my localrc file

HOST_IP_IFACE=eth0
HOST_IP=10.0.2.15
HOST_NAME=$(hostname)

DATABASE_PASSWORD=open
RABBIT_PASSWORD=open
SERVICE_TOKEN=open
SERVICE_PASSWORD=open
ADMIN_PASSWORD=open
MYSQL_PASSWORD=open
HORIZON_PASSWORD=open


enable_plugin networking-ovs-dpdk
https://github.com/stackforge/networking-ovs-dpdk master 
OVS_DPDK_MODE=controller_ovs

disable_service n-net
disable_service n-cpu
enable_service neutron
enable_service q-svc
enable_service q-agt
enable_service q-dhcp
enable_service q-l3
enable_service q-meta
enable_service n-novnc

DEST=/opt/stack
SCREEN_LOGDIR=$DEST/logs/screen
LOGFILE=${SCREEN_LOGDIR}/xstack.sh.log
LOGDAYS=1

Q_ML2_TENANT_NETWORK_TYPE=vlan
ENABLE_TENANT_VLANS=True
ENABLE_TENANT_TUNNELS=False

#Dual socket platform with 16GB RAM,3072*2048kB hugepages leaves ~4G for the 
system.
OVS_NUM_HUGEPAGES=2048
#Dual socket platform with 64GB RAM,14336*2048kB hugepages leaves ~6G for the 
system.
#OVS_NUM_HUGEPAGES=14336

OVS_DATAPATH_TYPE=netdev
OVS_LOG_DIR=/opt/stack/logs
OVS_BRIDGE_MAPPINGS=public:br-ex

ML2_VLAN_RANGES=public:100:200
MULTI_HOST=1

#[[post-config|$NOVA_CONF]]
#[DEFAULT]
firewall_driver=nova.virt.firewall.NoopFirewallDriver
novncproxy_host=0.0.0.0
novncproxy_port=6080
scheduler_default_filters=RamFilter,ComputeFilter,AvailabilityZoneFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,PciPassthroughFilter,NUMATopologyFilter


After running ./stack.sh which was sucessful , I could see that in ml2.conf.ini 
file ovsdpdk was added as the mechanism driver. But the agent running was still 
openvswitch. Tried running ovsdpdk on q-agt screen, but failed because ovsdpdk 
was not installed in /usr/local/bin, which I thought devstack is supposed to do.
Tried running setup.py in networking-ovs-dpdk folder, but that also did not 
install ovs-dpdk in /usr/local/bin.

Am stuck here. Please guide me how to proceed further. Also the Readme in 
networking-ovs-dpdk folder says the instructions regarding installation are 
available in below links - 
http://git.openstack.org/cgit/stackforge/networking-ovs-dpdk/tree/doc/source/installation.rst

But no repos found there. Kindly guide me to a doc or something on how to build 
ovs-dpdk from devstack

Thank you,
Prathyusha

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [networking-ovs-dpdk]

[Prathyusha Guduri]

Hello all,

Trying to install openstack with ovs-dpdk driver from devstack.

Following is my localrc file

HOST_IP_IFACE=eth0
HOST_IP=10.0.2.15
HOST_NAME=$(hostname)

DATABASE_PASSWORD=open
RABBIT_PASSWORD=open
SERVICE_TOKEN=open
SERVICE_PASSWORD=open
ADMIN_PASSWORD=open
MYSQL_PASSWORD=open
HORIZON_PASSWORD=open


enable_plugin networking-ovs-dpdk
https://github.com/stackforge/networking-ovs-dpdk master
OVS_DPDK_MODE=controller_ovs

disable_service n-net
disable_service n-cpu
enable_service neutron
enable_service q-svc
enable_service q-agt
enable_service q-dhcp
enable_service q-l3
enable_service q-meta
enable_service n-novnc

DEST=/opt/stack
SCREEN_LOGDIR=$DEST/logs/screen
LOGFILE=${SCREEN_LOGDIR}/xstack.sh.log
LOGDAYS=1

Q_ML2_TENANT_NETWORK_TYPE=vlan
ENABLE_TENANT_VLANS=True
ENABLE_TENANT_TUNNELS=False

#Dual socket platform with 16GB RAM,3072*2048kB hugepages leaves ~4G
for the system.
OVS_NUM_HUGEPAGES=2048
#Dual socket platform with 64GB RAM,14336*2048kB hugepages leaves ~6G
for the system.
#OVS_NUM_HUGEPAGES=14336

OVS_DATAPATH_TYPE=netdev
OVS_LOG_DIR=/opt/stack/logs
OVS_BRIDGE_MAPPINGS=public:br-ex

ML2_VLAN_RANGES=public:100:200
MULTI_HOST=1

#[[post-config|$NOVA_CONF]]
#[DEFAULT]
firewall_driver=nova.virt.firewall.NoopFirewallDriver
novncproxy_host=0.0.0.0
novncproxy_port=6080
scheduler_default_filters=RamFilter,ComputeFilter,AvailabilityZoneFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,PciPassthroughFilter,NUMATopologyFilter


After running ./stack.sh which was sucessful , I could see that in
ml2.conf.ini file ovsdpdk was added as the mechanism driver. But the
agent running was still openvswitch. Tried running ovsdpdk on q-agt
screen, but failed because ovsdpdk was not installed in
/usr/local/bin, which I thought devstack is supposed to do.
Tried running setup.py in networking-ovs-dpdk folder, but that also
did not install ovs-dpdk in /usr/local/bin.

Am stuck here. Please guide me how to proceed further. Also the Readme
in networking-ovs-dpdk folder says the instructions regarding
installation are available in below links -
http://git.openstack.org/cgit/stackforge/networking-ovs-dpdk/tree/doc/source/installation.rst

But no repos found there. Kindly guide me to a doc or something on how
to build ovs-dpdk from devstack

Thank you,
Prathyusha

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [networking-ovs-dpdk]

[Rapelly, Varun]

Hi All,

Can we use https://github.com/openstack/networking-ovs-dpdk with packstack??

I'm trying to configure devstack with ovs-dpdk on ubuntu. But till now no 
success.

Could anybody tell whether it is supported on ubuntu or not? or only on Fedora 
it is tested?


Regards,
Varun

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [networking-ovs-dpdk]

[Mooney, Sean K]

Integration with packsack is not currently supported.
We currently have the first step( a puppet module to install ovs-dpdk) under 
review.
At present we are not directly targeting packstack support but if anyone wants 
to add support
It would be welcomed. At present devstack is the only fully supported 
deployment tool.

Support for Ubuntu 14.04 and centos 7.1 was recently added.
Automated Testing is done by the intel-networking-ci using fedora 21 but
We have manually tested Ubuntu and centos.

I currently have a ovs-dpdk deployed on Ubuntu 14.04 on one of my dev systems 
using the devstack.

Our current getting start guide just describes fedora 21 deployment but we 
should be adding a Ubuntu and centOS version soon.

As far as I recall the main changes for Ubuntu are

-  Instead of setting selinux to permissive uninstall apparmor.

-  Instead of enabling the virt preview repo enable the kilo Ubuntu  
cloud archive.

Note that as devstack installs from source the openstack packages from the kilo 
cloud archive
are not used it is enabled to provided updated Libvirt and qemu packages only.
As such kilo,liberty and master openstack should be deployable by devstack.

It should also be noted that due to changes in upstream neutron the stable/x 
branch of the networking-ovs-dpdk repo
Is only compatible with the stable/x release of opentack.

Regards
Sean.




From: Rapelly, Varun [mailto:vrape...@sonusnet.com]
Sent: Thursday, November 5, 2015 12:04 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [networking-ovs-dpdk]

Hi All,

Can we use https://github.com/openstack/networking-ovs-dpdk with packstack??

I'm trying to configure devstack with ovs-dpdk on ubuntu. But till now no 
success.

Could anybody tell whether it is supported on ubuntu or not? or only on Fedora 
it is tested?


Regards,
Varun

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev