Feature #2757

Make noVNC proxy work in a federation to access VMs in any zones

Added by Ruben S. Montero over 5 years ago. Updated over 1 year ago.

Status:NewStart date:02/26/2014
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Sunstone
Target version:Release 5.6
Resolution: Pull request:

Related issues

Duplicated by Feature #4308: OpenNebula Federation VNC MASTER/SLAVE Closed 01/25/2016

History

#1 Updated by Ruben S. Montero over 5 years ago

  • Target version changed from Release 4.6 to Release 4.8

#2 Updated by Ruben S. Montero about 5 years ago

  • Target version deleted (Release 4.8)

#3 Updated by Daniel Molina about 5 years ago

  • Tracker changed from Feature to Backlog

#4 Updated by Daniel Molina over 4 years ago

  • Assignee deleted (Javi Fontan)

#5 Updated by EDUARDO IGNACIO SERRANO over 3 years ago

Good morning
How to solve this problem.
I do not understand how to solve "We will work Sunstone Directly With The workaround for each Zone as"
Could you explain me please!
-Federation Master-> Slave
Failed to connect to VNC server (code: 1006)

#6 Updated by Ruben S. Montero over 3 years ago

  • Duplicated by Feature #4308: OpenNebula Federation VNC MASTER/SLAVE added

#7 Updated by Ruben S. Montero over 2 years ago

  • Tracker changed from Backlog to Feature
  • Target version set to Release 5.4

To address this issue we may integrate the following patches:

The basic idea is to get the IP:Port from an external script that forwards it to the target zone VNC proxy server. This can be done by setting up an SSH tunnel. We can integrate the changes and provide a template script to let people forward traffic using any VPN to the zones. An ssh tunnel based will be provided as an example (http://www.rkeene.org/viewer/tmp/zone-vnc-proxy.sh.htm)

#8 Updated by Roy Keene over 2 years ago

One additional change that I've found useful is that supplying the VM's name in addition to the hypervisor name, port, and zone ID to the script. This can be done by adding it as a 4th argument, e.g:

vnc_proxy_info = `opennebula-zones-vnc-proxy '#{host}' '#{vnc_port}' '#{vm_zone_id}' 'one-#{vm_resource['ID']}'`

This lets the script make other determinations -- such as how to interpret "vnc_port", which another patch I'm using can be "auto" if the hypervisor is managing the VNC port rather than OpenNebula.

#9 Updated by Tino Vázquez about 2 years ago

  • Target version changed from Release 5.4 to Release 5.6

#10 Updated by kvaps kvaps over 1 year ago

Spice also can be simple proxied by http-proxy (just squid for example), oVirt and Proxmox already use this feature.
I wrote about it in #5231

Also available in: Atom PDF