[Users] ovirt VM custom properties

[Itamar Heim]

On 02/15/2012 05:34 PM, Brown, Chris (GE Healthcare) wrote:
> I assume the code for the Admin portal and PUP are shared (w/o looking)
> in regards to editing VM settings.
> Thus if I understand what you are saying, is that given proper
> permissions a power user would be able to view/edit the "custom
> properties".
> Any thoughts on a way now short of code changes to work around this
> (this is really a killer for our use cases)?
> An initial thought I had was to develop something perhaps a custom page
> (for now) leveraging the API to allow such changes.

you may have noticed the API allows this, but is limited to admins...
you could create a role of admin with limited permissions just like a 
power user role, and give it to these users.
only different from power user portal would be look and feel and the 
fact they could see VMs of others (and the rest of the entities in the 
system).
my view is the solution to this is to add a feature of permissions to 
custom properties, which requires making them entities, rather than a 
string, etc.

>
> Ultimately I see three core solutions to this issue:
> - The spice input/mouse interaction issues are resolved for all guests
> (old and new)
> - The UI allows for changes to the type of input device
> - Power users also have access to custom properties and can just use the
> vdsm hook instead.

as a temporary solution, would it hurt your new guests if you make the 
hook always enable the device? any other field in the vm you could base 
the decision on by the hook as an interim solution (it can go as hacky 
as vmname has X in it - hooks don't have to be based on custom properties).

>
> Let me know your thoughts.