On Mon, Jul 4, 2016 at 5:10 PM, Giorgio Biacchi <giorgio@di.unimi.it> wrote:

As I said, Infiniband is not ethernet so it cannot be L2 bridged. This is normal
and I understand why it can't be done. I'd like to know if there's a way to
configure host networking for infiniband link without bridging because is not
necessary to have a bridge there. In addition to this, 3.6 behavior was
different. Here's all the relevant configuration files generated by 3.6 and 4.0:

------------- 3.6 ---------------

[root@node3.6]# cat /etc/sysconfig/network-scripts/ifcfg-ib0
# Generated by VDSM version 4.17.11-7.gitc0752ac.el7
DEVICE=ib0
HWADDR=80:00:00:48:fe:80:00:00:00:00:00:00:00:02:c9:03:00:0a:06:9f
ONBOOT=yes
BOOTPROTO=dhcp
MTU=65520
DEFROUTE=no
NM_CONTROLLED=no
IPV6INIT=no

[root@node3.6]# cat /var/lib/vdsm/persistence/netconf/nets/ibstorage
{
"nic": "ib0",
"bootproto": "dhcp",
"blockingdhcp": true,
"bridged": "false",
"mtu": "65520"
}

---------------------------------

------------- 4.0 ---------------

[root@node4.0]# cat /etc/sysconfig/network-scripts/ifcfg-ib0
# Generated by VDSM version 4.18.5.1-1.el7.centos
DEVICE=ib0
BRIDGE=ibstorage
ONBOOT=yes
MTU=65520
NM_CONTROLLED=no
IPV6INIT=no

[root@node4.0]# cat /var/lib/vdsm/persistence/netconf/nets/ibstorage
{
"ipv6autoconf": false,
"nic": "ib0",
"mtu": 65520,
"switch": "legacy",
"dhcpv6": false,
"stp": false,
"bridged": true,
"defaultRoute": false
}

[root@node4.0]# cat /var/lib/vdsm/persistence/netconf/nets/ib0
{
"ipv6autoconf": false,
"nic": "ib0",
"mtu": 65520,
"switch": "legacy",
"dhcpv6": false,
"stp": false,
"bridged": true,
"defaultRoute": false
}

[root@node4.0]# cat /etc/sysconfig/network-scripts/ifcfg-ibstorage
# Generated by VDSM version 4.18.5.1-1.el7.centos
DEVICE=ibstorage
TYPE=Bridge
DELAY=0
STP=off
ONBOOT=yes
DEFROUTE=no
NM_CONTROLLED=no
IPV6INIT=no
MTU=65520

---------------------------------

So it seems that 4.0 generates more files and wants to bridge an ethernet
unbridgeable link. Steps to attempt to configure the connection for 4.0 was the
same done successfully for 3.6.

Thanks again

On 07/04/2016 03:25 PM, Arman Khalatyan wrote:
> As I remember the IBoIP is not fully implemented Ethernet protocol, it does not
> support bridging.
>
>
> ***********************************************************
>
> Dr. Arman Khalatyan eScience -SuperComputing
> Leibniz-Institut für Astrophysik Potsdam (AIP)
> An der Sternwarte 16, 14482 Potsdam, Germany
>
> ***********************************************************
>
> On Mon, Jul 4, 2016 at 2:58 PM, Yevgeny Zaspitsky <yzaspits@redhat.com
> <mailto:yzaspits@redhat.com>> wrote:
>
> Hello,
>
> What's "couple of vdsm hooks"? Could you provide the source code of those?
>
> Regards,
> Yevgeny
>
> On Mon, Jul 4, 2016 at 1:43 PM, Giorgio Biacchi <giorgio@di.unimi.it
> <mailto:giorgio@di.unimi.it>> wrote:
>
> Hi list,
> I'm trying a test installation of the new Ovirt Node Image and engine before
> upgrading my 3.6 installation.
>
> In my current environment every hypervisor access the NFS shared data
> domain via
> infiniband. With a couple of vdsm hooks I was able to set the infiniband
> link in
> connected mode and set a MTU of 65520. In my case the infiniband link is
> used as
> a common NIC, I don't use RDMA, only IP over infiniband to access the
> data domain.
>
> Now, when I attempt to setup host networking, the system try to bridge the
> connection "ibstorage" (defined in networks tab) with ib0 device. But a non
> ethernet device cannot be bridged that way and host networking setup fails.
>
> Any idea or suggestion? With 3.6 (node and engine) all was fine.
>
> Thanks
> --
> gb
>
> PGP Key: http://pgp.mit.edu/
> Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34
> _______________________________________________
> Users mailing list
> Users@ovirt.org <mailto:Users@ovirt.org>
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
> _______________________________________________
> Users mailing list
> Users@ovirt.org <mailto:Users@ovirt.org>
> http://lists.ovirt.org/mailman/listinfo/users

>
>

--
gb

PGP Key: http://pgp.mit.edu/
Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 0F34