On 26 Jul 2017, at 15:39, Ondra Machacek <omachace(a)redhat.com>
wrote:
Hi,
one possible way is to add PowerUserRole to user on datacenter where you want
the users to operate. That way, they only can create VMs from
templates which are
public or they have direct permissions on and if the VM is created they can use
only that VM, and not any other.
On Wed, Jul 26, 2017 at 2:22 PM, Hari Gowtham <hgowtham(a)redhat.com> wrote:
> Hi,
>
> we have been trying to use ovirt to let the other devs in our team
> spawn vms and use it.
> we are nearly done with the setup. we have the hosted engine up,
> created gluster volumes and now we have setup the login to the portal
> too. While trying to spawn vms we noticed that,
> The admin can view, start or stop the vms on the machines which is fine.
> But we can see that the users can see each other user's vms too.
> This will make it possible for one user to start or stop other user's
> vm which we don't want to happen.
> we need to avoid this situation were one user has access to other user's vm.
> A particular user should be able to see the vms created by him alone
> So that he will have the ability to stop his own vms alone. What is
> the best way to create this setup?
is that within the admin portal? That’s for dmins which have visibility (not necessarily
control) to all VMs/infrastructure
There’s the User Portal (VM Portal since 4.1) for regular “powerless” user which can see
only their VMs
Thanks,
michal
>
> Is this the way it was designed to work or have i done something wrong here?
> Do let me know.
>
> --
> Regards,
> Hari Gowtham.
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users