[pve-devel] [PATCH v2 qemu-server 00/16] migration: split phases

[Alexandre DERUMIER]

>>
>>Fabian is also looking into external migrate, posted a initial proof-of-concept 
>>last week[0]. The currently planned design is roughly: 

>>* having "remotes", which can be any nodes, or a whole cluster 
>>* we want to use the new API Token mechanisms for remotes - this allows 
>>nice integration where one can also revoke access from another node to 
>>theirs. 
>>* migration tunnel will for use WebSocket for secure data transfer, this 
>>allows to do a HTTPS request over API then switch protocol (i.e., what 
>>HTTP/2 would get us with multiplexing but not as nice) 

Oh, that's great ! I totally miss it . I'm curious to see performance of websocket for such big data transfert.

(BTW, I'm still dreaming of a multi-cluster pve-manager ;)


>>We may naturally still want to see if some patches of the split up make 
>>sense to apply now. 
>>Just that you know, not that you invest too much time in this now :-) 

ok, thanks.  (I had a need a work for this week, that's why I hve sent it)

I'll test the POC tomorrow. 



----- Mail original -----
De: "Thomas Lamprecht" <t.lamprecht at proxmox.com>
À: "pve-devel" <pve-devel at pve.proxmox.com>, "Alexandre Derumier" <aderumier at odiso.com>
Envoyé: Lundi 9 Mars 2020 16:39:44
Objet: Re: [pve-devel] [PATCH v2 qemu-server 00/16] migration: split phases

On 3/9/20 4:24 PM, Alexandre Derumier wrote: 
> Hi, 
> This is an update of last year patch series 
> https://pve.proxmox.com/pipermail/pve-devel/2019-April/036766.html 
> 
> This is splitting migration code of differents phases in smaller subs. 
> Will be usefull to implement migrate external (I'll work on it again soon) 

Hi, 

Fabian is also looking into external migrate, posted a initial proof-of-concept 
last week[0]. The currently planned design is roughly: 

* having "remotes", which can be any nodes, or a whole cluster 
* we want to use the new API Token mechanisms for remotes - this allows 
nice integration where one can also revoke access from another node to 
theirs. 
* migration tunnel will for use WebSocket for secure data transfer, this 
allows to do a HTTPS request over API then switch protocol (i.e., what 
HTTP/2 would get us with multiplexing but not as nice) 

We may naturally still want to see if some patches of the split up make 
sense to apply now. 

Just that you know, not that you invest too much time in this now :-) 

[0]: https://pve.proxmox.com/pipermail/pve-devel/2020-March/042121.html