yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #90996
[Bug 2002932] [NEW] image-volume opened too many times when image being importing which is unnecessary
Public bug reported:
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''.
** Affects: glance
Importance: Undecided
Status: New
** Description changed:
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):
+ 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)
+ 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''.
** Description changed:
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
+ I think when calling the add () method, we can get the actual size of
'stage_image'' in advance and pass it as' image_size''.
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/2002932
Title:
image-volume opened too many times when image being importing which is
unnecessary
Status in Glance:
New
Bug 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''.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/2002932/+subscriptions