Thank you, Gianluca.

= =3D The OpenStack integration with ScaleIO absolutely warrants further investig= =3D ation on my part. It looks like a rather recent addition to ScaleIO, so I'l= =3D l need to run that in a lab setting for a while. It looks like the best lon= =3D g term option.

In the meantime, I t= =3D hink that I might be able to get this working by exposing a few, larger LUN= =3D s via NFS running on the ScaleIO nodes. I lose granular snapshot capabiliti= =3D es and MPIO in ScaleIO that way, though.

If I need real MPIO-type performance on a VM, I guess I can just inst= =3D all the ScaleIO client in the guest and access the LUN that way.

<= =3D div>

Also, I plan on learning more about the iSCSI Direct LUN= =3D logic in oVirt to see if there is enough similarity between the output of = =3D iscsiadm and the ScaleIO SDC/SDS utilities to request a direct ScaleIO inte= =3D gration feature. That might be a nice little side project for a while.
<= =3D /div>

Have a great day,

--Scott Sobot= =3D ka

---- On Sun, 29 May 2016 02:45:3= =3D 6 -0700 =3D gianluca.cecchi(a)gmail.com wrote ----

=3D

On Sun, May 29, 2016 at 7:18 AM, Scott S= =3D obotka <s=3D cott(a)pragmatica.us> wrote:

Has anyone go= =3D tten an oVirt hosted engine and shared storage environment running with Sca= =3D leIO as the backing storage?

I was thinking t= =3D hat I would just set up iSCSI LUNs in ScaleIO and have oVirt point directly= =3D to one for the hosted engine setup. From there, my plan was to assign disk= =3D s to VMs as direct LUNs.

Unfortunately, it lo= =3D oks like ScaleIO dropped iSCSI support at around version 1.32 and I'm at a = =3D loss as to how I can expose ScaleIO LUNs to oVirt.

= =3D
Thank you,
--Scott Sobotka

I don't know much of ScaleIO, but at least since= =3D Liberty release it can be configured as a cinder backend driver in Opensta= =3D ck

http://docs.ope= ns=3D tack.org/liberty/config-reference/content/ScaleIO-cinder-driver.html

http://doc= s.=3D openstack.org/mitaka/config-reference/block-storage/drivers/emc-scaleio-dri= =3D ver.html

So the more "natural" way that comes = =3D to mind is to interface oVirt with cinder and configure ScaleIO in cinder i= =3D n similar way as with Ceph backend

http://old.ovirt.org= /F=3D eatures/Cinder_Integration

But this implies co= =3D nfiguring Openstack too and also I don't know how the security part (see ce= =3D ph authentication in above link), if present in ScaleIO, could be managed

HIH searching a solution

Gianlu= =3D ca

= =3D