<html><body><p>Yes, we want to use the same naming conventions when possible.<br>Submitted a fix here: <a href="https://review.openstack.org/#/c/315799/">https://review.openstack.org/#/c/315799/</a><br><br>Best,<br><br>Mohammad<br><br><br><img width="16" height="16" src="cid:1__=8FBBF522DFED31408f9e8a93df938690918c8FB@" border="0" alt="Inactive hide details for Antoni Segura Puimedon ---05/12/2016 11:51:04 AM---On Thu, May 12, 2016 at 4:50 PM, Neil Jerram <neil"><font color="#424282">Antoni Segura Puimedon ---05/12/2016 11:51:04 AM---On Thu, May 12, 2016 at 4:50 PM, Neil Jerram <neil@tigera.io> wrote: > I'm trying Kuryr with network</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Antoni Segura Puimedon <toni+openstackml@midokura.com></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org></font><br><font size="2" color="#5F5F5F">Cc: </font><font size="2">Mohammad Banikazemi/Watson/IBM@IBMUS</font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">05/12/2016 11:51 AM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [openstack-dev] [kuryr] Port binding query</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><br><br><font size="4">On Thu, May 12, 2016 at 4:50 PM, Neil Jerram <</font><a href="mailto:neil@tigera.io" target="_blank"><u><font size="4" color="#0000FF">neil@tigera.io</font></u></a><font size="4">> wrote:</font><ul><font size="4">I'm trying Kuryr with networking-calico and think I've hit an unhelpful inconsistency. A Neutron port has 'id' and 'device_id' fields that are usually different. When Nova does VIF binding for a Neutron port, it generates the Linux device name from 'tap' + port['id']. But when Kuryr does VIF binding for a Neutron port, I think it generates the Linux device name from 'tap' + port['device_id'].<br><br>Thoughts? Does that sound right, or have I misread the code and my logs? If it's correct, it marginally impacts the ability to use identical agent and Neutron driver/plugin code for the two cases (Nova and Kuryr).</font></ul><br><font size="4">I think we are supposed to behave like Nova, binding wise.<br></font><br><font size="4">@Banix: Can you confirm that it is a bug and not a feature?<br></font><br><font size="4">From a quick grepping I see hat nova sets the name to be:<br><br> nova/network/neutronv2/api.py: devname = "tap" + current_neutron_port['id']<br></font><br><font size="4">Whereas in Kuryr we use the first 8 characters of the Docker endpoint id.<br> </font><ul><font size="4"><br>Thanks,<br> Neil</font><br><br><font size="4"><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: </font><a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank"><u><font size="4" color="#0000FF">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</font></u></a><u><font size="4" color="#0000FF"><br></font></u><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><u><font size="4" color="#0000FF">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></u></a><font size="4"><br></font></ul><br><BR>
</body></html>