From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
	by lore.proxmox.com (Postfix) with ESMTPS id 8E6B11FF15F
	for <inbox@lore.proxmox.com>; Mon, 18 Nov 2024 14:32:37 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id 2D28D10C7A;
	Mon, 18 Nov 2024 14:32:43 +0100 (CET)
Message-ID: <e4d215eb-e3e9-4124-9907-3eb077eac14b@proxmox.com>
Date: Mon, 18 Nov 2024 14:32:40 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
References: <20241115120937.169342-1-s.hanreich@proxmox.com>
 <20241115120937.169342-7-s.hanreich@proxmox.com>
 <cfd24b51-431c-401b-a116-eb0c683807b1@proxmox.com>
 <cabba697-8b98-414f-844e-42003631cf59@proxmox.com>
 <7f76e6b0-eba4-4101-9c05-22e8eda93381@proxmox.com>
 <5264d9f3-4b32-4d8e-afcd-1901994286e2@proxmox.com>
Content-Language: en-US
From: Stefan Hanreich <s.hanreich@proxmox.com>
In-Reply-To: <5264d9f3-4b32-4d8e-afcd-1901994286e2@proxmox.com>
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.657 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DMARC_MISSING             0.1 Missing DMARC policy
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
Subject: Re: [pve-devel] [PATCH pve-firewall v4 6/9] api: load sdn ipsets
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>



On 11/18/24 14:23, Thomas Lamprecht wrote:
> Am 18.11.24 um 12:38 schrieb Thomas Lamprecht:
>> I'll take a short look if it's easily possible to add a sane migration path
>> at pmxcfs level, handling this transparently, otherwise we'll have to add
>> some compat handling at higher levels.
> 
> doing this directly in pmxcfs is not trivial as our link-plug is made for
> adding links at the top-level, besides inode updates from other members
> running older code would need to take special care, so this route is rather
> unfeasible as of now.
> 
> I will just add some fallback code in pve-network and be done, for the firewall
> uses cases this is a new feature anyway and thus needs all new package versions
> anyway to be expected to work.

Too bad to hear, if there's anything I can do wrt this don't hesitate to
ping me.


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