Backlog #5125
Support for VNC/SPICE autoport rather than tracking in OpenNebula
Status: | Pending | Start date: | 04/23/2017 | |
---|---|---|---|---|
Priority: | High | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | Core & System | |||
Target version: | Release 5.6 |
Description
Attached is a patch that adds support for the VNC/SPICE port being specified as "auto" rather than a number. This translates into, for KVM only, autoport=yes in the libvirt domain XML file.
Importing is supported as well.
Using this bypasses the VNC port checks and each hypervisor will pick a free port when the VM is migrated or started on it.
This currently does not deal well with the situation where some ports are specified and some are automatic, since migrating a statically specified port VM onto a hypervisor that has some dynamically specified ones may result in the port being already in use by one using "auto". So attached is another patch which forces "auto" to be used.
Related issues
History
#1 Updated by Roy Keene about 4 years ago
I forgot to mention that it relies upon the script referenced in #2757 to convert the port "auto" into a number.
#2 Updated by Ruben S. Montero about 4 years ago
- Tracker changed from Feature to Backlog
- Category set to Core & System
- Priority changed from Normal to High
Makes sense, as mentioned this need to be integrated together with the port gathering to connect to the VM
#3 Updated by EOLE Team about 4 years ago
I missed this one, my #5151 seems to be a duplicate.
Regards.
#4 Updated by Ruben S. Montero almost 4 years ago
- Target version set to Release 5.6
#5 Updated by Ruben S. Montero almost 4 years ago
- Duplicated by Backlog #5151: Get list of open ports on hypervisor dynamically added
#6 Updated by Ruben S. Montero almost 4 years ago
- Duplicated by Bug #5227: VM can not start due to already binded VNC address added
#7 Updated by Ruben S. Montero over 3 years ago
- Related to Bug #5389: Vnc tries to bind to wrong port number added