| 2023-05-11 10:08:33 |
Alex Lutay |
description |
Hi,
This is a Juju bugreport based on https://warthogs.atlassian.net/browse/DPE-1660
At the moment K8s charms (OCI resources) downloading speed is slow from registry.jujucharms.com.
It causes bugreports to our charm as it stays in "unknown" state for 2-4 minutes:
> Normal Pulled 26s kubelet Successfully pulled image "registry.jujucharms.com/charm/kotcfrohea62xreenq1q75n1lyspke0qkurhk/postgresql-image@sha256:d48d9a008fb9426a898ff6adcc601978b2d4bbbf99b2e0a90ba8df8f98c3b9f7" in 4m10.451608962s (4m11.867654465s including waiting)
Please find detailed STR in https://warthogs.atlassian.net/browse/DPE-1660?focusedCommentId=238556
It is important to mention several issues here:
1) lack of any end-user visibility about downloading progress is a root of the issue IMHO.
E.g. Juju shows downloading progress for VM charms, but not for K8s.
2) downloading speed for postgresql OCI resource (175MB) is 2-4 minutes from registry.jujucharms.com
(downloading the same OCI from ghcr.io and hub.docker.com is ~9 seconds)
3) juju confuses users with set status "unknown", see the unit status lifetime:
> postgresql-k8s/0 waiting allocating installing agent # OK
> postgresql-k8s/0* maintenance executing 10.1.221.139 installing charm software # OK
> postgresql-k8s/0* unknown executing 10.1.221.139
AFAIK, "unknown" is set during OCI downloading.
4) different juju units downloads the same resource/OCI in parallel (case `juju deploy postgresql-k8s -n 5`). Nice to optimize it too (https://github.com/juju/juju/pull/13215 for K8s OCI).
Thank you! |
Hi,
This is a Juju bugreport based on https://warthogs.atlassian.net/browse/DPE-1660
At the moment K8s charms (OCI resources) downloading speed is slow from registry.jujucharms.com.
It causes bugreports to our charm as it stays in "unknown" state for 2-4 minutes:
> Normal Pulled 26s kubelet Successfully pulled image "registry.jujucharms.com/charm/kotcfrohea62xreenq1q75n1lyspke0qkurhk/postgresql-image@sha256:d48d9a008fb9426a898ff6adcc601978b2d4bbbf99b2e0a90ba8df8f98c3b9f7" in 4m10.451608962s (4m11.867654465s including waiting)
Please find detailed STR in https://warthogs.atlassian.net/browse/DPE-1660?focusedCommentId=238556
It is important to mention several issues here:
1) lack of any end-user visibility about "resources (OCI)" downloading progress is a root of the issue IMHO.
E.g. Juju shows downloading progress for VM charms, but not for K8s.
2) downloading speed for postgresql OCI resource (175MB) is 2-4 minutes from registry.jujucharms.com
(downloading the same OCI from ghcr.io and hub.docker.com is ~9 seconds)
3) juju confuses users with set status "unknown", see the unit status lifetime:
> postgresql-k8s/0 waiting allocating installing agent # OK
> postgresql-k8s/0* maintenance executing 10.1.221.139 installing charm software # OK
> postgresql-k8s/0* unknown executing 10.1.221.139
AFAIK, "unknown" is set during OCI downloading.
4) different juju units downloads the same resource/OCI in parallel (case `juju deploy postgresql-k8s -n 5`). Nice to optimize it too (https://github.com/juju/juju/pull/13215 for K8s OCI).
Thank you! |
|
