Open Stack

Very nice

Get Outlook for Android<https://aka.ms/ghei36>

________________________________
From: pranab boruah <pranabjyotiboruah at gmail.com>
Sent: Wednesday, October 11, 2017 1:28:37 PM
To: Moshe Levi; openstack at lists.openstack.org; Trinath Somanchi
Cc: sean.k.mooney at intel.com
Subject: Re: [openstack-dev] [networking-odl] [SRIOV] [OVS HW offload] ERROR in port binding

Thanks Moshe and Trinath. We found out the issue.
We were using the stable pike branch of networking-odl.
This is where it failed:
https://github.com/openstack/networking-odl/blob/stable/pike/networking_odl/ml2/pseudo_agentdb_binding.py#L366

Now that we migrated to the master branch of networking-odl, it's
working for us.

Regards,
Pranab

On 8 October 2017 at 01:33, Moshe Levi <moshele at mellanox.com> wrote:
>
>
>> -----Original Message-----
>> From: pranab boruah [mailto:pranabjyotiboruah at gmail.com]
>> Sent: Friday, October 6, 2017 9:45 AM
>> To: openstack at lists.openstack.org
>> Cc: Moshe Levi <moshele at mellanox.com>; sean.k.mooney at intel.com
>> Subject: [openstack-dev] [networking-odl] [SRIOV] [OVS HW offload] ERROR
>> in port binding
>>
>> Hi,
>>
>> We have a SRIOV NIC that supports SRIOV and OVS HW offload. We built a
>> pike cluster with networking-odl as the mechanism driver.
>>
>> As Sean mentioned that ODL part for SRIOV + OVS HW offload is not ready,
>> so we applied the following patches to ODL(version Nitrogen) :
>>
>> 1.
>> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.
>> opendaylight.org%2Fgerrit%2F%23%2Fc%2F62481%2F&data=02%7C01%7Cm
>> oshele%40mellanox.com%7C28fcc198f7614f11c71a08d50c85c083%7Ca652971
>> c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636428690968981939&sdata=y8e
>> M1UjhRFofxv0JAkUyxzqvU6oQv8ctB%2Bu2fKohsZs%3D&reserved=0
>> 2.
>> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.
>> opendaylight.org%2Fgerrit%2F%23%2Fc%2F60259%2F&data=02%7C01%7Cm
>> oshele%40mellanox.com%7C28fcc198f7614f11c71a08d50c85c083%7Ca652971
>> c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636428690968981939&sdata=eQl
>> T9o4oeDv1XnnGMrWEqFsI8zWXoqwKEkKCVmav4cg%3D&reserved=0
>>
>> Now, when we create a direct vnic_type port and try to launch instances, we
>> are running into issues.
>>
>> 1. The ODL patches didn't work straight away with Nitrogen version.
>> The patches needs to be rebased.
> Yes ODL patch is till work in progress.
>>
>> 2. Modified Nova to include the pci device list. Also, added host-config to the
>> compute node using the following command
>>
>> ovs-vsctl set Open_vSwitch 7ef8db05-8a4f-4cea-8b3b-432416c102fc
>> external_ids:odl_os_hostconfig_config_odl_l2="{"supported_vnic_types":
>> [{"vnic_type": "normal", "vif_type":"ovs", "vif_details": {} },
>> {"vnic_type": "direct", "vif_type": "ovs", "vif_details": {} } ],
>> "allowed_network_types": ["local", "gre", "vlan", "vxlan"]}"
> I used the set_ovs_hostconfigs script see https://github.com/openstack/networking-odl/blob/master/networking_odl/cmd/set_ovs_hostconfigs.py
> With the ovs_sriov_offload and it worked for me.
>
>>
>> The error I am getting is from networking-odl ML2 driver. Do we need to
>> apply any patch there too?
>>
>> This is what the errror log says:
>>
>> networking_odl.ml2.pseudo_agentdb_binding
>> [req-0652004a-fd30-4503-aa57-e34aa8cff54e
>> 401f4c71873f4d17be9fbeabe423b7f9 8b48f23ebf754c41b336d13e69dcce11 -
>> default default] Binding failed: unsupported VNIC direct
>>
>> 2017-10-04 09:49:55.237 34400 WARNING
>> networking_odl.ml2.pseudo_agentdb_binding
>> [req-0652004a-fd30-4503-aa57-e34aa8cff54e
>> 401f4c71873f4d17be9fbeabe423b7f9 8b48f23ebf754c41b336d13e69dcce11 -
>> default default] No ODL hostconfigs for host overcloud-novacompute-
>> 1.localdomain found in agentdb
>>
>> 2017-10-04 09:49:55.237 34400 ERROR neutron.plugins.ml2.managers [req-
>> 0652004a-fd30-4503-aa57-e34aa8cff54e
>> 401f4c71873f4d17be9fbeabe423b7f9 8b48f23ebf754c41b336d13e69dcce11 -
>> default default] Failed to bind port
>> 96dc3a1f-fb21-4d9a-adfe-f34db45993d9 on host overcloud-novacompute-
>> 1.localdomain for vnic_type direct using segments [{'network_id': '6f747dee-
>> 3186-4aeb-b139-820c16709aee',
>> 'segmentation_id': 81, 'physical_network': None, 'id':
>> '845af7aa-5609-428c-bbd9-d133e16f9c22', 'network_type': u'vxlan'}]
>>
>> Are we missing any additional configuration step?
>>
>> TIA,
>> Pranab
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20171011/7508f821/attachment.html>