You would be better off using something like openvswtich and vxlan's for your purpose. oVirt does support OpenStack Networking... which will give you what you are looking for in a lab env... tenant networks

On Wed, Oct 7, 2015 at 12:27 PM, Sigbjorn Lie <sigbjorn@nixtra.com> wrote:
Ok. Thanks for your quick response. Sorry for my late reply back :)

I had a request to have multiple concurrent labs of testing end point equipment which required to see a vlan trunk having the exact same vlan numbers across all the labs. The vlans coming from each lab had to be mapped to different vms. The different lab networks could not be joined. This required adding the vlan trunk from each lab into a qinq trunk which connects to the same hypervisor. Or using networking equipment having the ability to rewrite the vlans of the lab vlan trunks into other vlan numbers before they reach the hypervisor.


Regards,
Siggi



Den 7. september 2015 16:27:33 CEST, skrev Dan Kenigsberg <danken@redhat.com>:
On Mon, Sep 07, 2015 at 02:45:04PM +0200, Sigbjorn Lie wrote:
 Hi list,
 
 I've been looking around the web for QinQ support in Ovirt. I see that QinQ is supported in CentOS
 6.x and above. However I cannot see any documented support in Ovirt. I've come across the page
 below which details QinQ as a future feature.
 
 Is QinQ still a future feature, or is it possible to use QinQ with Ovirt today somehow?
 
 http://www.ovirt.org/Networking

I'm afraid we do not support QinQ, and it's not on our immediate
roadmap.

However, we would love to understand your use case (do you want to
tunnel VM traffic within QinQ? why?)

I believe you can use network custom properties and
before/after_network_setup
hookpoint in order to tinker with this
yourself.

Regards,
Dan.

 --
Sent from my Android device with K-9 Mail. Please excuse my brevity.

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users




--
Donny Davis