On Apr 22, 2011, at 9:43 AM, Alex Dean wrote: > I'd like to get some feedback on how we should configure gweb's default > access permissions. > > #1. "$conf['auth_system']=false;" will disable authorization, so no logins > are required and the system behaves like the current ganglia web frontend. > In this case, should editing of views be allowed or denied? Do we want > disabling auth to mean 'read-only access' or 'anything goes'?
I think it should be read only at that point. I envision groups of users with competing ideas of what machines are important putting the web interface through a tug of war. If administrators want to risk that, it should be something they have to consciously enable. > #3. Should the default be to ship with authorization enabled or disabled? > > My preference is that 'read-only & no authorization required' is the default > configuration. That's my preference too. ------------------------------------------------------------------------------ Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails _______________________________________________ Ganglia-general mailing list Ganglia-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-general
