[ovirt-devel] [ovirt-users] When debug vdsm branch 4.0, why there has some code will call function ping(self) in bindingxmlrpc.py cycle? Even the vdsm is not managed by ovirt-engine?

[Francesco Romani]

----- Original Message -----
> From: "lifuqiong" <lifuqiong at cncloudsec.com>
> To: users at ovirt.org, Devel at ovirt.org
> Sent: Tuesday, July 26, 2016 7:26:04 AM
> Subject: [ovirt-users] When debug vdsm branch 4.0,	why there has some code will call function ping(self) in
> 	bindingxmlrpc.py cycle? Even the vdsm is not managed by	ovirt-engine?
> 
> 
> 
> Hi,
> 
> I setup a breakpoint in Line 637 in bindingxmlrpc.py , which as follows:
> (branch:4.0; code url is: https://github.com/oVirt/vdsm/tree/ovirt-4.0)
> 
> 636 def ping(self):
> 
> 637 api = API.Global()
> 
> 638 return api.ping()
> 
> 
> 
> But even the vdsm is not managed by any ovirt-engine , the line 637 will be
> called many times,
> 
> I thought the ping() function will be called only when the ovirt-engine will
> create connection with vdsm, so why it will be called cycle?

This should be caused by the MOM daemon, which periodically checks the availability
of Vdsm.

Bests,

-- 
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani