Bug 1428395

Summary: [RFE][Automation] - Remove read lock for copy template disk
Product: [oVirt] ovirt-engine Reporter: Elad <ebenahar>
Component: RFEsAssignee: Tal Nisan <tnisan>
Status: CLOSED DUPLICATE QA Contact: mlehrer
Severity: high Docs Contact:
Priority: medium    
Version: 4.1.1.2CC: aefrat, bugs, eshenitz, tnisan, vjuranek
Target Milestone: ovirt-4.4.3Keywords: Automation, FutureFeature, Performance
Target Release: ---Flags: pm-rhel: ovirt-4.4?
ylavi: planning_ack+
rule-engine: devel_ack?
rule-engine: testing_ack?
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-04 11:25:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Elad 2017-03-02 13:48:27 UTC 
Description of problem:

It should be possible to perform multiple copy operations simultaneously for a template disk. This can be achieved by removing the read lock for template disks. 

This can make a significant improvement for shortening the time it takes to copy a template disk to several storage domains, especially for large environments with many storage domains.

For example, for our day to day work in RHV QE automation, this operation takes much of our environments preparations, where we build environments with ~10 storage domains and we need a template disk to be copied to all of them for VM creation from it on each domain.
Comment 1 Yaniv Lavi 2017-06-13 09:25:00 UTC 
How low hanging is this?
Comment 2 Yaniv Lavi 2017-11-26 14:25:23 UTC 
(In reply to Yaniv Lavi from comment #1)
> How low hanging is this?

Tal replied in thread:
Should be relatively easy if I understand correctly
Comment 3 Sandro Bonazzola 2019-01-28 09:40:58 UTC 
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
Comment 4 Avihai 2020-07-13 14:13:02 UTC 
Performance issue moved to performance QE lead Mordechai for consideration and planning.
Comment 5 Tal Nisan 2020-08-04 11:25:33 UTC 

*** This bug has been marked as a duplicate of bug 1677500 ***