Description of problem: Currently when someone wants to fetch resources (for example VMs) using RESTAPI, he will need additional requests to fetch also its sub resources (like NICs or disk attachments). But inside RESTAPI we already return links to those subresources, so it would not be hard to provide parameter 'follow' to define which subresources should be fetched along with main resource using single request, for example: GET /ovirt-engine/api/vms?follow="nics,disk_attachments" RESTAPI will also provide default "naive" subresource fetching (which of course is not optimized for performance), but we will provide infrastructure for engine developers to easily add performance optimized implementations for common use cases (for example BZ1436206) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
http://lists.ovirt.org/pipermail/devel/2017-March/029954.html
Verified in ovirt version 4.2.0-0.0.master.20170823165744.git116f435.el7.centos Tested with: GET /ovirt-engine/api/vms?follow=disk_attachments,nics Result: <vms> <vm> <disk_attachments> </disk_attachments> ... <nics> </nics> </vm> </vms>
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.