Re: [ovirt-users] Best practices for LACP bonds on oVirt

On Tue, Jul 4, 2017 at 5:50 AM, Vinícius Ferrão <ferrao(a)if.ufrj.br <mailto:ferrao@if.ufrj.br>> 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: https://bugzilla.redhat.com/show_bug.cgi?id=1193961 <https://bugzilla.redhat.com/show_bug.cgi?id=1193961> 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. See: https://bugzilla.redhat.com/show_bug.cgi?id=1149579