Bug 1377359 - [RFE] Possibility to request disks by multiple disk IDs
Summary: [RFE] Possibility to request disks by multiple disk IDs
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: ---
: ---
Assignee: Juan Hernández
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-19 13:26 UTC by Filip Krepinsky
Modified: 2017-01-31 13:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-31 13:33:56 UTC
oVirt Team: Storage
juan.hernandez: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

Description Filip Krepinsky 2016-09-19 13:26:41 UTC
Description of problem:
Our mobile client moVirt needs to get disks of selected vm. This is done by either querying all disks or retrieving disks one by one, after the app has retrieved disk attachments of requested vm. These are quite expensive operations.

Expected results:
Possibility to query for multiple disks by their IDs (obtained from disk_attachments) or to find them by vm ID. 

Additional info:
In 3.6 API this is done by calling /vms/{vmId}/disks, but equivalent feature is missing in 4.0 API.

Comment 1 Filip Krepinsky 2017-01-05 16:47:30 UTC
This feature is not needed for moVirt anymore. 

We fetch all disks instead and then pair them with attachments. Fetching all disks is not problem for us anymore because we need all of them for our dashboard.

Comment 2 Allon Mureinik 2017-01-31 13:33:56 UTC
(In reply to Filip Krepinsky from comment #1)
> This feature is not needed for moVirt anymore. 
> 
> We fetch all disks instead and then pair them with attachments. Fetching all
> disks is not problem for us anymore because we need all of them for our
> dashboard.
Closing for now, feel free to reopen if there's a real usecase behind the request.


Note You need to log in before you can comment on or make changes to this bug.