VMware: Same image should not be transferred more than one time on concurrent spawn operations

Bug #1283325 reported by Arnaud Legendre
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Opinion
Wishlist
Unassigned

Bug Description

On concurrent spawn operations, the VMware driver transfers the same image into different temporary directories before getting into the cache: the same bits might be downloaded 20 times if 20 spawn operations happen at the same time for a given image (before being cached).
The goal here is to use a lock to only transfer one time the bits of the image.

Tags: vmware
Changed in nova:
assignee: nobody → Arnaud Legendre (arnaudleg)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/75551

Changed in nova:
status: New → In Progress
Eric Brown (ericwb)
tags: added: vmware
Changed in nova:
importance: Undecided → Medium
Revision history for this message
Joe Gordon (jogo) wrote :

Is this bug still valid? The patch was abandoned.

Changed in nova:
status: In Progress → Incomplete
Revision history for this message
zhu zhu (zhuzhubj) wrote :

This bug should be a valid bug. For the same flat image deployment in concurrent, it will transfer same image multiple times. Though deployment finally could get success, it will waste a lot of datastore disk spaces.

Sean Dague (sdague)
Changed in nova:
assignee: Arnaud Legendre (arnaudleg) → nobody
Revision history for this message
Sean Dague (sdague) wrote :

feature for performance enhancement

Changed in nova:
status: Incomplete → Opinion
importance: Medium → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.