Re: [one-users] cannot have two VNETs created by uid=0 on a single VM by another user

Thanks for the report, we'll take a look and check what's going on. You can follow the resolution in redmine: http://dev.opennebula.org/issues/502 Regards, Carlos. -- Carlos Martín, MSc Project Major Contributor OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org

Re: [one-users] cannot have two VNETs created by uid=0 on a single VM by another user

Hi again, I haven't been able to reproduce the error, in either one 2.0 or 2.2 branches. Unless all vnets are public, the authorization rejects the new VM. On the other hand, we may have confused you with this documentation quote: Virtual Networks created by oneadmin can be used by every other

Re: [one-users] cannot have two VNETs created by uid=0 on a single VM by another user

Thanks. I just replied your redmine case. So is it true to say that since 2.0, if a VNET is created by oneadmin (uid=0) and not published (the default), it cannot be used by other users? I actually find it is still usable by other users if there is only one VNET in the VM. FYI, my uid=0 is called

Re: [one-users] cannot have two VNETs created by uid=0 on a single VM by another user

By the way, this is a new problem in OpenNebula 2.x. I had similar setup working on version 1.4 without issue. Shi On Sat, Feb 26, 2011 at 4:59 PM, Shi Jin jinzish...@gmail.com wrote: Hi there, From the documentation, it says Virtual Networks created by oneadmin can be used by every other