[openstack-dev] [nova][NFV] VIF_VHOSTUSER

loy wolfe loywolfe at gmail.com
Mon Sep 1 07:10:10 UTC 2014


If the neutron side MD is just for snabbswitch, then I thinks there is no
change to be merged into the tree. Maybe we can learn from sriov nic,
although backend is vendor specific, but the MD is generic, can support
snabb, dpdkovs, ans other userspace vswitch, etc.

As the reference implementation CI, the snabb can work in a very simple
mode without need for agent (just as agentless sriov veb nic)


On Sun, Aug 31, 2014 at 9:36 PM, Itzik Brown <itzikb at dev.mellanox.co.il>
wrote:

>
> On 8/30/2014 11:22 PM, Ian Wells wrote:
>
>> The problem here is that you've removed the vif_driver option and now
>> you're preventing the inclusion of named VIF types into the generic driver,
>> which means that rather than adding a package to an installation to add
>> support for a VIF driver it's now necessary to change the Nova code (and
>> repackage it, or - ew - patch it in place after installation).  I
>> understand where you're coming from but unfortunately the two changes
>> together make things very awkward.  Granted that vif_driver needed to go
>> away - it was the wrong level of code and the actual value was coming from
>> the wrong place anyway (nova config and not Neutron) - but it's been
>> removed without a suitable substitute.
>>
>> It's a little late for a feature for Juno, but I think we need to write
>> something discovers VIF types installed on the system.  That way you can
>> add a new VIF type to Nova by deploying a package (and perhaps naming it in
>> config as an available selection to offer to Neutron) *without* changing
>> the Nova tree itself.
>>
>>
>> In the meantime, I recommend you consult with the Neutron cores and see
>> if you can make an exception for the VHOSTUSER driver for the current
>> timescale.
>> --
>> Ian.
>>
>>  I Agree with Ian.
> My understanding from a conversation a month ago was that there would be
> an alternative to the deprecated config option.
> As far as I understand now there is no such alternative in Juno and in
> case that one has an out of the tree VIF Driver he'll be left out with a
> broken solution.
> What do you say about an option of reverting the change?
> Anyway It might be a good idea to discuss propositions to address this
> issue towards Kilo summit.
>
> BR,
> Itzik
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140901/a3fe3e0b/attachment.html>


More information about the OpenStack-dev mailing list