On 07/25/2012 09:26 AM, Tzu-Mainn Chen wrote:
----- Original Message -----
> From: "JaromÃr Coufal"<jcoufal(a)redhat.com>
> To: "aeolus-devel"<aeolus-devel(a)lists.fedorahosted.org>
> Sent: Wednesday, July 25, 2012 6:34:21 AM
> Subject: Re: RFC: Adding Useful reports and Statistical Data
>
snip
> Hi,
>
> without any doubts statistical data are valuable and it is really
> good to have that in our system. But as Jirka mentioned, we need to
> be careful about main purpose of administration section. Right now,
> statistics are preventing us from main point of administrators - as
> for providers it is their and account management.
>
> In current state, imagine that you are administrators and you want to
> add account. How will you do that? It looks like very simple step.
> Very likely you will go to Administrator section, to Cloud Providers
One thing to keep in mind, we have no "administration" section as such
-- the "administer" tab is badly-named and we need to revisit. The top
level tabs ("monitor" and "administer") are, contrary to what might be
implied by the current names, not splitting by function, but by resource
type. "Monitor" contains pool/deployment/instance-level stuff, and
"administer" contains provider, pool family, image management, etc. The
point is that for a given resource, you don't go to one tab to "use" it
and the other to "administer" it -- for pools, user-level and
admin-level functions are on the same page. If you lack the proper
admin-level permissions, that stuff is hidden from you. Same with
images, pool families, providers on the "administer" side -- the same
pages are used for user-level and admin-level stuff, with some things
hidden based on permissions.
Also, keep in mind that the notion of "user" and "adminstrator"
doesn't
indicate a strict user category. Although there are site-wide admin
users, most users will have admin-level functionality in some limited
sense on certain resources. Some users may be admins for one pool, or
one provider only, but on other pools/providers they are not. Any user
that launches something will have admin-level permissions on those
particular instances, etc.
Scott