From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <d.csapak@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 B7C0E7EAE2 for <pve-devel@lists.proxmox.com>; Thu, 11 Nov 2021 12:47:02 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A68FAAB4D for <pve-devel@lists.proxmox.com>; Thu, 11 Nov 2021 12:46:32 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (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 firstgate.proxmox.com (Proxmox) with ESMTPS id 17AC8AB3E for <pve-devel@lists.proxmox.com>; Thu, 11 Nov 2021 12:46:32 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id D9507421A9; Thu, 11 Nov 2021 12:46:31 +0100 (CET) Message-ID: <2389187c-5513-b21a-c8f5-90a7dc4760db@proxmox.com> Date: Thu, 11 Nov 2021 12:46:31 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:95.0) Gecko/20100101 Thunderbird/95.0 Content-Language: en-US To: Fabian Ebner <f.ebner@proxmox.com>, pve-devel@lists.proxmox.com References: <20211108130758.160914-1-d.csapak@proxmox.com> <2dfd72a6-12b8-3549-bd28-25c8c49092b5@proxmox.com> From: Dominik Csapak <d.csapak@proxmox.com> In-Reply-To: <2dfd72a6-12b8-3549-bd28-25c8c49092b5@proxmox.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 2.223 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -3.999 Looks like a legit reply (A) 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 cluster/manager v2] add scheduling daemon for pvesr + vzdump (and more) 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> X-List-Received-Date: Thu, 11 Nov 2021 11:47:02 -0000 On 11/11/21 12:35, Fabian Ebner wrote: > Am 08.11.21 um 14:07 schrieb Dominik Csapak: >> with this series, we implement a new daemon (pvescheduler) that takes >> over from pvesrs' systemd timer (original patch from thomas[0]) and >> extends it with a generic job handling mechanism >> >> then i convert the vzdump cron jobs to these jobs, the immediate >> gain is that users can use calendarevent schedules instead of >> dow + starttime >> > > There's a problem for mixed-version clusters: > > If I edit/create a cluster-wide job (or job for another node) while > running the new version, a node that doesn't have the pvescheduler yet, > won't see that job anymore. > yes, that's a known issue and will be features in the release notes. basically, until all nodes are updated, you should not touch the backup jobs via a webinterface on a new node