Branch 'uidmap-management' - scripts/cloudfsd.py scripts/views
Kaleb S. KEITHLEY
kkeithle at redhat.com
Mon Jun 13 13:47:07 UTC 2011
On 06/13/2011 09:40 AM, Jeff Darcy wrote:
> On 06/13/2011 09:11 AM, Kaleb KEITHLEY wrote:
>> scripts/cloudfsd.py | 26 +++++++++++++++++---------
>> scripts/views/tenant_volumes.html | 2 +-
>> scripts/views/volume_tenants.html | 32
>> ++++++++++++++++++++++++++++++++ 3 files changed, 50 insertions(+),
>> 10 deletions(-)
>>
>> New commits: commit 97ed9a10228b9fd92381f058a62b7c870338fdde Author:
>> Kaleb S. KEITHLEY<kkeithle at redhat.com> Date: Mon Jun 13 09:10:15
>> 2011 -0400
>>
>> implement volumes link on the tenant management page of the Web UI
>>
> The asymmetry between what tenant_volumes and volume_tenants might cause
> some confusion for users. Would it make sense to have them work more
> the same way? For example, in tenants_volumes:
>
>
> Tenant Management for Volume _code_
> +--------+----------+---------+----------+-----+-----------------+
> | Tenant | Password | UID low | UID high | ... | (remove access) |
> +--------+----------+---------+----------+-----+-----------------+
> + Alice | foo | 1000 | 1999 | ... | (remove access |
> +--------+----------+---------+----------+-----+-----------------+
> | Bob | bar | 2000 | 2999 | ... | (remove access |
> +--------+----------+---------+----------+-----+-----------------+
> (add tenant)
>
>
> Volume Management for Tenant _Alice_
> +--------+----------+---------+----------+-----+-----------------+
> | Volume | Password | UID low | UID high | ... | (remove access) |
> +--------+----------+---------+----------+-----+-----------------+
> + code | foo | 1000 | 1999 | ... | (remove access |
> +--------+----------+---------+----------+-----+-----------------+
> | data | foo | 7000 | 7999 | ... | (remove access |
> +--------+----------+---------+----------+-----+-----------------+
> (add volume)
>
>
> That's just one possibility, but you get the idea. Having the two
> tables look and work as mirrors of one another is likely to reduce user
> mis-steps.
>
That's ultimately where I want to go. But first I wanted to eliminate
the dead end link and elicit some buy in before I went ahead and did it.
More information about the cloudfs-devel
mailing list