Hi Sean, its the dpdk physical interface.
dpdk interface is correctly added to the bridge. please find the below ovs-stats. controller -------------- [stack@localhost devstack]$ sudo ovs-vsctl show c74e8e55-8f4e-4e49-9547-4319803a85f9 Bridge "br-ens5f1" Port "br-ens5f1" Interface "br-ens5f1" type: internal Port "phy-br-ens5f1" Interface "phy-br-ens5f1" type: patch options: {peer="int-br-ens5f1"} Port "dpdk0" Interface "dpdk0" type: dpdk Bridge br-int fail_mode: secure Port "qr-9283d6fb-43" tag: 4095 Interface "qr-9283d6fb-43" type: internal Port "tap66998ddd-73" tag: 4095 Interface "tap66998ddd-73" type: internal Port br-int Interface br-int type: internal Port "int-br-ens5f1" Interface "int-br-ens5f1" type: patch options: {peer="phy-br-ens5f1"} Bridge br-ex Port "qg-736e604f-66" Interface "qg-736e604f-66" type: internal Port br-ex Interface br-ex type: internal compute -------------- [stack@compute-mwc devstack]$ sudo ovs-vsctl show 02f8fe2c-6d8a-426f-b9f0-8d228fab28e6 Bridge br-int fail_mode: secure Port "int-br-ens4f1" Interface "int-br-ens4f1" type: patch options: {peer="phy-br-ens4f1"} Port br-int Interface br-int type: internal Bridge "br-ens4f1" Port "br-ens4f1" Interface "br-ens4f1" type: internal Port "phy-br-ens4f1" Interface "phy-br-ens4f1" type: patch options: {peer="int-br-ens4f1"} Port "dpdk0" Interface "dpdk0" type: dpdk and one thing i notices is the ovs-dpdk agent for compute is missing in the neutron agent-list. [stack@localhost devstack]$ neutron agent-list +--------------------------------------+----------------+-----------------------+-------+----------------+---------------------------+ | id | agent_type | host | alive | admin_state_up | binary | +--------------------------------------+----------------+-----------------------+-------+----------------+---------------------------+ | 588b79af-6bec-4a5f-ac8b-1668cff948db | DHCP agent | localhost.localdomain | :-) | True | neutron-dhcp-agent | | 794acfdd-5e73-42b8-873b-682021689aad | DPDK OVS Agent | localhost.localdomain | :-) | True | neutron-openvswitch-agent | | 7b570743-7042-463c-af90-6c74adbec2e2 | Metadata agent | localhost.localdomain | :-) | True | neutron-metadata-agent | | ffc2f41d-33fa-4a8b-8a59-60cda81de6e4 | L3 agent | localhost.localdomain | :-) | True | neutron-l3-agent | +--------------------------------------+----------------+-----------------------+-------+----------------+---------------------------+ [stack@localhost devstack]$ nova service-list +----+----------------+-----------------------+----------+---------+-------+----------------------------+-----------------+ | Id | Binary | Host | Zone | Status | State | Updated_at | Disabled Reason | +----+----------------+-----------------------+----------+---------+-------+----------------------------+-----------------+ | 1 | nova-conductor | localhost.localdomain | internal | enabled | up | 2015-11-26T05:17:30.000000 | - | | 3 | nova-cert | localhost.localdomain | internal | enabled | up | 2015-11-26T05:17:33.000000 | - | | 4 | nova-scheduler | localhost.localdomain | internal | enabled | up | 2015-11-26T05:17:36.000000 | - | | 5 | nova-compute | compute-mwc | nova | enabled | up | 2015-11-26T05:17:37.000000 | - | +----+----------------+-----------------------+----------+---------+-------+----------------------------+-----------------+ Thanks Praveen On Thu, Nov 26, 2015 at 12:18 PM, Mooney, Sean K <sean.k.moo...@intel.com> wrote: > 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 > > ============================================ > > 0000:02:00.0 'Ethernet Controller XL710 for 40GbE QSFP+' drv=igb_uio > unused=i40e > > > > Network devices using kernel driver > > =================================== > > 0000:02:00.1 'Ethernet Controller XL710 for 40GbE QSFP+' if=ens785f1 > drv=i40e unused=igb_uio > > 0000:02:00.2 'Ethernet Controller XL710 for 40GbE QSFP+' if=ens785f2 > drv=i40e unused=igb_uio > > 0000:02:00.3 'Ethernet Controller XL710 for 40GbE QSFP+' if=ens785f3 > drv=i40e unused=igb_uio > > 0000:06:00.0 'I350 Gigabit Network Connection' if=enp6s0f0 drv=igb > unused=igb_uio > > 0000:06:00.1 'I350 Gigabit Network Connection' if=enp6s0f1 drv=igb > unused=igb_uio > > > > Other network devices > > ===================== > > <none> > > > > > > *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 " > 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 > >
__________________________________________________________________________ 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