From cb23414b4055bf34213747a8854cf9490fc13ea2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fran=E0=B2=A0=5F=E0=B2=A0is=20=28Fran=C3=A7ois=29=20Conil?= Date: Thu, 15 May 2025 13:57:41 +0200 Subject: [PATCH 1/5] Update ece-manage-capacity.md --- deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md b/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md index c2f3ad76f3..36ea877613 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md @@ -47,7 +47,9 @@ For more information on how to use API keys for authentication, check the sectio Prior to ECE 3.5.0, regardless of the use of this API, the [CPU quota](#ece-alloc-cpu) used the memory specified at installation time. :::: - +::::{important} +CPU quotas cannot be removed (CPU hard limit) or updated when running ECE on Podman. +:::: ### Examples [ece_examples] From 1af439cf6491a49deb7058b3b468e55f431e088b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?= <25320357+eedugon@users.noreply.github.com> Date: Wed, 28 May 2025 15:44:45 +0200 Subject: [PATCH 2/5] note slightly updated --- .../deploy/cloud-enterprise/ece-manage-capacity.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md b/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md index 36ea877613..12bd5ceb96 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md @@ -44,11 +44,9 @@ curl -X PUT \ For more information on how to use API keys for authentication, check the section [Access the API from the Command Line](cloud://reference/cloud-enterprise/ece-api-command-line.md). ::::{important} -Prior to ECE 3.5.0, regardless of the use of this API, the [CPU quota](#ece-alloc-cpu) used the memory specified at installation time. -:::: +* When running ECE on Podman, CPU quotas for existing instances cannot be removed or updated. As a result, changing an allocator’s capacity won’t affect the CPU quotas of already running containers. -::::{important} -CPU quotas cannot be removed (CPU hard limit) or updated when running ECE on Podman. +* Prior to ECE 3.5.0, regardless of the use of this API, the [CPU quota](#ece-alloc-cpu) calculation used the memory specified at installation time. :::: ### Examples [ece_examples] From 108f082348c0090fc442c9e8d1f4a5028668915e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?= <25320357+eedugon@users.noreply.github.com> Date: Wed, 28 May 2025 15:47:43 +0200 Subject: [PATCH 3/5] note slightly updated --- deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md b/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md index 12bd5ceb96..26d7b8d497 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md @@ -46,7 +46,7 @@ For more information on how to use API keys for authentication, check the sectio ::::{important} * When running ECE on Podman, CPU quotas for existing instances cannot be removed or updated. As a result, changing an allocator’s capacity won’t affect the CPU quotas of already running containers. -* Prior to ECE 3.5.0, regardless of the use of this API, the [CPU quota](#ece-alloc-cpu) calculation used the memory specified at installation time. +* In ECE versions prior to 3.5.0, the CPU quota is always calculated using the memory specified at installation time, even if you later update the capacity using the API. :::: ### Examples [ece_examples] From c2c9a2978dcc34b736e2f57aa87860747b7d8d2d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?= <25320357+eedugon@users.noreply.github.com> Date: Mon, 16 Jun 2025 12:17:49 +0200 Subject: [PATCH 4/5] final proposal for podman limitation --- .../deploy/cloud-enterprise/ece-manage-capacity.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md b/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md index fd854b598c..74ba09d44b 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md @@ -42,18 +42,16 @@ curl -X PUT \ ``` 1. For information on how to use API keys for authentication, refer to [Access the API from the command line](cloud://reference/cloud-enterprise/ece-api-command-line.md). +::::{important} +* When running ECE on Podman, CPU quotas for existing instances cannot be disabled or updated. As a result, changing an allocator’s capacity won’t affect the CPU quotas of already running containers. +:::: + After applying the change, log in to the allocator host you updated and restart the allocator service: ```sh docker restart frc-allocators-allocator ``` -::::{important} -* When running ECE on Podman, CPU quotas for existing instances cannot be removed or updated. As a result, changing an allocator’s capacity won’t affect the CPU quotas of already running containers. - -* In ECE versions prior to 3.5.0, the CPU quota is always calculated using the memory specified at installation time, even if you later update the capacity using the API. -:::: - ### Examples [ece_examples] Here are some examples to make Elastic deployments and ECE system services run smoothly on your host: @@ -72,6 +70,9 @@ ECE uses CPU quotas to assign shares of the allocator host to the instances that `CPU quota = DeploymentRAM / HostCapacity` +::::{important} +* In ECE versions prior to 3.5.0, the CPU quota is always calculated using the memory specified at installation time, even if you later update the host capacity using the API. +:::: ### Examples [ece_examples_2] From d67322781b24fbdddef2611ec13025e5d0bc0fc5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?= <25320357+eedugon@users.noreply.github.com> Date: Mon, 16 Jun 2025 12:35:43 +0200 Subject: [PATCH 5/5] final proposal for podman limitation --- deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md b/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md index 74ba09d44b..0f40998aec 100644 --- a/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md +++ b/deploy-manage/deploy/cloud-enterprise/ece-manage-capacity.md @@ -43,7 +43,7 @@ curl -X PUT \ 1. For information on how to use API keys for authentication, refer to [Access the API from the command line](cloud://reference/cloud-enterprise/ece-api-command-line.md). ::::{important} -* When running ECE on Podman, CPU quotas for existing instances cannot be disabled or updated. As a result, changing an allocator’s capacity won’t affect the CPU quotas of already running containers. +When running ECE on Podman, CPU quotas for existing instances cannot be disabled or updated. As a result, changing an allocator’s capacity won’t affect the CPU quotas of already running containers. :::: After applying the change, log in to the allocator host you updated and restart the allocator service: @@ -71,7 +71,7 @@ ECE uses CPU quotas to assign shares of the allocator host to the instances that `CPU quota = DeploymentRAM / HostCapacity` ::::{important} -* In ECE versions prior to 3.5.0, the CPU quota is always calculated using the memory specified at installation time, even if you later update the host capacity using the API. +In ECE versions prior to 3.5.0, the CPU quota is always calculated using the memory specified at installation time, even if you later update the host capacity using the API. :::: ### Examples [ece_examples_2]