Hi, I don't think you can do that right now (unless you manually set the vnc port in your templates).
It sounds like a good thing to have, though. Please open a feature request at http://dev.opennebula.org and we'll consider it for future releases Cheers -- Join us at OpenNebulaConf2013 in Berlin, 24-26 September, 2013 -- Carlos Martín, MSc Project Engineer OpenNebula - The Open-source Solution for Data Center Virtualization www.OpenNebula.org | [email protected] | @OpenNebula<http://twitter.com/opennebula><[email protected]> On Tue, May 7, 2013 at 2:11 PM, Ricardo Duarte <[email protected]> wrote: > Hi there, > > > I had a look at how OpenNebula assigns the VNC port, and it looks like it > can result in some trouble for me in the future. > As far as I can see, the VNC port is built with the instance ID. As the > instance ID is a running number, this poses a limit of ~60000 machines > during all the lifetime of an OpenNebula cloud. Also, it requires a very > large range of ports to be open on the firewall. > Is there a way to make it allocate the next free port on a range, and not > depend on the instance id? > > Thanks, > Ricardo > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > >
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
