[Users] Unable to get latest resource status

[Alex Jia]

Hi Michael,
Thanks for your reply, yeah, it's not a bug, I mean whether we may support
wait_for_status function in ovirt-engine-sdk like python-rhev, as I said,
it will be more convenient for users. so it should be RFE.

In addition, I know this user guide, however, I think I need to see it carefully
again.


Thanks,
Alex


----- Original Message -----
From: "Michael Pasternak" <mpastern at redhat.com>
To: "Alex Jia" <ajia at redhat.com>
Cc: "Juan Hernandez" <juan.hernandez at redhat.com>, users at ovirt.org, "Rita Wu" <rwu at redhat.com>, "Itamar Heim" <iheim at redhat.com>
Sent: Saturday, April 28, 2012 7:21:59 PM
Subject: Re: [Users] Unable to get latest resource status


Hi Alex,

On 04/28/2012 06:19 AM, Alex Jia wrote:
> On 04/27/2012 11:30 PM, Juan Hernandez wrote:
>> On 04/27/2012 05:27 PM, Alex Jia wrote:
>>> Although I haven't try it, I think you're right, I should refresh VM
>>> in loop body.
>> Let me know what is the result in your environment.
> I have tried it and indeed works well for me.
>>> In addition, as I said, it will be convenient if we have wait_for_status
>>> function like before.
>> I will look into it. I would greatly appreciate if you can open a bug to
>> request and track it.
>>
> It's okay for me, I want to know I need to file a fedora bug? which component?
> because I'm doing these on RHEL6.2.

it's not a bug, since we using RESTful api, you get resource representation
which is holding vm metadata relevant only for the given moment,

if you want to poll this vm for the status change, you'll have to retrieve
it on each iteration.

not relevant to vm execution, but we also have /sync execution mode/ (mostly
on storage related actions, see our user guide [1]), so you can block
action till it get accomplished on server side.

[1] http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Virtualization/3.0/html/REST_API_Guide/

-- 

Michael Pasternak
RedHat, ENG-Virtualization R&D