Scott Henson wrote:
seth vidal wrote:
On Tue, 2008-01-15 at 19:39 -0500, Michael DeHaan wrote:
Michael DeHaan wrote:
So, continuing from FudCON's hackfest ideas, I think these are the
biggies in terms of "func core" kind of stuff to get done.
Thoughts? I've added the missing ones to the ideas page. There
are a lot of other expansion/module ideas, but this is probably the
(larger) stuff that is perhaps missing. However some of it is
pretty much optional too.
* minion-to-minion + ACLs (and of course docs on how to do this)
.... a really neat feature
* multiple-overlords/cert-sharing ... seemed to be requested a lot
at talk
* overlord-delegation (for network reasons, but also maybe
efficiency.... there's a government app that basically did a tree
like fan-out for this).
* figuring out how to loosen up the permissions of caller (making
sure things are accessible by TurboGears if it opens up a Client()
object). Currently it just needs the /etc/pki/func and
/var/lib/func stuff. This is probably not too much of a problem
but worth talking about.
* Groups? We had talked about doing this in the WebUI and CLI
seperately but we could perhaps actually make it part of the Func
client API seperately and save a local DB so that could be
shared? Thoughts?
By DB, I mean of course something like bsddb or even a config file,
not an actual DB :)
for the love of all that is good and holy not bsddb.
-sv
I would vote for a python ConfigParser config file or use SQLAlchemy
to put it
into a sqlite db by default. It would allow the crazies to put it in
a real
db if they felt the need.
Groups would be small, config parser would fly and would still be human
editable. People really like things that are human editable.
_______________________________________________
Func-list mailing list
Func-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/func-list
