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 B0CD27516E for ; Mon, 12 Jul 2021 00:47:46 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A7A61EB5F for ; Mon, 12 Jul 2021 00:47:16 +0200 (CEST) Received: from kvmformation3.odiso.net (globalOdiso.M6Lille.odiso.net [89.248.211.242]) by firstgate.proxmox.com (Proxmox) with ESMTP id 19D78EB0B for ; Mon, 12 Jul 2021 00:47:15 +0200 (CEST) Received: by kvmformation3.odiso.net (Postfix, from userid 0) id A8B2BCF6; Mon, 12 Jul 2021 00:47:08 +0200 (CEST) From: Alexandre Derumier To: pve-devel@lists.proxmox.com Date: Mon, 12 Jul 2021 00:46:58 +0200 Message-Id: <20210711224707.63089-1-aderumier@odiso.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 1.061 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% HEADER_FROM_DIFFERENT_DOMAINS 0.001 From and EnvelopeFrom 2nd level mail domains are different KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods KHOP_HELO_FCRDNS 0.399 Relay HELO differs from its IP's reverse DNS NO_DNS_FOR_FROM 0.001 Envelope sender has no MX or A DNS records SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Subject: [pve-devel] [PATCH v2 qemu-server 0/9] RFC: sdn: add ipam support 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: Sun, 11 Jul 2021 22:47:46 -0000 Hi, This is an RFC to implement ipam support on qemu-server. This don't change the cloud-init current working. As I need to manage pending ip registration configuration, to follow the pending netX interfaces. I have added ip,ip6,gw,gw6 field to netX interfaces options. (same than LXC). (as current ipconfigX pending, is pending cloudinit generation) so the workflow is: --> update netX=...,ip=.... --> ip is registered as pending --> hotplug/coldplug succesful ---> pending ip replace current conf oldip ---->the ip set in cloudinit pending ipconfigX ------> cloudinit regeneration ---> ipconfigX is remove from pending As documentation said than ipconfigX is for cloudinit config, I think it could be ok. Some users could use the sdn features without cloudinit(allow some subnets only, and autogenerate firewall ipfilter). Also, for ipam, I need bridge && mac from the netX, and ip need to follow pending states of the nic. Changelog v2: - rebase on last master / proxmox7 - fix handling errors when multiple nics are hotplugged at same time - keep ip address in ipam if snapshots reference it - only update dns when pending ip is apply (need new pve-network patch) - implement snapshot rollback/delete - implement vm create/destroy todo : implement backup restore Alexandre Derumier (9): add ipam module add print_ipconfig add ip options to netdescr ipam : add update/delete support ipam : add revert ip support ipam : add snapshot rollback support ipam : add snaphot delete support ipam : add create vm support ipam : add destroy vm support PVE/API2/Qemu.pm | 56 +++++++++- PVE/QemuConfig.pm | 32 ++++++ PVE/QemuServer.pm | 228 ++++++++++++++++++++++++++++++++++++++++ PVE/QemuServer/Ipam.pm | 141 +++++++++++++++++++++++++ PVE/QemuServer/Makefile | 1 + 5 files changed, 457 insertions(+), 1 deletion(-) create mode 100644 PVE/QemuServer/Ipam.pm -- 2.30.2