Is it possible to update the value of image_size_cap in Glance config under StarlingX (stx-openstack)?

On Thu, Jul 8, 2021 at 5:44 PM open infra <openinfradn@gmail.com> wrote:
I was able to upload CentOS image which is around 1GB.
http://paste.openstack.org/show/807260/

Is there a quota related to image upload?
Where exactly I can alter if such limit exist.



On Thu, Jul 8, 2021 at 2:21 PM open infra <openinfradn@gmail.com> wrote:
Hi Mingyuan,

I have increased kubelet size from 10 to 200. But still no luck.
tried with --debug option http://paste.openstack.org/show/807253/

BTW I found errors inthe openstack_glace-api- log.
 http://paste.openstack.org/show/807250/

Regards,
Danishka

On Thu, Jul 8, 2021 at 1:51 PM Qi, Mingyuan <mingyuan.qi@intel.com> wrote:

Danishka,

 

You will need to extend kubelet-lv to enlarge glance pod’s disk cache.

 

For example:

system host-fs-modify controller-0 kubelet=100

system host-fs-modify controller-1 kubelet=100

 

Mingyuan

 

From: open infra <openinfradn@gmail.com>
Sent: Thursday, July 8, 2021 16:07
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] Image upload failed

 

Hi

 

I was supposed to upload Windows (qcow2) image, but it failed.

I was able to upload both fedora and centos images. Windows image is around 100GB.

 

 

controller-1:/images$ openstack endpoint list | grep glance
| 6c7c6662b5274e61afec25a67e2f13a8 | RegionOne | glance | image | True | public | http://glance.openstack.svc.cluster.local/ |
| 855c1127607749faa5896417a559a47a | RegionOne | glance | image | True | internal | http://glance.openstack.svc.cluster.local/ |
| cc5ca27d344c48e287657feee449916b | RegionOne | glance | image | True | admin | http://glance.openstack.svc.cluster.local/ |
controller-1:/images$

 

$ openstack image list
+--------------------------------------+-----------+--------+
| ID | Name | Status |
+--------------------------------------+-----------+--------+
| 0079f06a-498c-453c-a8fd-0ade7ac2f258 | CentOS-8 | active |
| dad6dfdc-b281-4592-928b-cf64b47f5b3a | Fedora-34 | active |

 

 

I appreciate if  I can get any hint or guide to resolve this.

 

Regard

Danishka