[
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239627#comment-16239627
]
ASF GitHub Bot commented on CLOUDSTACK-10025:
---------------------------------------------
rhtyd commented on issue #2204: [CLOUDSTACK-10025] Adding Support for NoVNC
Console for KVM and XENSERVER
URL: https://github.com/apache/cloudstack/pull/2204#issuecomment-341985286
@sachinnitw1317 here are the issues I faced:
If the console is opened normally (the old console/tile-based proxy), every
new tab opened will invalidate the session of the older (previously opened
window/console). However, this does not happen with novnc based console which
fails to get/load the websocket URL (upgrade url fails) if the console for the
same VM was previously opened with older vnc (tile-based, the `/ajax` path)
provider.
The other issue I'm seeing is when I copy and use the console url and append
`websocketconsole=true`, it does open `/novnc/` path in the iframe however,
it's bit flaky. For example, if I open the window more than once, the older
session/tab/popup should be invalidated without which sometimes what happens is
console does open but is not responsive to inputs (keyboard strokes). I've
tested this so far only on KVM, I'm planning to do the same for VMware and
XenServer next week. /cc @syed
Rebasing notes: I've rebased and fixed conflicts on your branch against
latest master, if you wish to work on it please do a git pull --rebase
`<remote> <branch>` against your local branch. Thanks.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> To create a better VNC client for Cloudstack using noVNC
> --------------------------------------------------------
>
> Key: CLOUDSTACK-10025
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10025
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VNC Proxy
> Affects Versions: 4.11.0.0
> Reporter: Sachin
> Priority: Minor
> Labels: features
>
> I have implemented this feature as my GSoC'17 project. noVNC is written in
> javascript and uses websockets to connect to VNC server. We have modified the
> ConsoleProxy server to accept websocket request from noVNC client, which then
> forwards the request request to VNC server.
> Javascript cannot make plain tcp request, hence the websocket request have to
> be forwarded to the VNC server via a proxy server that basically converts
> websocket request from client to plain tcp request for VNC server.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
