This is something I've been contemplating doing on Cloudstack for a while but have lacked time to dig deep on implementation or do actual coding. The only way to do what you're trying to do without accessing the database or console logs directly is to completely replace the console proxy....or at least add a new one. Or add an API to query for the data. If you go that route, I'd do a feature request to be able to disable console entirely :)
You cannot access the VNC console directly from the public network, only from the management network. The current console proxy implementation has you connect directly to the console proxy on its public interface, which creates an HTML console of the VNC connection it has established to the hypervisor. If cloudstack were changed to use the console proxy as a Hypervisor VNC --> NOVNC then that information could be displayed in NOVNC on the console Proxy or better yet, Proxied from Console Proxy to Console negating the need for DNS entries on the public side for console access while still not requiring an agent on the hypervisor (though for KVM that is already present) On Thu, Dec 11, 2014 at 12:21 AM, Anshul Gangwar <[email protected]> wrote: > > Even if you have below info you cannot connect to console of VM from > outside. > > Actually we are using hypervisor provided VNC server to connect to > consoles. > So to connect to console you need to be on that hypervisor as console > services are running on localhost(127.0.0.1). > Which probably will not server your purpose. > > Also providing this info via API will lead into security issues. > > > From: 吕海蛟 [mailto:[email protected]] > Sent: Thursday, December 11, 2014 8:43 AM > To: [email protected] > Cc: 'tangwenjun_215' > Subject: Replace the Built-in VNC Console > > Hi, > > To improve the user experience of using the built-in VNC console of > CloudStack, we are studying the possibility to replace that with NOVNC. > > To achieve this, we need get the following information of target VM and > import to NOVNC, > > > 1. VM-ID ( no problem, > can be acquired from API) > > 2. IP of VM (no problem, > can be acquired from API) > > 3. VNC port of target VM (seems unavailable from API) > > 4. VNC password of target VM (seems unavailable from API) > > We are stuck due to unable to acquire the VNC port and password of target > VM through API. > > Any advice for how to obtain this both ? or any other alternative way to > improve the built-in VNC console performance ? > > Thanks ! > > > > [private cloud2] We Deliver Enterprise-Grade Cloud ! > > ------------------------------------------------------------------------------ > 吕海蛟 > Product Engineering & Innovation Center (PEIC) > 华胜蓝泰科技（天津）有限责任公司 > > > 上海闵行区合川路2679号虹桥国际商务广场B栋601室 > 邮编：201103 > Office: +86-21-62351222 > Mobile: +86-18602198181 > > > >
