Hi Pavan and all:

We have committed the RHV support for next release of NetBackup. It would help 
if we can have a weekly/bi weekly call for next 2 months. If there are no 
topics then we can cancel the call. 

Please let us know if this is fine and we can send a calendar invite.

+ Renee

Thanks
Navin


Sent from my iPhone

> On Jul 30, 2018, at 7:04 PM, Suchitra Herwadkar 
> <[email protected]> wrote:
> 
> 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" <[email protected]> 
> 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-restore-disk-snapshots/
>    https://bugzilla.redhat.com/show_bug.cgi?id=1405805
> 
>    Appreciate your time!
> 
>    Thanks
>    Suchitra 
> 
> 
>    On 7/18/18, 8:13 PM, "Ondra Machacek" <[email protected]> wrote:
> 
> 
> 
>>        On 07/18/2018 03:57 PM, Martin Perina wrote:
>> Ondro/Ravi/Tal, could you please reply to below questions?
>> 
>> 
>> On Tue, Jul 17, 2018 at 3:59 PM, Suchitra Herwadkar 
>> <[email protected] <mailto:[email protected]>> 
>> wrote:
>> 
>>    Hello oVirt Development team____
>> 
>>    __ __
>> 
>>    We had some more questions as we continue working on REST APIs.
>>    Kindly help us answer the same. ____
>> 
>>    __ __
>> 
>>    What is the expiry of generated access_token? ____
>> 
>>    *Description: *We have observed that the output of
>>    *“/ovirt-engine/sso/oauth/token” *contains a field *“exp”* which
>>    points to the date when the access_token is going to expire. In our
>>    case, we have seen this value to be 8 days later. However, the
>>    access_token gets expired within an hour. We would like to
>>    understand exactly what is the lifetime of this access_token? What
>>    we are seeing is something unexpected? Is this value configurable by
>>    users?
> 
>        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?
> 
>> 
>>    ____
>> 
>>    __ __
>> 
>>    How to retrieve the ‘creation_status’ of the snapshot through REST
>>    API? ____
>> 
>>    *Description: *We see there is a way to get it as part of query
>>    snapshot API viz
>>    /ovirt-engine/api/vms/<vm_id>/snapshots/<snapshot_id> where the
>>    response contains detailed information of snapshot, along with the
>>    field *"snapshot_status": "ok". *Just wanted to check if there is
>>    another API explicitly devoted to getting the creation status so
>>    that we can poll it periodically to know the status?____
>> 
>>    At least in CURL, we see there is some URL to fetch the creation
>>    status like this /ovirt-engine/api/<vm_id>/snapshots/<snapshot_id>
>>    /creation_status/<WHAT_IS_THIS_ID?>"____
> 
>        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.
> 
>> 
>>    __ __
>> 
>>    *Q.* How to call a DELETE snapshot API with ‘async’ operation as
>>    ‘false’? ____
>> 
>>    *Description: *The documentation for DELETE snapshot API mentions
>>    that the DELETE operation can be invoked synchronously or
>>    asynchronously based on the value of the parameter ‘async’. I wanted
>>    to perform DELETE operation synchronously, so tried providing this
>>    parameter in the body as “<async>false<async>”, still it was doing
>>    the operation asynchronously. Please advise on the correct usage of it.​
> 
>        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.
> 
>> 
>>    ____
>> 
>>    __ __
>> 
>>    Thanks____
>> 
>>    Suchitra ____
>> 
>>    __ __
>> 
>>    __ __
>> 
>>    *From: *Ranjit DSouza <[email protected]
>>    <mailto:[email protected]>>
>>    *Date: *Tuesday, July 3, 2018 at 1:43 PM
>>    *To: *"[email protected] <mailto:[email protected]>" <[email protected]
>>    <mailto:[email protected]>>
>>    *Cc: *DL-VTAS-ENG-NBU-EverestFalcons
>>    <[email protected]
>>    <mailto:[email protected]>>, Sudhakar
>>    Paulzagade <[email protected]
>>    <mailto:[email protected]>>, Pavan Chavva
>>    <[email protected] <mailto:[email protected]>>, Navin Tah
>>    <[email protected] <mailto:[email protected]>>
>>    *Subject: *Image Transfer mechanism queries/API support____
>> 
>>    __ __
>> 
>>    Hello oVirt Development team____
>> 
>>    ____
>> 
>>    We had a conversation with Pavan Chavva for supporting RHV. He had
>>    suggested to contact you with queries related to oVirt APIs we plan
>>    to use.____
>> 
>>    We have following queries:____
>> 
>>    ____
>> 
>>    __1.__While downloading a snapshot disk, can we identify allocated
>>    extents and download only those using oVirt API? We are able to
>>    download the disk using the Image Transfer API mechanism. ____
>> 
>>    However, this method downloads the entire disk including the
>>    non-allocated extents, which is a performance overhead. If this
>>    functionality does not exist at this point will it be available in
>>    near future?____
>> 
>>    ____
>> 
>>    __2.__Is there an alternate method to transfer a snapshot to and
>>    from RHV storage? Are there other methods such as NFS share where we
>>    can download snapshot image to and from RHV storage?____
>> 
>>    ____
>> 
>>    Thanks____
>> 
>>    Ranjit____
>> 
>>    Team EverestFalcons____
>> 
>> 
>>    _______________________________________________
>>    Devel mailing list -- [email protected] <mailto:[email protected]>
>>    To unsubscribe send an email to [email protected]
>>    <mailto:[email protected]>
>>    Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>    <https://www.ovirt.org/site/privacy-policy/>
>>    oVirt Code of Conduct:
>>    https://www.ovirt.org/community/about/community-guidelines/
>>    <https://www.ovirt.org/community/about/community-guidelines/>
>>    List Archives:
>>    
>> https://lists.ovirt.org/archives/list/[email protected]/message/QJUITZUJKWVG2Y2Y3GMBLXMTRVHT33ZK/
>>    
>> <https://lists.ovirt.org/archives/list/[email protected]/message/QJUITZUJKWVG2Y2Y3GMBLXMTRVHT33ZK/>
>> 
>> 
>> 
>> 
>> -- 
>> Martin Perina
>> Associate Manager, Software Engineering
>> Red Hat Czech s.r.o.
> 
> 
> 
> 
_______________________________________________
Devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/YJJ4ZOEE4U73HCYEXLPJVY47J5KOYEGV/

Reply via email to