[Ovirt-devel] Questions on the Server Suite UI
sseago at redhat.com
Mon Nov 17 16:25:52 UTC 2008
Bryan Kearney wrote:
> Scott Seago wrote:
>> Bryan Kearney wrote:
>>> Below are a couple of functional question on the UI having installed
>>> it, and reviewed version .6 of the docs. I realize the answer may be
>>> "in an upcoming release", but I wanted to at least throw it out:
>>> 1) Can I set quotas at the VM pool level, or are they only inherited
>>> from the hardware pool?
>> Yes -- in fact the VM pool is the primary usage of quotas. At the
>> hardware pool level, quotas are only meaningful as 'default' values
>> inherited by VM pools that don't specify quotas.
> Ok.. my version does not have the ability to edit. Is that a bug or a
> "to be added" feature?
If your wui doesn't allow it now, sounds like a bug., We actually
implemented VM pool quota editing _before_ HW pool quota editing. But I
haven't looked at this functionality in a while. Feel free to add a bug.
>>> 4) In the appliance setup, is there a ui path to add users to LDAP?
>> As far as I know the only way to do this is via the IPA web UI or
>> other IPA APIs. Although we are creating the ovirtadmin user, so it
>> probably wouldn't be hard to use whatever API this uses to include
>> other users as well.
> On the appliance, is the LDAP UI exposed some place?
It's exposed via hte freeIPA UI at /ipa
>>> 5) In the docs it says that a user is defined at the Hardware / VM
>>> pool level and can not be moved. But, I assume that a person can
>>> have access to many hardware or VM pools. Is that accurate?
>> Sounds like the wording is a bit off there. Here's what's going on:
>> 1) users aren't created in the ovirt WUI but in IPA
>> 2) for any hardware or VM pool, users can be granted access
>> 3) when a user has access to a pool, he can access that pool and any
>> pool below it (i.e. if a user can access a HW pool, that user can
>> access all sub-HW pools and VM pools within it -- the admin user who
>> can access the 'default' pool at top can access all pools
>> 4) there are no limits on how many pools a user can be granted access to
>> 5) but no, there isn't a way to transfer a user permission to another
>> pool, since all that would mean would be that you're granting access
>> in one place and revoking it elsewhere.
> Ok.. that make sense. I did not read the doco that way.
Maybe that bit of the doc should be revisited.
More information about the ovirt-devel