From: "Trey Dockendorf" <treydock(a)gmail.com&gt; To: "Arman Khalatyan" <arm2arm(a)gmail.com&gt; Cc: "users" <users(a)ovirt.org&gt; Sent: Tuesday, September 30, 2014 5:24:27 AM Subject: Re: [ovirt-users] Is it possible to add ISCSI over iser? Arman, One of my storage domains is iSCSI using iSER. You need the following in vdsm.conf: [irs] iscsi_default_ifaces = iser,default I believe the proper way to set that so it's preserved during node updates is the following # cat /etc/ovirt-host-deploy.conf.d/40-custom-vdsm-config.conf [environment:enforce] VDSM_CONFIG/irs/iscsi_default_ifaces=str:iser,default The filename I believe can be changed, just requires .conf extension Once VDSM is configured to use iser you can add the domain in the GUI using the IPoIB IP address to initiate iSER. ovirtnode01 # iscsiadm -m session iser: [3] 192.168.211.245:3260,1 iqn.2014-04.DOMAIN.vmstore1:ovirt-data_iscsi - Trey On Wed, Sep 24, 2014 at 6:42 AM, Arman Khalatyan <arm2arm(a)gmail.com&gt; wrote: > Hi, > I am trying to attach my new storage domain over iser. > My server always gets that request is tcp/ip not rdma. > Simple work around is login from hosts over iser. > Would be good to add a possibility to select the protocol of > iscsi:tcp/iser/srp. > > Thanks, > Arman > > PS > for those who was struggling with same trouble: > 1) on hosts: > add lines in /etc/rdma/rdma.conf > # Load iSER module > ISER_LOAD=YES > 2) service rdma restart (or modprobe ib_iser > 3) iscsiadm -m discovery -t st -p 10.10.10.31 -I iser > 4) iscsiadm -m node --login > > 5) check if disks are there > iscsiadm -m session -o show > lssci > [1228:0:0:0] storage IET Controller 0001 - > [1228:0:0:1] disk IET VIRTUAL-DISK 0001 /dev/sde > lsblk /dev/sde > NAME MAJ:MIN RM > SIZE RO TYPE MOUNTPOINT > sde 8:64 0 > 36.4T 0 disk > ââ100090001 (dm-8) 253:8 0 > 36.4T 0 mpath > ââ18b70b0d--4944--4c73--970d--87a1af353b9f-metadata (dm-9) 253:9 0 > 512M 0 lvm > ââ18b70b0d--4944--4c73--970d--87a1af353b9f-ids (dm-10) 253:10 0 > 128M 0 lvm > ââ18b70b0d--4944--4c73--970d--87a1af353b9f-leases (dm-11) 253:11 0 > 2G 0 lvm > ââ18b70b0d--4944--4c73--970d--87a1af353b9f-outbox (dm-12) 253:12 0 > 128M 0 lvm > ââ18b70b0d--4944--4c73--970d--87a1af353b9f-inbox (dm-13) 253:13 0 > 128M 0 lvm > ââ18b70b0d--4944--4c73--970d--87a1af353b9f-master (dm-14) 253:14 0 > 1G 0 lvm >

I don't. My oVirt engine is bare-metal. - Trey On Tue, Sep 30, 2014 at 7:22 AM, Doron Fediuck <dfediuck(a)redhat.com&gt; wrote: > > > ----- Original Message ----- >> From: "Trey Dockendorf" <treydock(a)gmail.com&gt; >> To: "Arman Khalatyan" <arm2arm(a)gmail.com&gt; >> Cc: "users" <users(a)ovirt.org&gt; >> Sent: Tuesday, September 30, 2014 5:24:27 AM >> Subject: Re: [ovirt-users] Is it possible to add ISCSI over iser? >> >> Arman, >> >> One of my storage domains is iSCSI using iSER. You need the following >> in vdsm.conf: >> >> [irs] >> iscsi_default_ifaces = iser,default >> >> I believe the proper way to set that so it's preserved during node >> updates is the following >> >> # cat /etc/ovirt-host-deploy.conf.d/40-custom-vdsm-config.conf >> [environment:enforce] >> VDSM_CONFIG/irs/iscsi_default_ifaces=str:iser,default >> >> The filename I believe can be changed, just requires .conf extension >> >> Once VDSM is configured to use iser you can add the domain in the GUI >> using the IPoIB IP address to initiate iSER. >> >> ovirtnode01 # iscsiadm -m session >> iser: [3] 192.168.211.245:3260,1 iqn.2014-04.DOMAIN.vmstore1:ovirt-data_iscsi >> >> - Trey >> >> On Wed, Sep 24, 2014 at 6:42 AM, Arman Khalatyan <arm2arm(a)gmail.com&gt; wrote: >> > Hi, >> > I am trying to attach my new storage domain over iser. >> > My server always gets that request is tcp/ip not rdma. >> > Simple work around is login from hosts over iser. >> > Would be good to add a possibility to select the protocol of >> > iscsi:tcp/iser/srp. >> > >> > Thanks, >> > Arman >> > >> > PS >> > for those who was struggling with same trouble: >> > 1) on hosts: >> > add lines in /etc/rdma/rdma.conf >> > # Load iSER module >> > ISER_LOAD=YES >> > 2) service rdma restart (or modprobe ib_iser >> > 3) iscsiadm -m discovery -t st -p 10.10.10.31 -I iser >> > 4) iscsiadm -m node --login >> > >> > 5) check if disks are there >> > iscsiadm -m session -o show >> > lssci >> > [1228:0:0:0] storage IET Controller 0001 - >> > [1228:0:0:1] disk IET VIRTUAL-DISK 0001 /dev/sde >> > lsblk /dev/sde >> > NAME MAJ:MIN RM >> > SIZE RO TYPE MOUNTPOINT >> > sde 8:64 0 >> > 36.4T 0 disk >> > ââ100090001 (dm-8) 253:8 0 >> > 36.4T 0 mpath >> > ââ18b70b0d--4944--4c73--970d--87a1af353b9f-metadata (dm-9) 253:9 0 >> > 512M 0 lvm >> > ââ18b70b0d--4944--4c73--970d--87a1af353b9f-ids (dm-10) 253:10 0 >> > 128M 0 lvm >> > ââ18b70b0d--4944--4c73--970d--87a1af353b9f-leases (dm-11) 253:11 0 >> > 2G 0 lvm >> > ââ18b70b0d--4944--4c73--970d--87a1af353b9f-outbox (dm-12) 253:12 0 >> > 128M 0 lvm >> > ââ18b70b0d--4944--4c73--970d--87a1af353b9f-inbox (dm-13) 253:13 0 >> > 128M 0 lvm >> > ââ18b70b0d--4944--4c73--970d--87a1af353b9f-master (dm-14) 253:14 0 >> > 1G 0 lvm >> > > > Thanks for the info, guys. > Does any of you use hosted engine with iSER?