ONN v4.2.3 Hosted Engine Deployment - Auto addition of Gluster Hosts

The new Ovirt Node installation script in v4.2.3 automatically adds the gluster hosts after initial hosted engine setup. This caused major problems as I had used different FQDNs on a different VLAN to initially setup my gluster nodes [to isolate storage traffic] - but then put them onto the "ovirtmgmt" network. Because they were gluster nodes - I could not remove them from the ovirtmgmt network to re-install on the proper management VLAN. I recommend removing the auto-installation of the other gluster nodes - or at least provide an option to decline the automatic addition of the other nodes.

On Sat, May 12, 2018 at 9:33 AM, <glenn.farmer@netfortris.com> wrote:
The new Ovirt Node installation script in v4.2.3 automatically adds the gluster hosts after initial hosted engine setup. This caused major problems as I had used different FQDNs on a different VLAN to initially setup my gluster nodes [to isolate storage traffic] - but then put them onto the "ovirtmgmt" network. Because they were gluster nodes - I could not remove them from the ovirtmgmt network to re-install on the proper management VLAN.
I recommend removing the auto-installation of the other gluster nodes - or at least provide an option to decline the automatic addition of the other nodes.
It should let you specify an address on gluster subnet and one on management one for each host. Please see https://bugzilla.redhat.com/show_bug.cgi?id=1466132#c3
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org
participants (2)
-
glenn.farmer@netfortris.com
-
Simone Tiraboschi