| 2023-01-16 02:38:35 |
zhen |
bug |
|
|
added bug |
| 2023-01-16 02:42:57 |
zhen |
description |
image-volume opened too many times when image being importing which is unnecessary.
```
# glance_store/_drivers/cinder.py #Store.add()
def add(self, image_id, image_file, image_size, hashing_algo, context=None,
verifier=None):
...
```
During the import image process, the 'image_size' passed to the add () method is always 0. According to the current logic, when the mirror is relatively large, the mirror volume will be mounted frequently because of the dynamic expansion of the mirror volume (for example, 70g images need to be mounted / unmounted 69 times)
I think when calling the add () method, you can get the actual size of 'stage_image'' in advance and pass it as' image_size''. |
image-volume opened too many times when image being importing which is unnecessary.
```
# glance_store/_drivers/cinder.py #Store.add()
def add(self, image_id, image_file, image_size, hashing_algo, context=None,
verifier=None):
...
```
During the import image process, the 'image_size' passed to the add () method is always 0. According to the current logic, when the image is relatively large, the image-volume will be mounted/unmounted frequently because of the dynamic expansion of the mirror volume (for example, image with size 70G need to be mounted/unmounted 69 times)
I think when calling the add () method, you can get the actual size of 'stage_image'' in advance and pass it as' image_size''. |
|
| 2023-01-16 02:43:27 |
zhen |
description |
image-volume opened too many times when image being importing which is unnecessary.
```
# glance_store/_drivers/cinder.py #Store.add()
def add(self, image_id, image_file, image_size, hashing_algo, context=None,
verifier=None):
...
```
During the import image process, the 'image_size' passed to the add () method is always 0. According to the current logic, when the image is relatively large, the image-volume will be mounted/unmounted frequently because of the dynamic expansion of the mirror volume (for example, image with size 70G need to be mounted/unmounted 69 times)
I think when calling the add () method, you can get the actual size of 'stage_image'' in advance and pass it as' image_size''. |
image-volume opened too many times when image being importing which is unnecessary.
```
# glance_store/_drivers/cinder.py #Store.add()
def add(self, image_id, image_file, image_size, hashing_algo, context=None,
verifier=None):
...
```
During the import image process, the 'image_size' passed to the add () method is always 0. According to the current logic, when the image is relatively large, the image-volume will be mounted/unmounted frequently because of the dynamic expansion of the mirror volume (for example, image with size 70G need to be mounted/unmounted 69 times)
I think when calling the add () method, we can get the actual size of 'stage_image'' in advance and pass it as' image_size''. |
|
| 2023-01-16 03:18:19 |
zhen |
description |
image-volume opened too many times when image being importing which is unnecessary.
```
# glance_store/_drivers/cinder.py #Store.add()
def add(self, image_id, image_file, image_size, hashing_algo, context=None,
verifier=None):
...
```
During the import image process, the 'image_size' passed to the add () method is always 0. According to the current logic, when the image is relatively large, the image-volume will be mounted/unmounted frequently because of the dynamic expansion of the mirror volume (for example, image with size 70G need to be mounted/unmounted 69 times)
I think when calling the add () method, we can get the actual size of 'stage_image'' in advance and pass it as' image_size''. |
image-volume opened too many times when image being importing which is unnecessary.
```
# glance_store/_drivers/cinder.py #Store.add()
def add(self, image_id, image_file, image_size, hashing_algo, context=None,
verifier=None):
...
```
During the import image process, the 'image_size' passed to the add () method is always 0. According to the current logic, when the image is relatively large, the image-volume will be mounted/unmounted frequently because of the dynamic expansion of the mirror volume (for example, image with size 70G need to be mounted/unmounted 70/70 times)
I think when calling the add () method, we can get the actual size of 'stage_image'' in advance and pass it as' image_size''. |
|
