Re: [openstack-dev] [kuryr] Port binding query

2016-05-12 Thread Mohammad Banikazemi
emi/Watson/IBM@IBMUS Date: 05/12/2016 11:51 AM Subject: Re: [openstack-dev] [kuryr] Port binding query On Thu, May 12, 2016 at 4:50 PM, Neil Jerram wrote: I'm trying Kuryr with networking-calico and think I've hit an unhelpful inconsistency. A Neutron port has 'i

Re: [openstack-dev] [kuryr] Port binding query

2016-05-12 Thread Antoni Segura Puimedon
On Thu, May 12, 2016 at 4:50 PM, Neil Jerram wrote: > 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 devic

[openstack-dev] [kuryr] Port binding query

2016-05-12 Thread Neil Jerram
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 bindin

[openstack-dev] [kuryr] Port binding query

2016-05-10 Thread Neil Jerram
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 bin