From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <pbs-devel-bounces@lists.proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id EC7C01FF16E for <inbox@lore.proxmox.com>; Mon, 17 Mar 2025 13:12:00 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id AEDDA1876; Mon, 17 Mar 2025 13:11:50 +0100 (CET) Message-ID: <9bdf3889-b288-458a-bfe6-5ac9099971de@proxmox.com> Date: Mon, 17 Mar 2025 13:11:46 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Dominik Csapak <d.csapak@proxmox.com>, Proxmox Backup Server development discussion <pbs-devel@lists.proxmox.com> References: <20250310170125.528732-1-c.ebner@proxmox.com> <66676a8d-15fd-4a2c-b80b-19564cc268df@proxmox.com> <1d56786a-408b-4bd1-841e-5515cd1df15e@proxmox.com> <69533b86-7d14-41a5-8355-9eade40301b9@proxmox.com> Content-Language: en-US, de-DE From: Christian Ebner <c.ebner@proxmox.com> In-Reply-To: <69533b86-7d14-41a5-8355-9eade40301b9@proxmox.com> X-SPAM-LEVEL: Spam detection results: 0 AWL 0.031 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pbs-devel] [PATCH proxmox-backup 1/2] fix: ui: sync job: switch rate limit based on sync direction X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion <pbs-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pbs-devel>, <mailto:pbs-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pbs-devel/> List-Post: <mailto:pbs-devel@lists.proxmox.com> List-Help: <mailto:pbs-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel>, <mailto:pbs-devel-request@lists.proxmox.com?subject=subscribe> Reply-To: Proxmox Backup Server development discussion <pbs-devel@lists.proxmox.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: pbs-devel-bounces@lists.proxmox.com Sender: "pbs-devel" <pbs-devel-bounces@lists.proxmox.com> On 3/17/25 12:56, Dominik Csapak wrote: > On 3/17/25 11:32, Christian Ebner wrote: >> On 3/17/25 11:07, Dominik Csapak wrote: >>> High level comment: >>> >>> I know it's preexisting, bu does it even make sense to have a 'rate- >>> in' and 'rate-out' for sync >>> jobs? would it not make more sense to have a single 'rate' parameter >>> and apply it to both >>> directions? >> >> You mean only as additional parameter for the api endpoint for sync >> job config creation and update? Or as parameter for the sync job >> config itself? >> >> The former might be the better option, and one can check if both rate >> and rate-in/out were set and abort with error in that case or abort >> with error if a rate-in was configured for a push or rate-out for a pull? >> > > i had actually imagined 3 options for the sync job config > rate: limits both in/out > rate-in/out: precedence over rate, limits the respective direction > > and only expose the 'rate' option on the ui Okay, that makes sense, but the issue I see there is that per-existing rate limits are not shown in the UI anymore, as the `rate` field is now used, while the config has the explicit `rate-in/out` set. So this would need some merging first, or am I missing something? _______________________________________________ pbs-devel mailing list pbs-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel