Hi again,<div><br></div><div>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.</div><div><br></div><div>On the other hand, we may have confused you with this documentation quote:</div>
<div><meta charset="utf-8"><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">> Virtual Networks created by oneadmin can be used by every other user.</span></div>
<div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; "><br></span></div><div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">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.</span></div>
<div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; "><br></span></div><div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">Regards,</span></div>
<div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">Carlos.</span></div><div><br clear="all"><span style="border-collapse:collapse;color:rgb(136, 136, 136);font-family:arial, sans-serif;font-size:13px">--<br>
Carlos Martín, MSc<br>Project Major Contributor<br><span style="background-color:rgb(255, 255, 204);color:rgb(34, 34, 34);background-repeat:initial initial">OpenNebula</span> - The Open Source Toolkit for Cloud Computing<br>
<a href="http://www.opennebula.org/" style="color:rgb(42, 93, 176)" target="_blank">www.<span style="background-color:rgb(255, 255, 204);color:rgb(34, 34, 34);background-repeat:initial initial">OpenNebula</span>.org</a> | <a href="mailto:cmartin@opennebula.org" style="color:rgb(42, 93, 176)" target="_blank">cmartin@<span style="background-color:rgb(255, 255, 204);color:rgb(34, 34, 34);background-repeat:initial initial">opennebula</span>.org</a></span><br>
<br><br><div class="gmail_quote">2011/2/28 Carlos Martín Sánchez <span dir="ltr"><<a href="mailto:cmartin@opennebula.org" target="_blank">cmartin@opennebula.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks for the report, we'll take a look and check what's going on.<div>You can follow the resolution in redmine:<br><div><a href="http://dev.opennebula.org/issues/502" target="_blank">http://dev.opennebula.org/issues/502</a></div>
<div><br></div><div>Regards,</div><div>Carlos.<br clear="all"><span style="border-collapse:collapse;color:rgb(136, 136, 136);font-family:arial, sans-serif;font-size:13px">--<br>Carlos Martín, MSc<br>Project Major Contributor<br>
<span style="background-color:rgb(255, 255, 204);color:rgb(34, 34, 34);background-repeat:initial initial">OpenNebula</span> - The Open Source Toolkit for Cloud Computing<br><a href="http://www.opennebula.org/" style="color:rgb(42, 93, 176)" target="_blank">www.<span style="background-color:rgb(255, 255, 204);color:rgb(34, 34, 34);background-repeat:initial initial">OpenNebula</span>.org</a> | <a href="mailto:cmartin@opennebula.org" style="color:rgb(42, 93, 176)" target="_blank">cmartin@<span style="background-color:rgb(255, 255, 204);color:rgb(34, 34, 34);background-repeat:initial initial">opennebula</span>.org</a></span><br>
<br><br><div class="gmail_quote"><div><div></div><div>On 27 February 2011 01:01, Shi Jin <span dir="ltr"><<a href="mailto:jinzishuai@gmail.com" target="_blank">jinzishuai@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div>
By the way, this is a new problem in OpenNebula 2.x. I had similar setup working on version 1.4 without issue.<div><br></div><div>Shi<div><div></div><div><br><br><div class="gmail_quote">On Sat, Feb 26, 2011 at 4:59 PM, Shi Jin <span dir="ltr"><<a href="mailto:jinzishuai@gmail.com" target="_blank">jinzishuai@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi there,<div><br></div><div>From the documentation, it says</div><div>> Virtual Networks created by oneadmin can be used by every other user.</div>
<div><br></div><div>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.</div>
<div><br></div><div>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:</div><div>> Sat Feb 26 16:51:44 2011 [ReM][E]: [VirtualMachineAllocate] User [6] not authorized to perform CREATE on VM Pool<br clear="all">
If I publish any one of the VNET, the dual NIC setup would work again.</div><div><br></div><div>I think this is probably a bug, right?<br>-- <br>Shi Jin, Ph.D.<br><br>
</div>
</blockquote></div><br><br clear="all"><br></div></div>-- <br>Shi Jin, Ph.D.<br><br>
</div>
<br></div></div>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
<br></blockquote></div><br></div></div>
</blockquote></div><br></div>