[pve-devel] Dedicated Migration Network #1177 v2

[Phil Kauffman]

I was able to get this work on my test network.

Right now I believe the issue I am having might stem from using bonding 
mode 6 (balance-alb). It may take some time to verify as I am quite busy 
at the moment.



On 11/22/2016 02:21 AM, Thomas Lamprecht wrote:
> On 11/18/2016 09:12 PM, Phil Kauffman wrote:
>> On 11/18/2016 11:54 AM, Thomas Lamprecht wrote:
>>> Let me hear if you got some new results.
>>> A few people tested this here successfully, so at least basic
>>> functionality should work.
>>
>> Would it be possible for you to send me your network configuration you
>> used for your tests?
>>
>>
>
> Setup: 2 nodes with LAN on eth1
>
> Then I just add a arbitrary but unique IP address (in my case IPv6, but
> IPv4 works just as well) to each node:
>
> Node 1:
> # ip addr add dev eth1 fd0f:38:500:20::1/64
>
>
> Node 2:
> # ip addr add dev eth1 fd0f:38:500:20::2/64
>
>
> Check with
> ping6 IPv6
> or
> ping IPv4
>
> if it worked.
>
> the add ssh keys on this network:
>
> # ssh-keyscan -t rsa fd0f:38:500:20::2 fd0f:38:500:20::1 >>
> /etc/pve/priv/known_hosts
>
> Then do a migration:
>
> # qm migrate 167 due --online 1 --migration_network fd0f:38:500:20::1/64
>
> This ouputs:
>>
>> Nov 22 09:06:19 use dedicated network address for sending migration
>> traffic (fd0f:38:500:20::2)
>> Nov 22 09:06:19 starting migration of VM 167 to node 'due'
>> (fd0f:38:500:20::2)
>> Nov 22 09:06:19 copying disk images
>> Nov 22 09:06:19 starting VM 167 on remote node 'due'
>> Nov 22 09:06:21 starting online/live migration on
>> tcp:[fd0f:38:500:20::2]:60000
>> Nov 22 09:06:21 migrate_set_speed: 8589934592
>> Nov 22 09:06:21 migrate_set_downtime: 0.1
>> Nov 22 09:06:21 set migration_caps
>> Nov 22 09:06:21 set cachesize: 107374182
>> Nov 22 09:06:21 start migrate command to tcp:[fd0f:38:500:20::2]:60000
>> Nov 22 09:06:23 migration speed: 512.00 MB/s - downtime 22 ms
>> Nov 22 09:06:23 migration status: completed
>> Nov 22 09:06:25 migration finished successfully (duration 00:00:07)
>
> or
>
> # qm migrate 167 due --online 1 --migration_network fd0f:38:500:20::1/64
> --migration_type insecure
>
> or set the respective settings in datacenter.cfg
>
> In /etc/network/interfaces it would look like:
>
>> [...]
>> iface eth1 inet6 static
>>     address fd0f:38:500:12::2
>>     netmask  64
>>     accept_ra 0
>
> or IPv4:
>>
>> auto eth1
>> iface eth1 inet static
>>         address  10.10.10.2
>>         netmask  255.255.255.0
>
>
> So simple static network + ssh key scan should be enough. :)
>
> _______________________________________________
> pve-devel mailing list
> pve-devel at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


-- 
Phil Kauffman
Systems Admin
Dept. of Computer Science
University of Chicago
kauffman at cs.uchicago.edu
773-702-3913