Hi,
The scenario you describe was indeed a limitation of OpenNebula 3.0.
The permissions have been greatly improved in the recently released
OpenNebula 3.2, so I advise you to upgrade [1], and take a look at the new
user, group, other permissions [2].
Your VMs will be now private by default, or with the new nomenclature,
'600' or 'um- --- ---'
Regards.
[1] http://opennebula.org/documentation:rel3.2:upgrade
[2] http://opennebula.org/documentation:rel3.2:chmod
--
Carlos Martín, MSc
Project Engineer
OpenNebula - The Open Source Toolkit for Data Center Virtualization
www.OpenNebula.org | cmar...@opennebula.org |
@OpenNebulahttp://twitter.com/opennebulacmar...@opennebula.org
On Mon, Dec 5, 2011 at 12:58 PM, davood ghatreh davood.gh2...@gmail.comwrote:
Hi everyone,
I have created two users, both in the same group. I did it to let them use
the same images/networks/templates, but they are completely distinct. Now
they can see each other VMs and can simply login using VNC and make change
to each other vms. This is not what I want. And I don't want to create
distinct group for each of them, because i will have to make the same
images/templates/etc for them, because you cant chogrp a template to two
groups simultaneously.
Would you please provide me with a solution to figure it out?
Thanks all
___
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
