On 08/11/2009 09:33 PM, Paul Company wrote: > I'm running cobbler 1.6.6 on RHEL 5.3. > > Three Questions: > > Q1: Is there a way to have the Web UI behavior change according to the > person that logs in? > For example, I'd like it if user "foo" has full access to everything, > but user "bar" to only be able to create systems. > Listing distros, profiles, and repos is ok, but I don't want > bar to have the ability to add or delete distros, profiles or repos. > There is the "authz_ownership" module which is detailed on the Wiki under the security pages, that can restrict what objects people can edit.
At a generic level, there's not a concept for a read-only user group, but that's probably something that could be easily added. As a sidenote, since you sound like you are interested in helping us work on Cobbler Web, new things need to be done on the "master" branch, which targets 2.0 -- that should be out in a month. > Q2: Has anyone customized the "Add System" web page? > I'm not a web programmer but I'd like to simplify/customize > the "Add System" page so it's simpler for our end user. > I'd to add fields like "Location" and have the values entered > show up as --ksmeta values; so if you enter Location: nyc, > that would get processed into --ksmeta="loc=nyc" > Also, things like, if one chooses a profile that isn't a vm profile, > then don't show the VM stuff. Or if power management > is disabled, don't show the power management stuff. etc. > We've had some ideas on this, about making templates for self-service views in Cobbler. This could be done as a seperate Django app in the cobbler Django project, and I would like to see something like this very much. It really warrants a new thread on cobbler-devel list there, would you like to start one? I have a fair amount of ideas from our own IT guys -- things that we didn't quite implement yet -- but I think that would be exceptionally powerful. Some of those also dovetail into puppet recipe configuration through a similar interface, which I'm not sure if you are interested in. > Q3: Should I wait for cobbler 2.0 which uses Django? > Or should I plow ahead with the current mod_python stuff? > Aha, I got ahead of myself. Glad you're aware of that :) Yes, we need to do things on 2.0, since it will be out soon, and porting anything done to the old codebase will be a lot of extra effort. > Any tips/information/examples on developing mod_python or Django web > pages would be a big help. > Do a checkout of git's master branch and do a "make webtest" to get started. Code lives in the "web" directory and should be fairly self explanatory, but I'd be more than happy to answer any specific questions. Hoping on #cobbler and #cobbler-devel on irc.freenode.net is also a great idea. > Thanks, > > Paul > _______________________________________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/mailman/listinfo/cobbler > _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
