On Mon, Apr 3, 2017 at 4:50 AM, Devin A. Bougie <devin.bougie@cornell.edu> wrote:

Thanks for following up, Gianluca. At this point, my main question is why should I configure iSCSI Bonds within the oVirt engine instead of or in addition to configuring iSCSI initiators and multipathd directly in the host's OS.

Mainly because it is intention of the projct to let the oVirt admin able to setup the environment also without strong Linux sysadmin competencies

In my case I pre-configured only the multipath part from the OS, as I needed a custom multipath config for Dell PS storage arrays. See here:

http://lists.ovirt.org/pipermail/users/2017-March/080898.html

The key is the line with

# VDSM PRIVATE

to be put under the line generated by oirt:

# VDSM REVISION 1.3

From the iSCSI configuration point of view I only configured /etc/iscsi/iscsid.conf as suggested by Dell, and this file seems not to be touched by oVirt.

Also see here for my configuration steps and screenshots for iSCSI-Multipath (not bonding) from within oVirt webadmin Gui, that should give you the same configuration you usually get manually as you stated:

http://lists.ovirt.org/pipermail/users/2017-March/080992.html

The doc parts should be these:

http://www.ovirt.org/documentation/admin-guide/chap-Storage/#configuring-iscsi-multipathing

http://www.ovirt.org/develop/release-management/features/storage/iscsi-multipath/

And here for official RHEV 4.0 docs:

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.0/html/administration_guide/sect-preparing_and_adding_block_storage

HIH,

Gianluca