On Wed, Jul 31, 2019 at 4:41 PM Michael Frank <micha@metrox.org> wrote:
Hi,

 since several days i try to install the hosted engine initially to an iscsi multipath device without success.
Some information on the environment:
- Version 4.3.3
- using two 10gbe interfaces as single bond for the ovirtmgmt interface 
- using two 10gbe storage interfaces on each hypervisor for iscsi storage
-- each storage interface is configured without any bonding, etc
-- each storage interface lives in a separate vlan were also the iscsi Portals/target are available, the iscsi portals have 4x10ge interfaces each, (2 in vlan xx and 2 interfaces in vlan yy )
-- so; each storage interface is connected to two iscsi Portals via 4 interfaces 

The documentation here is for me unclear:
>Note: To specify more than one iSCSI target, you must enable multipathing before deploying the self-hosted engine. There is also a Multipath >Helper tool that generates a script to install and configure multipath with different options.

This indicates for me that it should be possbile to install the HE directly on the /dev/mapper/mpath device which is availibale when I have prepared the host accordingly before installing the HE (log in to multiple iscsi targets, create proper multipath,conf, etc) - right ?

I login to the two iscsi portals and get in sum 8 pathes, 4 from each interface and iscsi target.
Basically I have then the mpath device on the hypervisor available and i can  mount the mpath device and put data on it.
In the cockpit interface the mount can also be activated and is recognized correctly.
multipathd -ll and lsblk looks good. Everything seems to be fine.

But when I run the "hosted-engine" --deploy, the last option while running the assistant is to enter the iscsi data.
So, basically i just want to define my mpath device - when entering the data (ip, port)for the iscsi Portal I can see the 4 pathes of the single hosted Engine target,
and when i choose the path where the "lun" is finally available it fails. I think in general this option is not that what i want to have 
here for using the multipath device.

I' m lost - what is the usual way to install the HE on a multipath device ?

Sorry for the delay, I missed this thread.

From ovirt-hosted-engine-setup you can configure the iSCSI storage domain, exposed by a single iSCSI target, to be accessed over multiple portals in a single portal group.
Once you have a running engine you can eventually complete the configuration creating an iSCSI bond from there.
Follow this guide for that:
https://ovirt.org/documentation/admin-guide/chap-Storage.html#configuring-iscsi-multipathing

Let's now focus on the first part.
On your SAN you should create more than one iSCSI portal.
Then you should group them in a single iSCSI target portal group.
You iSCSI target should be configured to be exposed over the whole iSCSI target portal group.
Then you have to create a LUN for the hosted-engine storage domain and associate it with that iSCSI target.

Now, on hosted-engine-setup (via CLI or via cokpit) you should enter the IP address or one of the iSCSI portals (and eventually one username/password couple for the iSCSI discovery).
The iSCSI discovery process will report back your iSCSI targets and the address of other iSCSI portals in the same iSCSI target portal group; each of them will be a path so if you have more than one iSCSI portal in a single iSCSI target portal group you will have multipath.

Next step is choosing one of the listed iSCSI targets, then hosted-engine-setup will list the LUNs there and you will be able to choose one of them to be used for the hosted-engine storage domain.

 

Do i have to change the configuration of the storage interfaces or the iscsi network design?
Did I missed something obvious ?
Can I put in my multipath data into the answerfile to get rid of the last step of the assistant ?
Can I use the related ansible role for specify the Mpath device which is available when activating the multipath service ?

Is it not possible in general ?? :

Sorry in advance for the long mail .... 1!^^

br,
michael

Sent from a mobile device 
_______________________________________________
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/QRL2FYUD66C5J2RKC4UJZP4OQJWXWSB5/