Quoting Javier Fontan (jfon...@opennebula.org):
> I haven't tested this but it may work.
>
> When you do a migration the destination host is specified. The host
> name is the same as the one configured in OpenNebula so it will use
> the same network as ssh connections. To use another network you can
> modify the script so the destination host is changed. For example,
> let's asume that the machines have 192.168.1.x for the standard
> service network (ssh) and another network for migrations at 10.0.1.x.
> The node names for these both networks can be the same but adding a
> suffix to the migration network, something like this:
>
> 192.168.1.1 node01
> 10.0.1.1 node01-migration
> 192.168.1.2 node02
> 10.0.1.2 node02-migration
>
> Now you can change the migration script to use the migration network
> as destination host, for example for kvm:
>
> exec_and_log "virsh --connect $LIBVIRT_URI migrate --live $deploy_id
> $QEMU_PROTOCOL://${dest_host}-migration/system" \
> "Could not migrate $deploy_id to $dest_host"
>
> libvirt will use ssh to create the connection to the remote host so
> make sure known_hosts is correctly populated.
Check, sounds good. I'm gonna try it out. I'll let you know if it works.
Gr. Stefan
--
| BIT BV http://www.bit.nl/ Kamer van Koophandel 09090351
| GPG: 0xD14839C6 +31 318 648 688 / i...@bit.nl
_______________________________________________
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
