[ovirt-users] Migrate Hosted Engine to new iSCSI san with new IP/Target

[Simone Tiraboschi]

Hi Bill,
in order to provide HA, the hosted-engine HA services should be able to
autonomously connect the shared storage from each hosted-engine involved
host.

The storage configuration is in /etc/ovirt-hosted-engine/hosted-engine.conf

So:
1. set global-maintenance mode
2. shutdown the engine VM
3. manually edit /etc/ovirt-hosted-engine/hosted-engine.conf on each host
4. here we have a delicate point: on restart ovirt-ha-agent will connect
the new storage server but the issue is that it will not call
disconnectStorageServer on the previously connected one so you will
probably end with VDSM that has still a reference also to the previous
location and this can cause timeouts and so on if not available. Restarting
VDSM is probably not enough since the the symlinks under /var/run/vdsm will
not be refreshed if they are already there (  ) so I'd suggest to reboot
all the hosts to avoid any possible issue.
5. exits global maintenance mode

On Tue, Feb 2, 2016 at 6:12 AM, bill at taney.com <bill at taney.com> wrote:

> In a hosted-engine deployment has anyone had to migrate to a new iSCSI
> SAN? I can not figure out how to move the engine(s) to a new iSCSI target..
> The SAN’s can fully replicate to one another and I can move the LUN to the
> other device but don’t see how to stop the engine and change the settings
> for it’s iSCSI target to another IP/IQN. Any direction would be greatly
> appreciated - I am looking for any method to get this done, we have to
> retire the old SAN - Thanks.
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20160202/270d84bd/attachment-0001.html>