<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 13, 2018 at 11:14 AM, fsoyer <span dir="ltr"><<a href="mailto:fsoyer@systea.fr" target="_blank">fsoyer@systea.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>I can't find any exhaustive doc for new vdsm-client. My problem actually is a task (export a vm to OVA) blocked.<br></blockquote><div><br></div><div>I'm afraid you won't find any task in VDSM for 'export a VM to OVA'.</div><div>Expoting a VM to OVA is comprised of three steps:</div><div>1. Creating temporary cloned disks - you'll find a task of copy-image-group for each disk.</div><div>2. Creating the OVA file - that's done by a python script executed by ansible, there is no task for that in VDSM.</div><div>3. Removing the temporary cloned disks - you'll find a task of remove-image for each disk.</div><div><br></div><div>Can you please elaborate on the problem you're having - where do you see that task and how can you see that it's blocked?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I found that I can interact with<br>vdsm-client Task getInfo taskID=<uuid>, and replace getInfo by "stop", BUT : how can I find this UUID ???<br>Old "vdsClient -s 0 getAllTasksStatuses" has no equivalent ??<br><br>Does someone knows if a complete doc exists dot vdsm-client ?<br>Thanks<br>Frank<p class="m_-7891996504513696655Text2"><br> </p><br><br>Le Mercredi, Janvier 25, 2017 12:30 CET, Irit Goihman <<a href="mailto:igoihman@redhat.com" target="_blank">igoihman@redhat.com</a>> a écrit:<br> <blockquote type="cite" cite="http://CAA=i7HMsB7iRYqP9yyBx4w7pGer9rTE9wkJZRgcmXRQMaJezwg@mail.gmail.com"><div dir="ltr">Hi All,<div> </div><div>vdsClient will be removed from master branch today.</div><div>It is using XMLRPC protocol which has been deprecated and replaced by JSON-RPC.</div><div> </div><div>A new client for vdsm was introduced in 4.1: vdsm-client.</div><div>This is a simple client that uses JSON-RPC protocol which was introduced in ovirt 3.5.</div><div> </div><div>The client is not aware of the available methods and parameters, and you should consult </div><div>the schema [1] in order to construct the desired command.</div><div> </div><div>Future version should parse the schema and provide online help.</div><div> </div><div> </div><div>If you're using vdsClient, we will be happy to assist you in migrating to the new vdsm client.</div><div> </div><div> </div><div> </div><div><b><u>vdsm-client usage:</u></b></div><div> </div><div><div>vdsm-client [-h] [-a ADDRESS] [-p PORT] [--unsecure] [--timeout TIMEOUT]</div><div> [-f FILE] namespace method [name=value [name=value] ...]</div></div><div> </div><div> </div><div><div>Invoking simple methods:</div><div> </div><div># vdsm-client Host getVMList</div><div>['b3f6fa00-b315-4ad4-8108-<wbr>f73da817b5c5']</div></div><div> </div><div>For invoking methods with many or complex parameters, you can read the parameters from a JSON format file:</div><div> </div><div># vdsm-client Lease info -f lease.json</div><div> </div><div>where lease.json file content is:</div><div> </div><div><div>{ </div><div> "lease": { </div><div> "sd_id": "75ab40e3-06b1-4a54-a825-<wbr>2df7a40b93b2", </div><div> "lease_id": "b3f6fa00-b315-4ad4-8108-<wbr>f73da817b5c5" </div><div> } </div><div> } </div></div><div> </div><div>It is also possible to read parameters from standard input, creating complex parameters interactively:</div><div> </div><div><div># cat <<EOF | vdsm-client Lease info -f - </div><div> { </div><div> "lease": { </div><div> "sd_id": "75ab40e3-06b1-4a54-a825-<wbr>2df7a40b93b2", </div><div> "lease_id": "b3f6fa00-b315-4ad4-8108-<wbr>f73da817b5c5" </div><div> } </div><div> } </div><div> EOF </div></div><div> </div><div> </div><div><b><u>Constructing a command from vdsm schema:</u></b></div><div> </div><div>Let's take VM.getStats as an example.</div><div>This is the entry in the schema:</div><div> </div><div><div>VM.getStats: </div><div> added: '3.1' </div><div> description: Get statistics about a running virtual machine. </div><div> params: </div><div> - description: The UUID of the VM </div><div> name: vmID </div><div> type: *UUID </div><div> return: </div><div> description: An array containing a single VmStats record </div><div> type: </div><div> - *VmStats </div></div><div> </div><div>namespace: VM</div><div>method name: getStats</div><div>params: vmID</div><div> </div><div>The vdsm-client command is:</div><div> </div><div># vdsm-client VM getStats vmID=b3f6fa00-b315-4ad4-8108-<wbr>f73da817b5c5</div><div> </div><div> </div><div><div><b><u>Invoking getVdsCaps command:</u></b></div><div> </div><div># vdsm-client Host getCapabilities</div></div><div> </div><div><div> </div><div> </div><div>Please consult vdsm-client help and man page for further details and options.</div><div> </div><div> </div><div> </div><div>[1] <a href="https://github.com/oVirt/vdsm/blob/master/lib/api/vdsm-api.yml" target="_blank">https://github.com/oVirt/vdsm/<wbr>blob/master/lib/api/vdsm-api.<wbr>yml</a></div><div> </div><span class="HOEnZb"><font color="#888888">--<div class="m_-7891996504513696655gmail_signature"><div dir="ltr">Irit Goihman<div>Software Engineer</div><div>Red Hat Israel Ltd.</div></div></div></font></span></div></div></blockquote><br><br>
<br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
<br></blockquote></div><br></div></div>