Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1652540

Summary:	[RFE] use getAllVolumesInfo() verb instead of getVolumeInfo() in the engine relevant flows
Product:	[oVirt] ovirt-engine	Reporter:	Eyal Shenitzky <eshenitz>
Component:	BLL.Storage	Assignee:	Tal Nisan <tnisan>
Status:	CLOSED DEFERRED	QA Contact:	Avihai <aefrat>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	future	CC:	bugs
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-01 14:45:01 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:
Bug Depends On:	1520674
Bug Blocks:

Description Eyal Shenitzky 2018-11-22 10:39:14 UTC

Description of problem:

After bug 1520674 will be merged, the engine will be able to fetch all the volumes info on a specific storage domain in one VDSM call (getAllVolumesInfo) instead of calling getVolumeInfo() for each volume which creates redundant back and forward communication that takes a long time.

One example of a relevant flow is - attach storage domain operation.
As part of the attach operation of a storage domain, we fetch all the images from the storage domain and check each image whether it is an OVF_STORE disk or not.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Michal Skrivanek 2020-03-18 15:44:08 UTC

This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly

Comment 2 Michal Skrivanek 2020-03-18 15:47:16 UTC

This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly

Comment 3 Michal Skrivanek 2020-04-01 14:45:01 UTC

ok, closing. Please reopen if still relevant/you want to work on it.

Comment 4 Michal Skrivanek 2020-04-01 14:49:45 UTC

ok, closing. Please reopen if still relevant/you want to work on it.