Clarifications regarding ovirt-provider-ovn network

Hi, I had some questions a overt-provider-ovn based external network which is built on top of an physical network. I notice that VLAN tagging gets greyed out when I try to create an external provider network. Is it not supported by overt right now?I am on version 4.2.5.3. Also, if I create NICs with the external provider network built atop a physical network on VMs that are on different hosts, but the same cluster, I see they are unable to ping each other, though it seems to work fine if they are on the same host. Is that elected behaviour? Could you you please help me understand why? Thanks, Anurag

On Tue, Aug 14, 2018 at 11:50 PM, Anurag Porripireddi <anurag.porripireddi@bigswitch.com> wrote:
Hi,
I had some questions a overt-provider-ovn based external network which is built on top of an physical network. I notice that VLAN tagging gets greyed out when I try to create an external provider network. Is it not supported by overt right now?I am on version 4.2.5.3. Also, if I create NICs with the external provider network built atop a physical network on VMs that are on different hosts, but the same cluster, I see they are unable to ping each other, though it seems to work fine if they are on the same host. Is that elected behaviour? Could you you please help me understand why?
Currently, inter-host communication over an external network is only supported *if* the cluster's switch type is OVS - could you confirm my suspicion that the switch type of the cluster where you're creating your VMs is indeed linux bridge? You could achieve inter host communication in a linux bridge cluster by specifying a pure overlay network - e.g. don't connect the external network to a physical network. Never-the-less, the 'correct' way would be to created both the physical and the external network in another cluster, with switch type OVS; which - AFAIK - is currently *not* recommended for production use cases.
Thanks, Anurag _______________________________________________ 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/OAJ62BNREVNYOX...

Well, you are right about that. My cluster's switch type is linux bridge. Regrding the first question though, is VLAN tagging unsupported on external provider networks?

On Thu, Aug 16, 2018 at 9:11 PM, <anurag.porripireddi@bigswitch.com> wrote:
Well, you are right about that. My cluster's switch type is linux bridge. Regrding the first question though, is VLAN tagging unsupported on external provider networks?
Yes, VLAN tagging is *not* supported on external provider networks. The idea there is that you can create multiple isolated logical networks in the external provider, providing the same functionality as VLAN does. You can though connect an external network to a VLAN tagged physical network.
_______________________________________________ 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/WGA4KMZAAWYDHW...
participants (3)
-
Anurag Porripireddi
-
anurag.porripireddi@bigswitch.com
-
Miguel Duarte de Mora Barroso