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 028381FF173 for <inbox@lore.proxmox.com>; Mon, 25 Nov 2024 11:26:06 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 981E0F8E9; Mon, 25 Nov 2024 11:26:16 +0100 (CET) Message-ID: <cc37ab90-8c25-4316-87e3-27a4167406e4@proxmox.com> Date: Mon, 25 Nov 2024 11:25:43 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>, "andrew@apalrd.net" <andrew@apalrd.net> References: <20241008040109.322473-1-andrew@apalrd.net> <20241008040109.322473-2-andrew@apalrd.net> <9045eca45de7aa50fd817fb9221cfa04c524ff19.camel@groupe-cyllene.com> <17214981-4406-4100-AFF6-9F70E12E421B@apalrd.net> <99349e23b9a957cdf81d5bf2fa8c6af9f6b24ad0.camel@groupe-cyllene.com> Content-Language: en-US From: Stefan Hanreich <s.hanreich@proxmox.com> In-Reply-To: <99349e23b9a957cdf81d5bf2fa8c6af9f6b24ad0.camel@groupe-cyllene.com> X-SPAM-LEVEL: Spam detection results: 0 AWL 0.667 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 ifupdown2 1/1] Correctly handle IPv6 addresses in vxlan 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> Cc: "pve-devel@lists.proxmox.com" <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 10/9/24 23:05, DERUMIER, Alexandre wrote: > but we need to be able to not diverge too much from upstream, > if one day (ok that's waiting since 4 years...) an official > support is added by cumulus/nvidia. > (to be honest, the upstream is a lot less active since nvidia have buy > cumulus/mellanox) > > That's mean maintain both syntax, or plan a config update, > between 2 majors pve releases. Not a big deal. yes, it seems a bit tricky, since we'd have to predict what ifupdown2 is doing - but with the current speed of ifupdown2 development, I'm not sure if VXLAN IPv6 support will land anytime soon. There's a similar PR open though in the ifupdown2 github [1]. Since there is currently discussion about moving away from ifupdown2 on debian-devel [2] [3] and the point of contention is not really about IF they will be moving away from ifupdown2 but rather WHAT the replacement will be, we could support our implementation (with possible compatibility patches) while we move to a new network stack. > BTW, I don't have followed the ifupdown-ng project since a long time. > (just follow the early days). Is the project really active and have > almost same features than ifupdown2 ? (netlink support, reload support > with diff of running config,...) Judging from the current discussion on debian-devel, ifupdown-ng doesn't seem to be a candidate for the Debian network stack moving forward. There's some heated discussion between netplan and systemd-networkd, with some (from my perception) preference for systemd-networkd so we'll be monitoring that closely for our trixie release. I'll test this series a bit this week and report back. Would you be interested in sending a v2 afterwards? (particularly wrt to the perl style issues). Otherwise I can also take this patch series over. in any case, have you signed a CLA with us already? Otherwise we cannot include your patches in our repositories. [1] https://github.com/CumulusNetworks/ifupdown2/pull/315 [2] https://lists.debian.org/debian-devel/2024/07/msg00098.html [3] https://lists.debian.org/debian-devel/2024/09/msg00240.html _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel