From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 6374764090 for ; Mon, 5 Oct 2020 17:21:14 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 478521ECA2 for ; Mon, 5 Oct 2020 17:20:44 +0200 (CEST) Received: from mail-lf1-x134.google.com (mail-lf1-x134.google.com [IPv6:2a00:1450:4864:20::134]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 39AF41EC8B for ; Mon, 5 Oct 2020 17:20:42 +0200 (CEST) Received: by mail-lf1-x134.google.com with SMTP id a9so1967501lfc.7 for ; Mon, 05 Oct 2020 08:20:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=odiso-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=STPnA0XFbcDgurAws7Gwl5fQHDb9HVBiwIJ9Xf3lisg=; b=joKsoqcBsUtmZ8lKRR2MTtz1Nn/gQGwqMOOZTNjNIpHnijWYf4LUq1s2o7sa+v8obz usc4bH3v7zhkka2xEezA30UOHyihRKgt2a5xy17fSICwCruIkwpKdAgMBVOLzVwVlhKG SFmUotvf2S7mPUoIvwZ4FhdBSJYQ+UtTJgLv77LOWN0EzTtt3DJt4UreGdk55BDkFQQT 4YGmmVYc8z3tSJhEHrEGQMncwYQsAW223TW0G7vvvW7KmloHNl01MLOM+ivF/OdKrToh q3KmgJnl/LvVvC9c4zd0D/ibaZLs0uugsuPVEA5fv0fZSzGEBd/v37MzlmuAWegZsy/u /B6g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=STPnA0XFbcDgurAws7Gwl5fQHDb9HVBiwIJ9Xf3lisg=; b=gYHpbPneA+jUuyV+/jhta79vsFI69jaDE5pGaYLrWcQYPzTR72S7pj1HtSf1YXdtRa hBmdsCLSxdNnSRSMgxN+fI4s5AXOQTVPtxJxpkCklAVrrvxUMeDbXwMceY1Kpj0+JJHI GIceT/SuqWRU+4BH9ZJ1zuEONkFJL1b/UUJlOS4+SvRcsU79IYdL9NXKlWUHyru/qB2E 5pJHU5N6PgGRX1WAhnTaf8YE37cqdwjh3vGgyPwSrsO8JGB0U2e77ImPfp/V/B6rGD+R 1O6sKGKD9vLXl6H4R6lbyYACMpls2KLFHVA0TgdTzrC2iYX+tKa/Xrir8ZI1PgNbNHTJ hejw== X-Gm-Message-State: AOAM532ArASDTgqXmbocKL5BDEyFMT32GANcCGlz3B8t0J5BudAKx7n1 J+uX2cx5l3w0alwxQVkmREuL7hr8PIyrPbJjIyFjsoHaL14= X-Google-Smtp-Source: ABdhPJzwmSZW1i1MOUTAQ88lHOa9lQyGJ2D65hAOd693pQ3amw2dobhvZNOd5VoE1FFoKIjGWtPpfR6HTI9F8nx18MY= X-Received: by 2002:a19:7e8d:: with SMTP id z135mr757lfc.158.1601911235509; Mon, 05 Oct 2020 08:20:35 -0700 (PDT) MIME-Version: 1.0 References: <20200827111655.22957-1-f.ebner@proxmox.com> <110ea3a0-4076-96fa-b31b-aca0188ed2bb@proxmox.com> <1844854487.155436.1598619062646.JavaMail.zimbra@odiso.com> In-Reply-To: <1844854487.155436.1598619062646.JavaMail.zimbra@odiso.com> From: Alexandre Aderumier Date: Mon, 5 Oct 2020 17:20:24 +0200 Message-ID: To: Thomas Lamprecht Cc: pve-devel X-SPAM-LEVEL: Spam detection results: 0 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 HTML_MESSAGE 0.001 HTML included in message RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [pve-devel] sdn patches ready for review X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Oct 2020 15:21:14 -0000 Hi, I have send new patch series for pve-network (v10), pve-manager (v6). They need pve-cluster v5 that I have sent last week. I have also send a new poc for pve-container. I have retested all the features subnets/dns/ipams with differents plugins, all seem to working fine. (I'm going to write to test units soon, because it's really take time to do it manually ;) So, now ipam/dns options are setup on zone, you can define same subnets on different zones, pending config are displayed (I'm displaying change in the grid with a new renderer, so maybe it'll need to little bit of polish). I think the gui is easy to use now. I'll rework pve-docs after theses series are applied. Alexandre Le ven. 28 ao=C3=BBt 2020 =C3=A0 14:53, Alexandre DERUMIER a =C3=A9crit : > Hi everybody, > > I think my summer work on sdn is ready for review. > I have implemented subnet/nat/ipam/dns registration. > > I'll stop to add new feature for now, I have planned time in september fo= r > fixes,cleanup. > > Here the different patch series: > > > [pve-devel] [PATCH v7 pve-network 00/21] sdn : add subnets management > https://lists.proxmox.com/pipermail/pve-devel/2020-August/044850.html > > [pve-devel] [PATCH v4 pve-manager 0/8] sdn : add subnets management > https://lists.proxmox.com/pipermail/pve-devel/2020-August/044775.html > > > [pve-devel] [PATCH v4 pve-cluster 0/4] sdn : add subnets management > https://lists.proxmox.com/pipermail/pve-devel/2020-August/044770.html > > [pve-devel] [PATCH v2 pve-docs 0/2] simple zone + subnet/ipam documentati= on > https://lists.proxmox.com/pipermail/pve-devel/2020-August/044874.html > > > > > For testing subnet/ipam in lxc (is really a poc, do not apply) -> > > [pve-devel] [PATCH v2 pve-container] POC : add/del/update ip from > vnet-subnet-ipam > https://lists.proxmox.com/pipermail/pve-devel/2020-August/044781.html > > Currently, if you use a vnet with subnet with registered ipam, and you > keep the ip field empty, it'll auto-assign an ip. > (or you can still defined your own ip, it'll be registered in pam too) > > > _______________________________________________ > pve-devel mailing list > pve-devel@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel > >