[Engine-devel] Hints for building up a spicec connection in Ovirt
Andrew Wells
agwells0714 at gmail.com
Wed Mar 14 17:17:39 UTC 2012
On Wed, Mar 14, 2012 at 12:53 PM, Itamar Heim <iheim at redhat.com> wrote:
> On 03/14/2012 06:49 PM, Ewoud Kohl van Wijngaarden wrote:
>
>> On Wed, Mar 14, 2012 at 05:36:38PM +0200, Itamar Heim wrote:
>>
>>> On 03/14/2012 04:51 PM, Andrew Wells wrote:
>>>
>>>> I am trying to build a connection manually with spicec (or what ever I
>>>> need to build the connection with) in Ovirt/RHEV and I am wondering what
>>>> do I need to form this connection?
>>>>
>>>> And if this is the wrong place to ask, can you point me in the correct
>>>> direction?
>>>>
>>>
>>> rhev-m mostly uses the activex/xpi wrappers.
>>> cc-ing spice-devel on command line invocation (or client integrating
>>> with the REST API).
>>>
>>> one thing you will need is to call the engine via the API to set the
>>> "ticket" (password) of the VM, to pass to the client.
>>>
>> http://code.google.com/p/rhev-**api-labs/source/browse/python/**spice/<http://code.google.com/p/rhev-api-labs/source/browse/python/spice/>
>> is a fairly old example written for RHEV 2.2 based on the powershell
>> RHEV-M API, but I don't think this really changed.
>>
>
> actually, i just saw the ovirt cli has a console launch option.
> michael - does it launch spice as well, or only vnc?
>
> ______________________________**_________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/**mailman/listinfo/engine-devel<http://lists.ovirt.org/mailman/listinfo/engine-devel>
>
So I am assuming that building this connection up in a linux terminal on
Ovirt is more or less equal to setting it up using RHEV, but is that not
the case? Also what michael posted looks good, but I will need to wait
before I can actually dig into that code. In the end I am hoping to just
launch X and then launch the spicec session.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20120314/a91208f3/attachment-0002.html>
More information about the Devel
mailing list