HostedEngine migration from ovirt1:/engine to gluster1:/engine (new ip)
Hello Community, I have added new interfaces and bonded them in order to split storage from oVirt traffic and I have one last issue. In Storage -> Storage Domains , I have the "hosted_storage" domain that is pointing to the old "ovirt1.localdomain:/engine" instead of "gluster1:/engine". I have managed to reconfigure the ha agent to bring the new storage , but it seems the engine mounts the old gluster path and this causes problem with the ha agent . How can I edit the "hosted_storage" in a safe manner to point to "gluster1:/engine" and mount options of "backup-volfile-servers=gluster2:ovirt3". Should I edit the DB ? P.S.: My google skills did not show any results on this topic and thus I'm raising it to the mail list.Thanks in advance. Best Regards,Strahil Nikolov
Shouldn't this be done by restoring the engine? Initial engine host and storage parameters are collected while doing the restore. It might be a bit far stretched, but at least be an automated repeatable experience. Are there really procedures where you manipulate the DHW directly? I never saw a reference in the documentation.
On May 13, 2019 1:42:53 PM GMT+03:00, Andreas Elvers <andreas.elvers+ovirtforum@solutions.work> wrote:
Shouldn't this be done by restoring the engine? Initial engine host and storage parameters are collected while doing the restore. It might be a bit far stretched, but at least be an automated repeatable experience.
Are there really procedures where you manipulate the DHW directly? I never saw a reference in the documentation. _______________________________________________ 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/5JYINPWJINWQPI...
Updating the base is faster than restoring the engine. I'm avoiding the restore, as I cannot find a dummy-style instruction for restore and with my luck - I will definately hit a wall. In my case this is the final piece left and DB manipulation is far easier . Of course , I wouldn't manipulate the DB on a production site - but for a lab is acceptable. Best Regards, Strahil Nikolov
participants (2)
-
Andreas Elvers -
Strahil Nikolov