Not really messy when scripted, each step is a small API command after all. This is what oVirt does when you connect, getting the data and populating the .vv file for you. So if the VM migrates in the instant it takes to get the info, the connection will fail, so you simply rerun the connect script. On Sat, Oct 11, 2014 at 7:49 PM, John Gardeniers < jgardeniers@objectmastery.com> wrote:
Thanks for the info Dan. If that's what it takes I'll need to use a different method. The one you describe is not only very messy but extremely breakable and error prone (e.g. if the VM migrates to another host).
regards, John
On 11/10/14 02:02, Dan Yasny wrote:
The steps are: 1. Find the VM's UUID in the API https://rhevm/ovirt-engine/api/vms?search=VMNAME 2. Find the VM's current host and spice ports: https://rhevm/ovirt-engine/api/vms/UUID/ Look for the <display> section - it will hold the host IP or FQDN, and the spice ports 3. Issue a spice ticket via https://rhevm/ovirt-engine/api/vms/UUID/ticket 4. Connect with a spice client (remote-viewer or spicec) with the target being HOST:PORT and the ticket you issued as password
All this can be scripted via the API or the engine CLI
Hope this helps
Dan
On Thu, Oct 9, 2014 at 5:03 PM, John Gardeniers < jgardeniers@objectmastery.com> wrote:
Connecting to a VM console with Spice via the RHEV/Ovirt admin interface works just fine. How can I connect to a VM's console using a free-standing Spice viewer, such as the Chrome Spice Viewer plug-in? I've so far found no information on this at all.
regards, John
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________