On Mar 10, 2017, at 1:28 PM, Juan Pablo <pablo.localhost(a)gmail.com> wrote:
Hi, what kind of setup you have? hosted engine just runs on nfs or
gluster afaik.
Thanks for replying, Juan. I was under the impression that the hosted engine would run on
an iSCSI data domain, based on
http://www.ovirt.org/develop/release-management/features/engine/self-host...
and the fact that "hosted-engine --deploy" does give you the option to choose
iscsi storage (but only one path, as far as I can tell).
I certainly could manage the iSCSI sessions outside of ovirt / vdsm, but wasn't sure
if that would cause problems or if that was all that's needed to allow the hosted
engine to boot automatically on an iSCSI data domain.
Thanks again,
Devin
2017-03-10 15:22 GMT-03:00 Devin A. Bougie
<devin.bougie(a)cornell.edu>:
We have an ovirt 4.1 cluster with an iSCSI data domain. If I shut down the entire
cluster and just boot the hosts, none of the hosts login to their iSCSI sessions until the
engine comes up. Without logging into the sessions, sanlock doesn't obtain any leases
and obviously none of the VMs start.
I'm sure there's something I'm missing, as it looks like it should be
possible to run a hosted engine on a cluster using an iSCSI data domain.
Any pointers or suggestions would be greatly appreciated.
Many thanks,
Devin
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users