Bug #5094

custom vnet driver using ovswitch is not possible

Added by Edouard Bourguignon over 2 years ago.

Status:PendingStart date:04/04/2017
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Core & System
Target version:-
Resolution: Pull request:
Affected Versions:OpenNebula 5.2

Description

I tried to add a new custom vnet driver. Everything is ok when hotplugging the interface to a running VM. But you have to modify the attach_nic script (which is I guess a bad idea? since it's outside of the vnet driver scope).

But when a new vm is DEPLOYed, ovswitch vn_mad type is hardcoded in the src/vmm/LibVirtDriverKVM.cc, meaning that you won't have the virtualport line in the libvirt XML vm definition. So the port of the VM won't be attached to the OVS bridge. And since it's hardcoded in the LibVirtDriverKVM.cc, you can't use custom drivers to deal with OVS type port. Am I wrong ?

It should be great if we can deal with OVS inside custom drivers.

ps: forum discussion is here https://forum.opennebula.org/t/custom-vnet-driver/4046

Also available in: Atom PDF