| Table of Contents |
|---|
...
- You must add a proxy to forward websockets requests to traditional sockets. This proxy should be installed on a separate machine from any other Abiquo service.
- You must define a password for VMs in ESXi in order to be able to connect.
- At the time of writing, noVNC does not support user specified keyboard mappings, so these will not be taken into account.
- When you upgrade to the next version of Abiquo, the noVNC setup will be overwritten. During your upgrade, allow time to copy the noVNC component to the client-premium webapp of the new version.
Background
Because noVNC uses websockets to establish connections, instead of traditional sockets, we will need to set up an additional piece of software that will forward these requests. Moreover, this software can also act as a proxy for VNC connections, so you only need to expose one IP/Port to the Internet, and through this, you can connect to any VM on your Abiquo platform.
...
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
...