------GRXBPOHPD2HEMBNX2EO5M1ZQ7TTCG1
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
charset=UTF-8
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(a)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.
------GRXBPOHPD2HEMBNX2EO5M1ZQ7TTCG1
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: 8bit
<html><head></head><body>Ok. Thanks for your quick response. Sorry
for my late reply back :)<br>
<br>
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.<br>
<br>
<br>
Regards, <br>
Siggi<br>
<br>
<br><br><div class="gmail_quote">Den 7. september 2015
16:27:33 CEST, skrev Dan Kenigsberg <danken@redhat.com>:<blockquote
class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px
solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On Mon, Sep 07, 2015 at 02:45:04PM +0200, Sigbjorn Lie
wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt
1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> Hi list,<br
/> <br /> I've been looking around the web for QinQ support in Ovirt. I see
that QinQ is supported in CentOS<br /> 6.x and above. However I cannot see any
documented support in Ovirt. I've come across the page<br /> below which details
QinQ as a future feature.<br /> <br /> Is QinQ still a future feature, or is
it possible to use QinQ with Ovirt today somehow?<br /> <br /> <a
href="http://www.ovirt.org/Networking">http://www.ovirt.org/...
/></blockquote><br />I'm afraid we do not support QinQ, and it's
not on our immediate<br />roadmap.<br /><br />However, we would love to
understand your use case (do you want to<br />tunnel VM traffic within QinQ?
why?)<br /><br />I believe you can use network custom properties and<br
/>before/after_network_setup
hookpoint in order to tinker with this<br />yourself.<br /><br
/>Regards,<br />Dan.<br
/></pre></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my
brevity.</body></html>
------GRXBPOHPD2HEMBNX2EO5M1ZQ7TTCG1--