Am 2017-07-04 um 10:01 schrieb Simone Tiraboschi:

On Tue, Jul 4, 2017 at 5:50 AM, Vinícius Ferrão < <>> wrote:

    Thanks, Konstantin.

    Just to be clear enough: the first deployment would be made on
    classic eth interfaces and later after the deployment of Hosted
    Engine I can convert the "ovirtmgmt" network to a LACP Bond, right?

    Another question: what about iSCSI Multipath on Self Hosted Engine?
    I've looked through the net and only found this issue:

    Appears to be unsupported as today, but there's an workaround on the
    comments. It's safe to deploy this way? Should I use NFS instead?

It's probably not the most tested path but once you have an engine you should be able to create an iSCSI bond on your hosts from the engine. Network configuration is persisted across host reboots and so the iSCSI bond configuration.

A different story is instead having ovirt-ha-agent connecting multiple IQNs or multiple targets over your SAN. This is currently not supported for the hosted-engine storage domain.

Hi Simone,

i think my post to this list titled "iSCSI multipathing setup troubles" just recently is about the exact same problem, except i'm not talking about the hosted-engine storage domain. i would like to configure _any_ iSCSI storage domain the way you describe it in i would like to do so using the oVirt "iSCSI Multipathing" GUI after everything else is setup. i can't find a way to do this. is this now possible? i think the iSCSI Multipathing documentation could be improved by describing an example IP setup for this.

thanks a lot
Users mailing list

Reply via email to