incubator-cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kelven Yang <kelven.y...@citrix.com>
Subject RE: console proxy question
Date Mon, 14 May 2012 16:32:16 GMT
The decision of replacing with new VNC engine is primarily due to our shift to ASF, previous
console proxy uses third-party open source software that is not compatible to ASF license
policy.

The screen resolution problem has been fixed for certain hypervisors like VMware, however
as there is another security related changes for XenServer recently, the problem still exists
in XenServer, this will be fixed soon.

Kelven



> -----Original Message-----
> From: Tamas Monos [mailto:tamasm@veber.co.uk]
> Sent: Monday, May 14, 2012 7:08 AM
> To: cloudstack-users@incubator.apache.org
> Subject: console proxy question
> 
> Dear All,
> 
> I'm just having a thought about the console-proxy implementation in
> cloudstack.
> In 3.0.0 we had a console proxy that was able to follow screen resolution
> changes while from 3.0.1 upward this is gone.
> I saw on the devel list someone wrote/replaced the console-proxy part for
> some reason. Maybe there was a development reason for it however from
> user point of view it's just got worse.
> I get lots of heat because this resolution change problem. People
> building VMs with UI and done. They want to go a see the console straight
> away and they can't just half of the screen..
> 
> Is there a way to forcefully reinstall the console-proxy package from
> 3.0.0 onto a 3.0.1/2 installation? Would that fix this problem at all?
> 
> Regards
> 
> Tamas Monos                                               DDI
> +44(0)2034687012
> Chief Technical                                             Office
> +44(0)2034687000
> Veber: The Hosting Specialists               Fax         +44(0)871 522
> 7057
> http://www.veber.co.uk<http://www.veber.co.uk/>
> 
> Follow us on Twitter:
> www.twitter.com/veberhost<http://www.twitter.com/veberhost>
> Follow us on Facebook:
> www.facebook.com/veberhost<http://www.facebook.com/veberhost>


Mime
View raw message