I had originally setup my cluster following this older guide at https://blogs.ovirt.org/2018/02/up-and-running-with-ovirt-4-2-and-gluster-storage/ and the fqdn steps did not exist at that time. After deployment I then followed steps to add gluster network and set that network as storage and migration. What is the difference between what I did and the new method gdeploy uses? If my gluster config is using hostnames on the management network subnet but the gluster network is set for gluster and migration traffic what happens?

On Wed, Oct 16, 2019 at 12:05 PM Jayme <jaymef@gmail.com> wrote:

Is there a way to fix this on a hci deployment which is already in operation? I do have a separate gluster network which is chosen for migration and gluster network but when I originally deployed I used just one set of host names which resolve to management network subnet.

I appear to have a situation where gluster traffic may be going through both networks in seeing what looks like gluster traffic on both the gluster interface and ovirt management.

On Wed, Oct 16, 2019 at 11:34 AM Stefano Stagnaro <stefanos@prismatelecomtesting.com> wrote:
Thank you Simone for the clarifications.

I've redeployed with both management and storage FQDNs; now everything seems to be in its place.

I only have a couple of questions:

1) In the Gluster deployment Wizard, section 1 (Hosts) and 2 (Additional Hosts) are misleading; should be renamed in something like "Host Configuration: Storage side" / "Host Configuration: Management side".

2) what is the real function of the "Gluster Network" cluster traffic type? What it actually does?

Thanks,
Stefano.
_______________________________________________
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/NTNXPJMOZEYVHIZV2SJXXOVXMXCXS2XP/