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

[Shi Jin]

Hi there,

>From the documentation, it says
>  Virtual Networks created by oneadmin can be used by every other user.

I have created two vNETs, intranet-office and LAN-1, both created by the
oneadmin user (uid=0) and as the document says, any other user can use these
vnets, at least in my experience, one VNET per VM.

But I found that if another user wants to deploy a VM with two NICs, both
owned by uid=0, then we will get a permission error:
> Sat Feb 26 16:51:44 2011 [ReM][E]: [VirtualMachineAllocate] User [6] not
authorized to perform CREATE on VM Pool
If I publish any one of the VNET, the dual NIC setup would work again.

I think this is probably a bug, right?
-- 
Shi Jin, Ph.D.
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

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

[Shi Jin]

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  wrote:

> Hi there,
>
> From the documentation, it says
> >  Virtual Networks created by oneadmin can be used by every other user.
>
> I have created two vNETs, intranet-office and LAN-1, both created by the
> oneadmin user (uid=0) and as the document says, any other user can use these
> vnets, at least in my experience, one VNET per VM.
>
> But I found that if another user wants to deploy a VM with two NICs, both
> owned by uid=0, then we will get a permission error:
> > Sat Feb 26 16:51:44 2011 [ReM][E]: [VirtualMachineAllocate] User [6] not
> authorized to perform CREATE on VM Pool
> If I publish any one of the VNET, the dual NIC setup would work again.
>
> I think this is probably a bug, right?
> --
> Shi Jin, Ph.D.
>
>


-- 
Shi Jin, Ph.D.
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

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

[Carlos Martín Sánchez]

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  | cmar...@opennebula.org


On 27 February 2011 01:01, Shi Jin  wrote:

> 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  wrote:
>
>> Hi there,
>>
>> From the documentation, it says
>> >  Virtual Networks created by oneadmin can be used by every other user.
>>
>> I have created two vNETs, intranet-office and LAN-1, both created by the
>> oneadmin user (uid=0) and as the document says, any other user can use these
>> vnets, at least in my experience, one VNET per VM.
>>
>> But I found that if another user wants to deploy a VM with two NICs, both
>> owned by uid=0, then we will get a permission error:
>> > Sat Feb 26 16:51:44 2011 [ReM][E]: [VirtualMachineAllocate] User [6] not
>> authorized to perform CREATE on VM Pool
>> If I publish any one of the VNET, the dual NIC setup would work again.
>>
>> I think this is probably a bug, right?
>> --
>> Shi Jin, Ph.D.
>>
>>
>
>
> --
> Shi Jin, Ph.D.
>
>
> ___
> Users mailing list
> Users@lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

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

[Carlos Martín Sánchez]

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 user.

That was how VNets were shared in OpenNebula 1.4. Since 2.0, oneadmin's
VNets are shared using the 'onevnet publish' command, just like any other
user's. The guide is now fixed, sorry for the confusion.

Regards,
Carlos.

--
Carlos Martín, MSc
Project Major Contributor
OpenNebula - The Open Source Toolkit for Cloud Computing
www.OpenNebula.org  | cmar...@opennebula.org


2011/2/28 Carlos Martín Sánchez 

> 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  | cmar...@opennebula.org
>
>
> On 27 February 2011 01:01, Shi Jin  wrote:
>
>> 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  wrote:
>>
>>> Hi there,
>>>
>>> From the documentation, it says
>>> >  Virtual Networks created by oneadmin can be used by every other user.
>>>
>>> I have created two vNETs, intranet-office and LAN-1, both created by the
>>> oneadmin user (uid=0) and as the document says, any other user can use these
>>> vnets, at least in my experience, one VNET per VM.
>>>
>>> But I found that if another user wants to deploy a VM with two NICs, both
>>> owned by uid=0, then we will get a permission error:
>>> > Sat Feb 26 16:51:44 2011 [ReM][E]: [VirtualMachineAllocate] User [6]
>>> not authorized to perform CREATE on VM Pool
>>> If I publish any one of the VNET, the dual NIC setup would work again.
>>>
>>> I think this is probably a bug, right?
>>> --
>>> Shi Jin, Ph.D.
>>>
>>>
>>
>>
>> --
>> Shi Jin, Ph.D.
>>
>>
>> ___
>> Users mailing list
>> Users@lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>>
>
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

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

[Shi Jin]

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 cloudadmin instead of oneadmin but I don't think it
should create any problem, right?

Thank you very much.

Shi
2011/2/28 Carlos Martín Sánchez 

> 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 user.
>
> That was how VNets were shared in OpenNebula 1.4. Since 2.0, oneadmin's
> VNets are shared using the 'onevnet publish' command, just like any other
> user's. The guide is now fixed, sorry for the confusion.
>
> Regards,
> Carlos.
>
> --
> Carlos Martín, MSc
> Project Major Contributor
> OpenNebula - The Open Source Toolkit for Cloud Computing
> www.OpenNebula.org  | cmar...@opennebula.org
>
>
> 2011/2/28 Carlos Martín Sánchez 
>
> 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  | cmar...@opennebula.org
>>
>>
>> On 27 February 2011 01:01, Shi Jin  wrote:
>>
>>> 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  wrote:
>>>
 Hi there,

 From the documentation, it says
 >  Virtual Networks created by oneadmin can be used by every other user.

 I have created two vNETs, intranet-office and LAN-1, both created by the
 oneadmin user (uid=0) and as the document says, any other user can use 
 these
 vnets, at least in my experience, one VNET per VM.

 But I found that if another user wants to deploy a VM with two NICs,
 both owned by uid=0, then we will get a permission error:
 > Sat Feb 26 16:51:44 2011 [ReM][E]: [VirtualMachineAllocate] User [6]
 not authorized to perform CREATE on VM Pool
 If I publish any one of the VNET, the dual NIC setup would work again.

 I think this is probably a bug, right?
 --
 Shi Jin, Ph.D.


>>>
>>>
>>> --
>>> Shi Jin, Ph.D.
>>>
>>>
>>> ___
>>> Users mailing list
>>> Users@lists.opennebula.org
>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>
>>>
>>
>


-- 
Shi Jin, Ph.D.
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org