| Table of Contents |
|---|
...
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. 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 or port 443 if SSL is used
- The websockify proxy also requires access to the management network address of every hypervisor in your infrastructure and its VNC port range
noVNC and websockify configuration diagram
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
...
| Tip |
|---|
Note that if you use a balancer for your websockify proxies, you need to edit the tightvnc.html file in client-premium webapp to point to the IP and port of the balancer. |
Installing HAProxy
You will need the gcc compiler and make to compile HAProxy.
...
| Code Block |
|---|
# chkconfig haproxy on |
System Diagrams
The following diagrams show the configuration of websockify with noVNC, and HAProxy loadbalancing websockify.
...