From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH manager 1/4] api: pools: add limits management
Date: Thu, 11 Apr 2024 11:24:04 +0200 [thread overview]
Message-ID: <3ycjoufdmc2vds3rysuoyvguxz3llmdu77esvkejzkuneum2uw@7rhkj22n672a> (raw)
In-Reply-To: <20240410131316.1208679-11-f.gruenbichler@proxmox.com>
On Wed, Apr 10, 2024 at 03:13:07PM +0200, Fabian Grünbichler wrote:
> allow to set/update limits, and return them when querying individual pools.
>
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
> ---
>
> Notes:
> requires bumped pve-access-control
>
> PVE/API2/Pool.pm | 36 ++++++++++++++++++++++++++++++++----
> 1 file changed, 32 insertions(+), 4 deletions(-)
>
> diff --git a/PVE/API2/Pool.pm b/PVE/API2/Pool.pm
> index 54e744558..26ff7742e 100644
> --- a/PVE/API2/Pool.pm
> +++ b/PVE/API2/Pool.pm
> @@ -7,6 +7,7 @@ use PVE::AccessControl;
> use PVE::Cluster qw (cfs_read_file cfs_write_file);
> use PVE::Exception qw(raise_param_exc);
> use PVE::INotify;
> +use PVE::JSONSchema qw(get_standard_option parse_property_string print_property_string);
> use PVE::Storage;
>
> use PVE::SafeSyslog;
> @@ -47,10 +48,7 @@ __PACKAGE__->register_method ({
> type => "object",
> properties => {
> poolid => { type => 'string' },
> - comment => {
> - type => 'string',
> - optional => 1,
> - },
> + comment => { type => 'string', optional => 1 },
> members => {
> type => 'array',
> optional => 1,
> @@ -79,6 +77,7 @@ __PACKAGE__->register_method ({
> },
> },
> },
> + limits => { type => 'string', optional => 1 },
> },
> },
> links => [ { rel => 'child', href => "{poolid}" } ],
> @@ -136,6 +135,8 @@ __PACKAGE__->register_method ({
> members => $members,
> };
> $pool_info->{comment} = $pool_config->{comment} if defined($pool_config->{comment});
> + $pool_info->{limits} = print_property_string($pool_config->{limits}, 'pve-pool-limits')
> + if defined($pool_config->{limits});
> $pool_info->{poolid} = $poolid;
>
> push @$res, $pool_info;
> @@ -173,6 +174,7 @@ __PACKAGE__->register_method ({
> type => 'string',
> optional => 1,
> },
> + limits => get_standard_option('pve-pool-limits'),
> },
> },
> returns => { type => 'null' },
> @@ -196,6 +198,13 @@ __PACKAGE__->register_method ({
> };
>
> $usercfg->{pools}->{$pool}->{comment} = $param->{comment} if $param->{comment};
> + if (my $limits = parse_property_string('pve-pool-limits', $param->{limits} // '')) {
> + for my $kind (qw(mem cpu disk)) {
Like mentioned in the guest-helpers, this could itearte over the keys
exposed via access-control, or `keys %$limits` and deal with the
`-run`/`-config` suffixes.
> + raise_param_exc({ "$kind-run" => "'$kind-run' limit must be below '$kind-config' limit if both are defined!" })
> + if defined($limits->{"$kind-run"}) && defined($limits->{"$kind-config"}) && $limits->{"$kind-config"} < $limits->{"$kind-run"};
> + }
> + $usercfg->{pools}->{$pool}->{limits} = $limits;
> + }
>
> cfs_write_file("user.cfg", $usercfg);
> }, "create pool failed");
> @@ -288,6 +297,9 @@ __PACKAGE__->register_method ({
> optional => 1,
> default => 0,
> },
> + limits => get_standard_option("pve-pool-limits", {
> + description => "Update pool limits. Passing '0' for a specific limit will remove any currently configured value.",
> + }),
> },
> },
> returns => { type => 'null' },
> @@ -346,6 +358,21 @@ __PACKAGE__->register_method ({
> }
> }
>
> + if (my $update = parse_property_string('pve-pool-limits', $param->{limits} // '')) {
> + my $limits = $pool_config->{limits};
> + for my $kind (sort keys $update->%*) {
> + if ($update->{$kind} == 0) {
> + delete $limits->{$kind};
> + } else {
> + $limits->{$kind} = $update->{$kind};
> + }
> + }
> + for my $kind (qw(mem cpu disk)) {
> + raise_param_exc( { "$kind-run" => "'$kind-run' limit must be below '$kind-config' limit if both are defined!" })
> + if defined($limits->{"$kind-run"}) && defined($limits->{"$kind-config"}) && $limits->{"$kind-config"} < $limits->{"$kind-run"};
> + }
^ should probably be factored out, since it exists twice and is quite
unwieldy ;-)
> + }
> +
> cfs_write_file("user.cfg", $usercfg);
> }, "update pools failed");
>
> @@ -409,6 +436,7 @@ __PACKAGE__->register_method ({
> },
> },
> },
> + limits => get_standard_option("pve-pool-limits"),
> },
> },
> code => sub {
> --
> 2.39.2
next prev parent reply other threads:[~2024-04-11 9:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 13:12 [pve-devel] [RFC qemu-server/pve-container/.. 0/19] pool resource limits Fabian Grünbichler
2024-04-10 13:12 ` [pve-devel] [PATCH access-control 1/1] pools: define " Fabian Grünbichler
2024-04-10 13:12 ` [pve-devel] [PATCH container 1/7] config: add pool usage helper Fabian Grünbichler
2024-04-10 13:13 ` [pve-devel] [PATCH container 2/7] status: add pool usage fields Fabian Grünbichler
2024-04-11 9:28 ` Wolfgang Bumiller
2024-04-15 9:32 ` Fabian Grünbichler
2024-04-10 13:13 ` [pve-devel] [PATCH container 3/7] create/restore/clone: handle pool limits Fabian Grünbichler
2024-04-10 13:13 ` [pve-devel] [PATCH container 4/7] start: " Fabian Grünbichler
2024-04-10 13:13 ` [pve-devel] [PATCH container 5/7] hotplug: " Fabian Grünbichler
2024-04-10 13:13 ` [pve-devel] [PATCH container 6/7] rollback: " Fabian Grünbichler
2024-04-10 13:13 ` [pve-devel] [PATCH container 7/7] update: " Fabian Grünbichler
2024-04-11 7:23 ` Fabian Grünbichler
2024-04-11 10:03 ` Wolfgang Bumiller
2024-04-15 9:35 ` Fabian Grünbichler
2024-04-10 13:13 ` [pve-devel] [PATCH guest-common 1/1] helpers: add pool limit/usage helpers Fabian Grünbichler
2024-04-11 9:17 ` Wolfgang Bumiller
2024-04-15 9:38 ` Fabian Grünbichler
2024-04-10 13:13 ` [pve-devel] [PATCH manager 1/4] api: pools: add limits management Fabian Grünbichler
2024-04-11 9:24 ` Wolfgang Bumiller [this message]
2024-04-10 13:13 ` [pve-devel] [PATCH manager 2/4] pvestatd: collect and broadcast pool usage Fabian Grünbichler
2024-04-11 9:32 ` Wolfgang Bumiller
2024-04-15 12:36 ` Fabian Grünbichler
2024-04-10 13:13 ` [pve-devel] [PATCH manager 3/4] api: return pool usage when queried Fabian Grünbichler
2024-04-10 13:13 ` [pve-devel] [PATCH manager 4/4] ui: add pool limits and usage Fabian Grünbichler
2024-04-10 13:13 ` [pve-devel] [PATCH qemu-server 1/6] config: add pool usage helper Fabian Grünbichler
2024-04-10 13:13 ` [pve-devel] [PATCH qemu-server 2/6] vmstatus: add usage values for pool limits Fabian Grünbichler
2024-04-10 13:13 ` [pve-devel] [PATCH qemu-server 3/6] create/restore/clone: handle " Fabian Grünbichler
2024-04-10 13:13 ` [pve-devel] [PATCH qemu-server 4/6] update/hotplug: " Fabian Grünbichler
2024-04-10 13:13 ` [pve-devel] [PATCH qemu-server 5/6] start: " Fabian Grünbichler
2024-04-10 13:13 ` [pve-devel] [PATCH qemu-server 6/6] rollback: " Fabian Grünbichler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ycjoufdmc2vds3rysuoyvguxz3llmdu77esvkejzkuneum2uw@7rhkj22n672a \
--to=w.bumiller@proxmox.com \
--cc=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox