all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Kevin Schneider <k.schneider@proxmox.com>
Subject: Re: [pve-devel] [PATCH docs 1/7] pvecm: drop notes about old version incompatibilities
Date: Mon, 12 May 2025 14:01:18 +0200	[thread overview]
Message-ID: <d8a25613-d398-4753-ae6f-72c877c61e3f@proxmox.com> (raw)
In-Reply-To: <c8cb4433-0c3d-4208-ade9-bb7dd5fcee8f@proxmox.com>

Am 07.05.25 um 17:22 schrieb Kevin Schneider:
> On 29.04.25 15:57, Aaron Lauterer wrote:
>> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
>> ---
>>   pvecm.adoc | 12 ------------
>>   1 file changed, 12 deletions(-)
>>
>> diff --git a/pvecm.adoc b/pvecm.adoc
>> index 18f7389..47e42e2 100644
>> --- a/pvecm.adoc
>> +++ b/pvecm.adoc
>> @@ -77,18 +77,6 @@ Requirements
>>   * Online migration of virtual machines is only supported when nodes have CPUs
>>     from the same vendor. It might work otherwise, but this is never guaranteed.
>>   
>> -NOTE: It is not possible to mix {pve} 3.x and earlier with {pve} 4.X cluster
>> -nodes.
>> -
>> -NOTE: While it's possible to mix {pve} 4.4 and {pve} 5.0 nodes, doing so is
>> -not supported as a production configuration and should only be done temporarily,
>> -during an upgrade of the whole cluster from one major version to another.
>> -
>> -NOTE: Running a cluster of {pve} 6.x with earlier versions is not possible. The
>> -cluster protocol (corosync) between {pve} 6.x and earlier versions changed
>> -fundamentally. The corosync 3 packages for {pve} 5.4 are only intended for the
>> -upgrade procedure to {pve} 6.0.
>> -
>>   
>>   Preparing Nodes
>>   ---------------
> 
>   In 8.2 we modernized the handling of host keys for SSH connections 
> between cluster by moving them onto the cluster filesystem. We also 
> introduced symlinks for the ceph.client.admin.keyring and ceph.conf 
> files. So =<8.1 and =>8.3 are not compatible.
> 
> For the documentation it would probably the best to either include 
> recent limitations or clearly state, that nodes should only have a 
> single dot release difference between each other  and give examples like:
> 
> Perfect: All Nodes are up to date
> 
> Good: 8.1 and 8.2
> 
> Bad: 8.1 and 8.3 ; 8.1 and 8.2 and 8.3
That's not general true though, the following is:
- we try hard to always allow forward-upgrades.
- in the end all nodes should run the same version.

That means, admins should upgrade all nodes, one after another, and
if the–whyever that is–did not do that they cannot have expect full
compatibility no matter what the version difference is but can expect
that upgrading the older node(s) will work and will make the cluster
fully compatible again.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

  reply	other threads:[~2025-05-12 12:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-29 13:57 [pve-devel] [PATCH docs, manager 0/7] add and expand on cluster recommendations Aaron Lauterer
2025-04-29 13:57 ` [pve-devel] [PATCH docs 1/7] pvecm: drop notes about old version incompatibilities Aaron Lauterer
2025-05-07 15:22   ` Kevin Schneider
2025-05-12 12:01     ` Thomas Lamprecht [this message]
2025-04-29 13:57 ` [pve-devel] [PATCH docs 2/7] pvecm: add anchor for cluster requirements Aaron Lauterer
2025-04-29 13:57 ` [pve-devel] [PATCH docs 3/7] pvecm: add anchor for corosync exernal vote support Aaron Lauterer
2025-04-29 13:57 ` [pve-devel] [PATCH docs 4/7] pvecm: extend cluster Requirements Aaron Lauterer
2025-05-07 15:22   ` Kevin Schneider
2025-05-08 11:54     ` Robin Christ
2025-04-29 13:57 ` [pve-devel] [PATCH docs 5/7] ha-manager: expand requirements Aaron Lauterer
2025-04-29 13:57 ` [pve-devel] [PATCH manager 6/7] ui: cluster create: add recommendations for cluster networks Aaron Lauterer
2025-04-29 13:57 ` [pve-devel] [PATCH manager 7/7] ui: guest import: make sure an external link has target _blank Aaron Lauterer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d8a25613-d398-4753-ae6f-72c877c61e3f@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=k.schneider@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal