Il giorno ven 21 set 2018 alle ore 12:34 Davide Butti <dbutti194@gmail.com> ha scritto:
Hello; I'm having some hard time getting my oVirt cluster back to work, after the last update to 4.2.6.

One thing that does not work anymore is VLAN Trunks; before the update, the cluster was running in OVS mode, and I could define logical networks without VLAN tag; then, networks packets got forwarded to the guest as "tagged".

Right now version 4.2.6 won't allow me to assign the (OVS) Logical network to the guest NICs anymore, but it insists that I use a vNIC profile from an external provider.

First question: Is this expected? Must I really work with externally provided networks only?

Anyway, for the vNIC interfaces that only carry untagged traffic, I was able to define an external OVN network, connect it to the corresponding "Data center Network", and everything works as it did before. But the "trick" does not work for "trunk" interfaces that should carry VLAN tagged traffic.

So to the second (main) question? How is this to be solved? Is there a way to define a VLAN trunk under OVN? Or is there a way to pickup a Data Center logical network to attach to the vNIC as we did before?



Dominic, can you please have a look?


 
Thanks in advance for your help!
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/P4OCWNPMJ442EJJJ3IC6MQD5G44ID26B/


--

SANDRO BONAZZOLA

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA

sbonazzo@redhat.com