[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16712014#comment-16712014
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10025:
-

svenvogel commented on issue #2204: [CLOUDSTACK-10025] Adding Support for NoVNC 
Console for KVM and XENSERVER
URL: https://github.com/apache/cloudstack/pull/2204#issuecomment-445024138
 
 
   @syed is there any updates on the html 5 console?


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
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618898#comment-16618898
 ] 

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-422343457
 
 
   @syed any updates on this? really looking forward to this


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
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558015#comment-16558015
 ] 

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-408006346
 
 
   Looking forward to it @syed !


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
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16552184#comment-16552184
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10025:
-

svenvogel commented on issue #2204: [CLOUDSTACK-10025] Adding Support for NoVNC 
Console for KVM and XENSERVER
URL: https://github.com/apache/cloudstack/pull/2204#issuecomment-406901030
 
 
   Hi @syed that would be great!!!


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
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16550839#comment-16550839
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10025:
-

syed commented on issue #2204: [CLOUDSTACK-10025] Adding Support for NoVNC 
Console for KVM and XENSERVER
URL: https://github.com/apache/cloudstack/pull/2204#issuecomment-406623411
 
 
   Sorry guys, I have been pulled into various things and it's a challenge to 
find time. I have to do this on my own time. I'll try to get to it this weekend.


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
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16547622#comment-16547622
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10025:
-

svenvogel commented on issue #2204: [CLOUDSTACK-10025] Adding Support for NoVNC 
Console for KVM and XENSERVER
URL: https://github.com/apache/cloudstack/pull/2204#issuecomment-405875150
 
 
   ping @syed some news on theis pull request?


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
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478929#comment-16478929
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10025:
-

wido commented on issue #2204: [CLOUDSTACK-10025] Adding Support for NoVNC 
Console for KVM and XENSERVER
URL: https://github.com/apache/cloudstack/pull/2204#issuecomment-389836720
 
 
   @syed Could you take a look at this one and fix the conflicts?


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
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16459737#comment-16459737
 ] 

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-385693082
 
 
   ping @syed 


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
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360947#comment-16360947
 ] 

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-364967523
 
 
   @syed great, happy to collaborate you've my support. Perhaps we can also get 
some help from @ustcweizhou and others who may have worked on novnc integration.


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
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360892#comment-16360892
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10025:
-

syed commented on issue #2204: [CLOUDSTACK-10025] Adding Support for NoVNC 
Console for KVM and XENSERVER
URL: https://github.com/apache/cloudstack/pull/2204#issuecomment-364958976
 
 
   @rhtyd Sorry for dropping the ball on this. We will be looking at working on 
this in the coming months.


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
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307993#comment-16307993
 ] 

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-354761308
 
 
   Ping, any updates? I'll remove this from 4.11 milestone due to lack of 
engagement, a response from the author, reviewers and discussions. Hopefully, 
we can get this stabilized, reviewed/tested merged for a future release.


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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296351#comment-16296351
 ] 

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-352660130
 
 
   @syed  any update on this?


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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[Tutkowski, Mike (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16293360#comment-16293360
 ] 

Tutkowski, Mike commented on CLOUDSTACK-10025:
--

Hi,

You can find information on how to unsubscribe here:

https://cloudstack.apache.org/mailing-lists.html

Thanks,
Mike

On Dec 11, 2017, at 1:10 AM, Mohammad Aladwan 
> wrote:

hi,

please i want to leave this group,i am not sure how i  can leave it


my best regards

On Mon, Dec 11, 2017 at 1:55 AM, ASF GitHub Bot (JIRA) 
>
wrote:


   [ https://issues.apache.org/jira/browse/CLOUDSTACK-10025?
page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&
focusedCommentId=16285617#comment-16285617 ]

ASF GitHub Bot commented on CLOUDSTACK-10025:
-

sachinnitw1317 commented on issue #2204: [CLOUDSTACK-10025] Adding Support
for NoVNC Console for KVM and XENSERVER
URL: https://github.com/apache/cloudstack/pull/2204#issuecomment-350647294


  Hey, I reported the keyboard problem earlier as well. If you do a right
click -> reload frame it will start taking your keyboard strokes. I never
got the fix though. Let me  know if you need any help from me.


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)



> 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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16286129#comment-16286129
 ] 

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-350774975
 
 
   @sachinnitw1317 the expectation is that once you've the novnc console/UI you 
should be able to click on ti and start typing. Anyway to fix that?


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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285661#comment-16285661
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10025:
-

asfbot commented on issue #2204: [CLOUDSTACK-10025] Adding Support for NoVNC 
Console for KVM and XENSERVER
URL: https://github.com/apache/cloudstack/pull/2204#issuecomment-350661280
 
 
   Sigert GOEMINNE  on d...@cloudstack.apache.org replies:
   Hi,
   
   Send an email to dev-unsubscr...@cloudstack.apache.org to unsubscribe from
   the mailing list. (https://cloudstack.apache.org/mailing-lists.html)
   
   Kind regards,
   Sigert
   
   *Sigert Goeminne*
   Software Development Engineer
   
   *nuage*networks.net 
   Copernicuslaan 50
   2018 Antwerp
   Belgium


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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285629#comment-16285629
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10025:
-

asfbot commented on issue #2204: [CLOUDSTACK-10025] Adding Support for NoVNC 
Console for KVM and XENSERVER
URL: https://github.com/apache/cloudstack/pull/2204#issuecomment-350650334
 
 
   Mohammad Aladwan  on d...@cloudstack.apache.org replies:
   hi,
   
   please i want to leave this group,i am not sure how i  can leave it
   
   
   my best regards


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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[Mohammad Aladwan (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285625#comment-16285625
 ] 

Mohammad Aladwan commented on CLOUDSTACK-10025:
---

hi,

please i want to leave this group,i am not sure how i  can leave it


my best regards

On Mon, Dec 11, 2017 at 1:55 AM, ASF GitHub Bot (JIRA) 



> 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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285617#comment-16285617
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10025:
-

sachinnitw1317 commented on issue #2204: [CLOUDSTACK-10025] Adding Support for 
NoVNC Console for KVM and XENSERVER
URL: https://github.com/apache/cloudstack/pull/2204#issuecomment-350647294
 
 
   Hey, I reported the keyboard problem earlier as well. If you do a right 
click -> reload frame it will start taking your keyboard strokes. I never got 
the fix though. Let me  know if you need any help from me.


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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285399#comment-16285399
 ] 

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-350585600
 
 
   @syed ping?


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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266115#comment-16266115
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10025:
-

syed commented on issue #2204: [CLOUDSTACK-10025] Adding Support for NoVNC 
Console for KVM and XENSERVER
URL: https://github.com/apache/cloudstack/pull/2204#issuecomment-347027241
 
 
   @rhtyd I'm going to look at this tomorrow


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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263967#comment-16263967
 ] 

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-346554784
 
 
   I've rebased this branch, fixed build and backend issues, upgraded noVNC to 
v0.6.2. I could get a console now, but it fails to register keyboard strokes. 
@syed @ustcweizhou -- please review, advise.


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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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 
` ` 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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16239625#comment-16239625
 ] 

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  
 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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[Sachin (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16239390#comment-16239390
 ] 

Sachin commented on CLOUDSTACK-10025:
-

Rohit can you please share the exact link you are using to access it?




> 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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[Sachin (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16239380#comment-16239380
 ] 

Sachin commented on CLOUDSTACK-10025:
-

Hello Sir,

Will check it and let you know by tomorrow.

Regards,
Sachin




> 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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16239082#comment-16239082
 ] 

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-341908982
 
 
   @sachinnitw1317 the /novnc/ url is not working for me for KVM, can you 
check? /cc @syed 


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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238918#comment-16238918
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10025:
-

blueorangutan commented on issue #2204: [CLOUDSTACK-10025] Adding Support for 
NoVNC Console for KVM and XENSERVER
URL: https://github.com/apache/cloudstack/pull/2204#issuecomment-341888900
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1207


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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238903#comment-16238903
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10025:
-

blueorangutan commented on issue #2204: [CLOUDSTACK-10025] Adding Support for 
NoVNC Console for KVM and XENSERVER
URL: https://github.com/apache/cloudstack/pull/2204#issuecomment-341887717
 
 
   @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted 
as I make progress.


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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238902#comment-16238902
 ] 

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-341887691
 
 
   @blueorangutan package


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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238901#comment-16238901
 ] 

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-341887394
 
 
   @sachinnitw1317 can you rebase this branch and add me to your repo/branch as 
a collaborator, I would like to work with you, try and get this reviewed, 
tested and accepted.
   
   Update -- nevermind, I found I had write access, have rebased against latest 
master and fixed conflicts.


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)

[jira] [Commented] (CLOUDSTACK-10025) To create a better VNC client for Cloudstack using noVNC

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238897#comment-16238897
 ] 

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-341887394
 
 
   @sachinnitw1317 can you rebase this branch and add me to your repo/branch as 
a collaborator, I would like to work with you, try and get this reviewed, 
tested and accepted.


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)