[ovirt-devel] Re: [EXTERNAL] Re: Re: Image Transfer mechanism queries/API support

Hi Pavan Is it possible to discuss this over a call/webex? It will help us put up our perspective and we can discuss options. Let us know! -Suchitra On 7/26/18, 6:44 AM, "Suchitra Herwadkar" <Suchitra.Herwadkar(a)veritas.com&gt; wrote: Hi Ondra and team Thanks for helping us out on below answers. We recently have reported bug using Bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1608452 This is regarding download of snapshot disk, having multiple snapshots before creation of snapshot for backup. We have observed that in case of multiple snapshots, the caller needs to keep track of the chain and have them in the same order while uploading them back. Is this a correct understanding? We were looking for an alternate approach of downloading entire disk using snapshot ID XXX, which is created for backup purpose, with REST API (i.e. using proxy_url and signed ticket). We could achieve this if this only if it was a first snapshot when the actual size is same as the provisional size and not for interleaved snapshots. Kindly advise if that's possible. Reference Articles: https://ovirt.org/develop/release-management/features/storage/backup-rest... https://bugzilla.redhat.com/show_bug.cgi?id=1405805 Appreciate your time! Thanks Suchitra On 7/18/18, 8:13 PM, "Ondra Machacek" <omachace(a)redhat.com&gt; wrote: On 07/18/2018 03:57 PM, Martin Perina wrote: I know you can increase user session timeout in engine-config property called 'UserSessionTimeOutInterval', by default it's one hour (note you must restart ovirt-engine in order to take effect of the change). How the field 'exp' is related, I don't exactly know. Ravi? The link to creation_status is provided in the response of create snapshot operation, if you do it asynchronously. But it's not recomended to use it that way. As you've described polling the 'snapshot_status' attribute is the best way of waiting for operation to finish. Same as above the sync/async is incorrect here. Both operations behave the same, but async will return the 'creation_status' which you can poll to get the result, but every operation is implemented differently so I wouldn't recomend to use it. If you want to be sure the snapshost is deleted I the best way is the run DELETE /api/vms/123/snapshots/456, and then do polling of /api/vms /123/snapshots/456 until it returns 404. This operation unfortunatelly can't be invoked synchronously.