Re: Quick question on dynamic loading of authn_spacewalk
Partha Aji wrote:
I am a bit puzzled on why authn_spacewalk is part of the cobbler
upstream. Shouldn't it be part of spacewalk project upstream ?
In a multi-server setup, we would want this installed on the cobbler
machine (there may likely be more cobbler installs than Spacewalk
servers at a given site), not the Spacewalk machine, and it's easier
than maintaining a "spacewalk-cobbler" RPM for one 10-or-so line python
file.
Is the problem just that there is no way to tell cobbler to
dynamically load modules outside its realm ??
You can do this today. If another RPM (such as Spacewalk) wanted to
install a Cobbler module, all it has to do is install the .py in the
correct path and then reference that in the config file.
I am just concerned that every time we find a bug in
authn_spacewalk.py its just going to take a lot of time to submit to
cobbler and have them review it.
I am pretty sure we can turn out a Cobbler release as quickly as
needed. Cobbler is a pretty simple app by comparison, and we are also
talking about a very small module that should not be changing
frequently. Just send a patch to the list, and cross-post it to
Spacewalk-list if necessary.
This also requires cobbler reviewer to be aware of how authentication
is done on spacewalk and looks unnecessary to me.. Ideally I 'd like
to be as follows. In modules.conf
It's a pretty simple module, I think folks
can understand it.
--Michael