From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <t.lamprecht@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 40D607E723 for <pve-devel@lists.proxmox.com>; Wed, 10 Nov 2021 21:42:10 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3429F22292 for <pve-devel@lists.proxmox.com>; Wed, 10 Nov 2021 21:42:10 +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 7F3A422281 for <pve-devel@lists.proxmox.com>; Wed, 10 Nov 2021 21:42:08 +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 4D4BE44BB1 for <pve-devel@lists.proxmox.com>; Wed, 10 Nov 2021 21:42:08 +0100 (CET) Message-ID: <a337ef4d-02ec-162c-209e-9affdb3021f4@proxmox.com> Date: Wed, 10 Nov 2021 21:42:06 +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: Proxmox VE development discussion <pve-devel@lists.proxmox.com>, Dominik Csapak <d.csapak@proxmox.com> References: <20211108130758.160914-1-d.csapak@proxmox.com> From: Thomas Lamprecht <t.lamprecht@proxmox.com> In-Reply-To: <20211108130758.160914-1-d.csapak@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.135 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 SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com, cluster.pm] Subject: [pve-devel] applied-series: [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: Wed, 10 Nov 2021 20:42:10 -0000 On 08.11.21 14:07, Dominik Csapak wrote: > pve-cluster: > > Dominik Csapak (1): > add 'jobs.cfg' to observed files > > data/PVE/Cluster.pm | 1 + > data/src/status.c | 1 + > 2 files changed, 2 insertions(+) > > pve-manager: > > Dominik Csapak (5): > add PVE/Jobs to handle VZDump jobs > pvescheduler: run jobs from jobs.cfg > api/backup: refactor string for all days > api/backup: handle new vzdump jobs > ui: dc/backup: show id+schedule instead of dow+starttime > > Thomas Lamprecht (1): > replace systemd timer with pvescheduler daemon applied series, thanks! It's obv. time to call it a day now as I forgot to apply Dylan's and Aaron's T-b tags, sorry about that, but they certainly assured me and allowed to invest less time here, thanks to both of you testers! I made a few smaller followup on top: bd0af783 ui: form/calendar event: add some more complex examples 90d66ebf ui: form/calendar event: increase width of combobox picker 9569c89b ui: backup job: limit ID to 20 chars for now 3fc5bbc4 ui: backup job: ellipsize read-only ID on edit ae8c5aba ui: backup job: avoid row wrapping due to overly long label @Dominik, please still check the other reply to the followup series: https://lists.proxmox.com/pipermail/pve-devel/2021-November/050863.html And I think now it would be a good time to add that scheduler simulation API call to get the next X actual date-times and calendar event would trigger, which we could use to provide a small button for the users to show them their 10 (or so) next events, at least that functionality from `systemd-analyze calendar <event>` always helps me a lot to reassure my systemd.timer units are going off as planned ^^