Using noVNC in the current version of Abiquo
...
The proxy we will use is called websockify and it is included in the noVNC distribution package. This software should run on a separate machine from any other Abiquo service.When the user clicks on the eye icon, the client premium loads the VNC client (in this case noVNC) from the Abiquo Server. As we are going to replace part of the platform, some small changes will be needed in order for all of this to work with the current release of Abiquo.
Ports and Communications
...
- The Abiquo client GUI (noVNC client) requires access to the websockify proxy at its public IP address on port 41337.
- The websockify proxy requires access to the Abiquo API on port 80.
- The websockify proxy also requires access to the management network address of every hypervisor in your infrastructure
...
- and its VNC port range
...
Prerequisites
| Info | ||
|---|---|---|
| ||
The websockify proxy server described in this documentation was tested on CentOS 6.0 using Python 2.6 |
...
Replacing TightVNC applet with noVNC in the client-premium webapp
Download the noVNC distribution package from: http://kanaka.github.com/noVNC
Note that this is the same package we used for the websockify
...