[pve-devel] Proxmox VE developer release for Debian "jessie"
Stefan Priebe - Profihost AG
s.priebe at profihost.ag
Fri Mar 6 15:02:54 CET 2015
+1
Stefan
Excuse my typo sent from my mobile phone.
Am 06.03.2015 um 13:31 schrieb Alexandre DERUMIER <aderumier at odiso.com>:
>>> 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)
>
>
>
> ----- 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 13:02:20
> Objet: Re: [pve-devel] Proxmox VE developer release for Debian "jessie"
>
>> for the corosync upgrade path,
>>
>> I wonder if we could provide corosync2 packages for wheezy,
>>
>> upgrade all wheezy servers to corosync2
>>
>> then rolling upgrade to jessie with vm migrations.
>>
>> What do you think about it ?
>
>
> How does that help exactly? You still need to update corosync on all nodes at
> the same time?
>
> _______________________________________________
> pve-devel mailing list
> pve-devel at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-devel/attachments/20150306/900d4667/attachment.htm>
More information about the pve-devel
mailing list