12:03 a.m.
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
5:52 p.m.
Hi John,
do you mean 'Spice client' addon in chrome store?
From what I learnt about the client, it seems it's basically HTML5
client for SPICE. For this you must set up your websocket proxy.
I believe the easier way is to use already built-in SPICE-HTML5 client. It should run on
Firefox and Chrome. Please take a look at this page [1] and feel free to contact me about
it.
There is also possibility of setting up websocket proxy and connecting to spice port
directly, but IMHO that wouldn't be exactly user-friendly.
Cheers,
Franta.
[1]:
http://www.ovirt.org/Features/noVNC_console#Setup_Websocket_Proxy_on_the_...
----- Original Message -----
From: "John Gardeniers" <jgardeniers(a)objectmastery.com>
To: "users" <users(a)ovirt.org>
Sent: Thursday, October 9, 2014 11:03:31 PM
Subject: [ovirt-users] Using a free-standing Spice viewer
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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
6:02 p.m.
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(a)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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
2:49 a.m.
This is a multi-part message in MIME format.
--------------030903030901020006000708
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
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(a)objectmastery.com <mailto: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(a)ovirt.org <mailto: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
______________________________________________________________________
--------------030903030901020006000708
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
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).<br>
<br>
regards,<br>
John<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 11/10/14 02:02, Dan Yasny
wrote:<br>
</div>
<blockquote
cite="mid:CALLXwb72wU7aQHHcZy2RacvXn8PicMmF0R==3mUyeDkDb_dn8w@mail.gmail.com"
type="cite">
<div dir="ltr">The steps are:
<div>1. Find the VM's UUID in the API</div>
<div><a moz-do-not-send="true"
href="https://rhevm/ovirt-engine/api/vms?search=VMNAME">https://rhevm/ovirt-engine/api/vms?search=VMNAME</a><br>
</div>
<div>2. Find the VM's current host and spice ports:</div>
<div><a moz-do-not-send="true"
href="https://rhevm/ovirt-engine/api/vms/UUID/">https://rhevm/ovirt-engine/api/vms/UUID/</a> </div>
<div>Look for the <display> section - it will hold the
host IP or FQDN, and the spice ports<br>
</div>
<div>3. Issue a spice ticket via <a moz-do-not-send="true"
href="https://rhevm/ovirt-engine/api/vms/UUID/ticket">https://rhevm/ovirt-engine/api/vms/UUID/ticket</a></div>
<div>4. Connect with a spice client (remote-viewer or spicec)
with the target being HOST:PORT and the ticket you issued as
password</div>
<div><br>
</div>
<div>All this can be scripted via the API or the engine CLI</div>
<div><br>
</div>
<div>Hope this helps</div>
<div><br>
</div>
<div>Dan</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Oct 9, 2014 at 5:03 PM, John
Gardeniers <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:jgardeniers@objectmastery.com"
target="_blank">jgardeniers(a)objectmastery.com</a>&gt;</span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">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.<br>
<br>
regards,<br>
John<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Users@ovirt.org"
target="_blank">Users(a)ovirt.org</a><br>
<a moz-do-not-send="true"
href="http://lists.ovirt.org/mailman/listinfo/users"
target="_blank">http://lists.ovirt.org/mailman/listinfo/user...
</blockquote>
</div>
<br>
</div>
<br clear="all">
______________________________________________________________________<br>
This email has been scanned by the Symantec Email Security.cloud
service.<br>
For more information please visit <a class="moz-txt-link-freetext"
href="http://www.symanteccloud.com">http://www.symanteccloud.com</a><br>
______________________________________________________________________<br>
</blockquote>
<br>
</body>
</html>
--------------030903030901020006000708--
3:12 a.m.
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(a)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(a)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(a)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
______________________________________________________________________
2:10 a.m.
On 10/12/2014 02:49 AM, John Gardeniers 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(a)objectmastery.com <mailto: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(a)ovirt.org <mailto: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
> ______________________________________________________________________
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
the ovirt cli console command should cover you?
3681
days inactive
3697
days old
5 comments
4 participants
participants (4)
-
Dan Yasny -
Frantisek Kobzik -
Itamar Heim -
John Gardeniers