[pve-devel] Proxmox VE developer release for Debian "jessie"

[Alexandre DERUMIER]

Maybe:

Build a new empty cluster with jessie, with same storage.cfg,copy ssh keys, 
and allow to do live migration between both cluster.

It should be easy,
we simply need to scp the vm config file to the target host instead move it,
and remove it from source host.

Like this it can be easy to test the new cluster with jessie, and migrate slowly.

What do you think about it ?



----- Mail original -----
De: "aderumier" <aderumier at odiso.com>
À: "dietmar" <dietmar at proxmox.com>
Cc: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Vendredi 6 Mars 2015 18:03:39
Objet: Re: [pve-devel] Proxmox VE developer release for Debian "jessie"

>>You probably need some downtime ... 

so, downtime for the whole cluster ? 
I manage around 800vms....It's impossible for me to manage that with all my customers .... 




----- Mail original ----- 
De: "dietmar" <dietmar at proxmox.com> 
À: "aderumier" <aderumier at odiso.com> 
Cc: "pve-devel" <pve-devel at pve.proxmox.com> 
Envoyé: Vendredi 6 Mars 2015 15:43:32 
Objet: Re: [pve-devel] Proxmox VE developer release for Debian "jessie" 

> On March 6, 2015 at 1:31 PM Alexandre DERUMIER <aderumier at odiso.com> wrote: 
> 
> 
> >>How does that help exactly? You still need to update corosync on all nodes 
> >>at 
> >>the same time? 
> 
> yes, but I don't need to shutdown my vms. 
> 
> If I directly update a node to jessie with corosync2, how can I migrate a vm 
> to this jessie node ? 
> 
> (If corosync1-wheezy-source node - don't speak with corosync2-jessie-target 
> node) 

You probably need some downtime ... 

So I guess what you suggest makes sense, but it requires some work to implement 
it. You would 
need to update several packages: libqb corosync, pve-cluster, ... 
_______________________________________________ 
pve-devel mailing list 
pve-devel at pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel