The correct way to allow hosted engine to use other available gluster peers in case of failure of the specified peer is to pass the –config-append option during setup as described https://ovirt.org/develop/release-management/features/sla/self-hosted-engine-gluster-support/
If you want to change that now, then just edit the file /etc/ovirt-hosted-engine/hosted-engine.conf on all hosts and add the following line: mnt_options=backup-volfile-servers=host02:host03 However note that for any new hosted engine deployments, the file has to be manually edited. On Wed, Jul 4, 2018 at 4:51 PM Liebe, André-Sebastian <[email protected]> wrote: > > Well, I though this wouldn’t be supported at the moment. > > But I seriously doubt changing this in engine’s SQL database will be a good > idea at all, since the way hosted-engine’s configuration is shared across > each node (/etc/ovirt-hosted-engine/hosted-engine.conf, > /var/lib/ovirt-hsoted-engine-ha, configuration inside hosted-engine’s storage > domain: hosted-engine.metadata) > > > > I had hoped hosted-engine or hosted-engine-setup cli could be extended to > support this use case. I’m willing to help out testing any (manual) procedure > to get this implemented (e.g. undeploy hosted-engine on two of three nodes, > make changes to hosted-engine.metadata, hosted-engine.conf, start/stop > hosted-engine, run SQL commands inside engine) > > > > Sincerely > > André > > > > Von: Renout Gerrits [mailto:[email protected]] > Gesendet: Mittwoch, 4. Juli 2018 12:04 > An: Liebe, André-Sebastian > Cc: Gobinda Das; Alex K; users > Betreff: Re: [ovirt-users] Re: hyperconverged cluster - how to change the > mount path? > > > > unsupported, make backups, use at your own risk etc... > > > > you could update the db if you can't put the storage domain into maintenance > > after that put your hosts into maintenance and out again to remount > > > > find the id of the sd you want to update with: > > engine=# select * from storage_server_connections; > > > > ensure you have to correct id, the following should point to the old mount > point: > > engine=# select connection from storage_server_connections where id='<id > from output above>'; > > > > next update your db > > engine=# update storage_server_connections set connection='<your new mount > point' where id='<id from output above>'; > > > > > > > > On Wed, Jul 4, 2018 at 9:13 AM, Liebe, André-Sebastian > <[email protected]> wrote: > > Yeah, sorry that doesn’t work. > > I can’t set hosted_storage (storage domain where hosted engine runs on) into > maintenance mode to being able to edit it. > > > > André > > > > Von: Gobinda Das [mailto:[email protected]] > Gesendet: Montag, 2. Juli 2018 09:00 > An: Alex K > Cc: Liebe, André-Sebastian; users > Betreff: Re: [ovirt-users] Re: hyperconverged cluster - how to change the > mount path? > > > > You can do it by using "Manage Domain" option from Starage Domain. > > > > On Sun, Jul 1, 2018 at 7:02 PM, Alex K <[email protected]> wrote: > > The steps roughly would be to put that storage domain in maintenance then > edit/redefine it. You have the option to set gluster mount point options for > the redundancy part. No need to set dns round robin. > > > > Alex > > > > On Sun, Jul 1, 2018, 13:29 Liebe, André-Sebastian <[email protected]> > wrote: > > Hi list, > > I'm looking for an advice how to change the mount point of the hosted_storage > due to a hostname change. > > When I set up our hyperconverged lab cluster (host1, host2, host3) I > populated the mount path with host3:/hosted_storage which wasn't very clever > as it brings in a single point of failure (i.e. when host3 is down). > So I thought adding a round robin dns/hosts entry (i.e. gluster1) for host 1 > to 3 and changing the mount path would be a better idea. But the mount path > entry is locked in web gui and I couldn't find any hint how to change it > manually (in database, shared and local configuration) in a consistent way > without risking the cluster. > So, is there a step by step guide how to achieve this without reinstalling > (from backup)? > > > Sincerely > > André-Sebastian Liebe > Technik / Innovation > > gematik > Gesellschaft für Telematikanwendungen der Gesundheitskarte mbH > Friedrichstraße 136 > 10117 Berlin > Telefon: +49 30 40041-197 > Telefax: +49 30 40041-111 > E-Mail: [email protected] > www.gematik.de > ___________________________________________ > Amtsgericht Berlin-Charlottenburg HRB 96351 B > Geschäftsführer: Alexander Beyer > _______________________________________________ > Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > 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/[email protected]/message/B2R6G3VCK545RKT5BMAQ5EXO4ZFJSMFG/ > > > _______________________________________________ > Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > 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/[email protected]/message/QKNPBUXPIHNYN2NT63KUCYZOBZO5HUOL/ > > > > > > -- > > Thanks, > > Gobinda > > > _______________________________________________ > Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > 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/[email protected]/message/SQJGVJLSRHAXTX6EFU4Z6GPO5IN565CD/ > > > > _______________________________________________ > Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > 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/[email protected]/message/YZSKCK6LGC7POYMELRQLJOURIRIDIMQZ/ _______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/N2CDSUYQT2HLWHHPN7Z5ERPJO5NURIBL/
