[Openstack] [Neutron]Can Neutron support multiple mechanism drivers on the same compute node

Zhou, Bin Bin_Zhou at comcast.com
Mon Jul 25 12:34:52 UTC 2016


Thanks Kevin for the clarification.
Bin

From: Kevin Benton <kevin at benton.pub<mailto:kevin at benton.pub>>
Date: Saturday, July 23, 2016 at 8:07 PM
To: "Zhou, Bin" <Bin_Zhou at comcast.com<mailto:Bin_Zhou at comcast.com>>
Cc: "openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>" <openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>>
Subject: Re: [Openstack] [Neutron]Can Neutron support multiple mechanism drivers on the same compute node

It can as long as they use different vnic_types. When the agent-based mechanism drivers determine if they can bind a port on the compute node they examine the host as well as the vnic_type.

This function is what an agent-based mech driver uses: https://github.com/openstack/neutron/blob/dcb43cf85e8764d3167fc307bcd81a80abf09644/neutron/plugins/ml2/drivers/mech_agent.py#L85-L114

On Sat, Jul 23, 2016 at 1:02 PM, Zhou, Bin <Bin_Zhou at comcast.com<mailto:Bin_Zhou at comcast.com>> wrote:
Can Neutron support multiple mechanism drivers on the same compute node? I thought the answer was “no”. But I start to doubt when I read configuration guide about SR-IOV driver. Particularly the following bugs:
SR-IOV port doesn’t reach OVS port on same compute node: https://bugs.launchpad.net/neutron/+bug/1492228
No connectivity when Launching an instance with Openvswitch interface when using SR-IOV: https://bugzilla.redhat.com/show_bug.cgi?id=1174864

Can anyone kindly help me to clarify it? Thanks a lot!

Bin Zhou

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160725/97217aad/attachment.html>


More information about the Openstack mailing list