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 721FD1FF168 for <inbox@lore.proxmox.com>; Tue, 26 Nov 2024 11:36:59 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id CECDC2C839; Tue, 26 Nov 2024 11:36:57 +0100 (CET) Date: Mon, 25 Nov 2024 15:09:48 +0000 To: Stefan Hanreich <s.hanreich@proxmox.com> In-Reply-To: <cc37ab90-8c25-4316-87e3-27a4167406e4@proxmox.com> 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> <cc37ab90-8c25-4316-87e3-27a4167406e4@proxmox.com> X-Mailman-Approved-At: Tue, 26 Nov 2024 11:36:57 +0100 MIME-Version: 1.0 Message-ID: <mailman.692.1732617417.391.pve-devel@lists.proxmox.com> List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Post: <mailto:pve-devel@lists.proxmox.com> From: Andrew via pve-devel <pve-devel@lists.proxmox.com> Precedence: list Cc: Andrew <andrew@apalrd.net>, "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com> X-Mailman-Version: 2.1.29 X-BeenThere: pve-devel@lists.proxmox.com List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> 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/> Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> Subject: Re: [pve-devel] [PATCH ifupdown2 1/1] Correctly handle IPv6 addresses in vxlan Content-Type: multipart/mixed; boundary="===============1855130221057731051==" Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com> --===============1855130221057731051== Content-Type: message/rfc822 Content-Disposition: inline Return-Path: <andrew@apalrd.net> X-Original-To: pve-devel@lists.proxmox.com Delivered-To: pve-devel@lists.proxmox.com Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 91F52C9772 for <pve-devel@lists.proxmox.com>; Mon, 25 Nov 2024 16:19:08 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7BFED172C9 for <pve-devel@lists.proxmox.com>; Mon, 25 Nov 2024 16:19:08 +0100 (CET) Received: from mail-41103.protonmail.ch (mail-41103.protonmail.ch [185.70.41.103]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for <pve-devel@lists.proxmox.com>; Mon, 25 Nov 2024 16:19:07 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apalrd.net; s=protonmail; t=1732547394; x=1732806594; bh=cDp6NXY1JYftFtaT3HxD2d/JMavYJ4l2tTP96zcivkw=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=xQDKPe6ax1EknWriX5hlBWN9ix0QDphLHwFQe0yyKJS0CQl9t/gwmNy/11j9qMZ0D WEdr8vPRo7AcJyOR6DapYpDstSTRY2qfITVKlOAwj7RE2yz5Y9BnR6Dfm8ui1sWj5s ZS4GAsA6u09kUlyKZ9kt+JcwKXdgztvQAytZYgB3to5ymsjQZtfVRW/fl6j166SkRA tm8GorOZnIE8Zkn41hcI9qdwKnQTEFEy8gSe0H2ENiaJnBqpOlyfDGH1vfWkaJfR7A h1LNnuMKbrlj5fO45KiUBpK4NdOLg2qu7b2rL9fuZJgC4hp7VfwiM7akmNyClovenv 4CyMd6ka2dckA== Date: Mon, 25 Nov 2024 15:09:48 +0000 To: Stefan Hanreich <s.hanreich@proxmox.com> From: Andrew <andrew@apalrd.net> Cc: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>, "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com> Subject: Re: [PATCH ifupdown2 1/1] Correctly handle IPv6 addresses in vxlan Message-ID: <2DB93EBD-8A9D-4CB9-8992-9A9C85742505@apalrd.net> In-Reply-To: <cc37ab90-8c25-4316-87e3-27a4167406e4@proxmox.com> 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> <cc37ab90-8c25-4316-87e3-27a4167406e4@proxmox.com> Feedback-ID: 38364418:user:proton X-Pm-Message-ID: 8ec90322dd8305e68cc08fec945d79d67f65eeec MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL 0.000 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_PASS -0.1 DMARC pass policy SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record X-Mailman-Approved-At: Tue, 26 Nov 2024 11:36:57 +0100 Hello, Yes, I=E2=80=99ve signed the CLA.=20 You=E2=80=99re welcome to take it over to fix the style issues.=20 At least for Trixie it seems like PVE staying on ifupdown2 would make sense= , given how tightly integrated it=E2=80=99s syntax is with SDN. Andrew > On Nov 25, 2024, at 05:25, Stefan Hanreich <s.hanreich@proxmox.com> wrote= : >=20 >=20 > 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) >>=20 >> That's mean maintain both syntax, or plan a config update, >> between 2 majors pve releases. Not a big deal. >=20 > 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]. >=20 > 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. >=20 >> 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,...) >=20 > 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. >=20 >=20 > 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. >=20 > [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 >=20 --===============1855130221057731051== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel --===============1855130221057731051==--