Using noVNC in Abiquo 2.x - 3.6.x

By default Abiquo has an integrated TightVNC applet viewer to provide remote connections to VM consoles. This can be changed to noVNC, an HTML5 VNC viewer, by following the steps below.

For Abiquo 3.8+ see Using noVNC in Abiquo 3.8 and above

Caveats

• 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 component will be overwritten. During your upgrade, allow time to copy the noVNC component to the client-premium or UI webapp of the new version and to test the configuration.

...

• -a: The API URL to connect to. Should be the same as abiquo.server.api.location property in abiquo.properties file.
• -u: The username that will be used to interact with the API. Requires a role with next privileges: 
  
  • USERS_MANAGE_ENTERPRISE, ENTERPRISE_ADMINISTER_ALL, VDC_ENUMERATE, VAPP_CUSTOMIZE_SETTINGS
• -p: The password for the user.
• -f: The file the results will be written too.

...

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

...