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 89F626C3BE for ; Sun, 28 Mar 2021 17:12:45 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id F32D0E544 for ; Sun, 28 Mar 2021 17:12:14 +0200 (CEST) Received: from kvmformation3.odiso.net (globalOdiso.M6Lille.odiso.net [89.248.211.242]) by firstgate.proxmox.com (Proxmox) with ESMTP id E478EE475 for ; Sun, 28 Mar 2021 17:12:11 +0200 (CEST) Received: by kvmformation3.odiso.net (Postfix, from userid 0) id B2F182E96F; Sun, 28 Mar 2021 17:12:04 +0200 (CEST) From: Alexandre Derumier To: pve-devel@lists.proxmox.com Date: Sun, 28 Mar 2021 17:11:57 +0200 Message-Id: <20210328151203.2063706-1-aderumier@odiso.com> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 1 AWL -0.172 Adjusted score from AWL reputation of From: address HEADER_FROM_DIFFERENT_DOMAINS 0.25 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.4 Relay HELO differs from its IP's reverse DNS NO_DNS_FOR_FROM 0.379 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 qemu-server 0/6] cloudinit pending behaviour change 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, 28 Mar 2021 15:12:45 -0000 Hi, This is an attempt to cleanup current behaviour of cloudinit online changes. Currently, we setup cloudinit options as pending, until we generate the config drive. This is not 100% true, because some option like vm name, nic mac address can be changed, without going to pending, so user can't known if it need to regenerated it. Also, some can are very difficult to handle, if you hotplug a nic but it's failing,so pending, then you defined an ipconfig, and then you revert hotplug. or if you delete a nic, the ipconfig is no more displayed in the gui. So, instead of setting cloudinit values in pending, this patch serie copy the current cloudinit config in a new section [special:cloudinit], when the config drive is generated. This is only an hint, to allow to display diff between the generated cloudinit drive, and the current vm config. A new specific cloudinit config api is added too, merging ipaddrX && netX mac in same field, and displaying the diff between current and generated config. Changelog V1: - use [special:cloudinit] instead [CLOUDINIT] for section - delete config section on drive removal - config api: move code to new PVE::QemuServer::Cloudinit::get_pending_config - config api: add "qm cloudinit pending" cli - add update api to regenerate drive with 1 api call - add cloudinit hotplug option Alexandre Derumier (6): cloudinit: add cloudinit section for current generated config. generate cloudinit drive on offline plug cloudinit: make cloudnit options fastplug api2: add cloudinit config api api2: add cloudinit_update add cloudinit hotplug PVE/API2/Qemu.pm | 117 ++++++++++++++++++++++++++++++++++++ PVE/CLI/qm.pm | 2 + PVE/QemuServer.pm | 104 +++++++++++++++++++++----------- PVE/QemuServer/Cloudinit.pm | 102 +++++++++++++++++++++++++++++++ 4 files changed, 291 insertions(+), 34 deletions(-) -- 2.20.1