Return-Path: X-Original-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0227DEFC0 for ; Wed, 20 Feb 2013 06:23:09 +0000 (UTC) Received: (qmail 95214 invoked by uid 500); 20 Feb 2013 06:23:07 -0000 Delivered-To: apmail-incubator-cloudstack-users-archive@incubator.apache.org Received: (qmail 95103 invoked by uid 500); 20 Feb 2013 06:23:07 -0000 Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-users@incubator.apache.org Delivered-To: mailing list cloudstack-users@incubator.apache.org Received: (qmail 94957 invoked by uid 99); 20 Feb 2013 06:23:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Feb 2013 06:23:01 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of aemneina@gmail.com designates 209.85.212.179 as permitted sender) Received: from [209.85.212.179] (HELO mail-wi0-f179.google.com) (209.85.212.179) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Feb 2013 06:22:54 +0000 Received: by mail-wi0-f179.google.com with SMTP id ez12so5766013wid.6 for ; Tue, 19 Feb 2013 22:22:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:reply-to:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=A3VoZ/7wPVBvYOYLvSA9nNVS+7ZIPIE3yW3ILyfzp58=; b=ZJTGxZ5vu7OIgjqN5r2o6zg6dWAIzoIyEXN2NzZo/eNw9PQcp/SKMEaWxu4ntdVLby Ajh34f2n/wCxyOuLeHoTcvFejR+06zhYq4u3xvdrTrDhYI5ibarKbiASp1CcPgPgZoj9 lb+pzWFtN0/eLCOhx+H+mAMTNEKyevp4gPjYxwVyipcL/ajUmIKlOP5ci9oZHT7Uob92 O0BOkN/VxZGEnWYtEDXhh/36uwfPdrV1Yyd0VeKhZ08oGV/hmOjlEupwmFhfRaJdY33t W84e5RUALci8SwrHx3iemHsJVAyCKxiEKqF63jxZqCmO1vALBcRne8z4frx64e4y9Zfq HtJA== X-Received: by 10.194.87.100 with SMTP id w4mr31044058wjz.48.1361341354125; Tue, 19 Feb 2013 22:22:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.19.40 with HTTP; Tue, 19 Feb 2013 22:22:14 -0800 (PST) Reply-To: aemneina@gmail.com In-Reply-To: References: From: Ahmad Emneina Date: Tue, 19 Feb 2013 22:22:14 -0800 Message-ID: Subject: Re: spice protocol integration with cloudstack To: Cloudstack users Content-Type: multipart/alternative; boundary=047d7bf10a16d4a7dc04d621fb1f X-Virus-Checked: Checked by ClamAV on apache.org --047d7bf10a16d4a7dc04d621fb1f Content-Type: text/plain; charset=ISO-8859-1 On Tue, Feb 19, 2013 at 9:58 PM, Ignazio Cassano wrote: > I am afraid cloudstack never will include spice because citrix has got the > ica hdx vdi protocol . > its not up to citrix, as to what makes it into cloudstack, so I'm not sure why cloudstack wouldnt include it... esp if someone implemented it AND it were accepted by the community. I'd personally like to see this solution in cloudstack, users can enable it or the console proxy... or both! it has the potential to provide a richer desktop experience than the console proxy (sorry Kelven :p ). What i wonder is how one manages and secures the access. > As far as kvm is concerned, I read someone is working on xen spice > integration . > regards > ignazio > Il giorno 18/feb/2013 07:34, "David Nalley" ha scritto: > > > On Mon, Feb 18, 2013 at 1:17 AM, Sunilreddy Kovvuri > > wrote: > > > Hi, > > > > > > I compiled spice 0.10.1.I want to use spice instead of vnc iin > > > cloudstack. How to integrate spice with cloudstack? > > > > So there are a few different places you'd need to make changes in source > > code: > > > > First - agent code to tell CloudStack to spawn machines that use SPICE > > > > Second - there's the functionality that the console proxy provides > > (essentially it proxies the vnc session to provide isolation of the > > end user from the hypervisor, and presents that as a javascript > > interface to the end user.) So I suppose you could use something like > > spice-html5. > > > > All of that said, I am not certain that this is the best path - the > > console proxy isn't really designed for true remote desktop > > functionality like RDP and SPICE provide, but rather to be something > > akin to OBM/LOM access on a physical server - good enough when you > > have no network, but not something you'd tolerate every day. It's also > > KVM-specific afaik. > > > > --David > > > --047d7bf10a16d4a7dc04d621fb1f--