Here's my attempt to summarize the project ideas offered recently,
because I feel there are enough that some good ones might get lost:
If I left any out, please add them in!!
There are 3 general projects:
====================================================
I) central config-db
II) package system
III) gui admin program
I can be done alone, even with the current lrcfg and lrpkg.
II is dependant on I being done.
III is dependant on II.
Can we concur on the above? I think it's important to get
our foundation in order. I think the dependancies are more
logical than hard and fast rules. I don't want to have to
rewrite a gui admin program if a new package system comes
out a month later.
MY SUMMARY OF THE IDEAS SO FAR
=============================================================
CONFIG-DB PROPOSALS
1. flat-db
2. api-flat-db
3. api-xml-db
4. api-binary-db
5. template-api-xml-db
PACKAGE SYSTEM PROPOSALS
[all are .tgz and FAT based ==> 8.3 filenames]
1. extend apkg to use one of the db ideas.
2. rewrite the package system from scratch to use one of the db ideas.
3. make packages automatically restart via trigger, when necessary
4. make remotely loadable packages via http, ftp, tftp, scp, etc.
5. make package system load all packages it finds, no more list.
ADMIN PROGRAM PROPOSALS
[all pre-config ideas utilize a master cdrom of utils/modules/packages/LEAF variants]
[all post-config idea might use sshd on LEAF to facilitate scp and an ssh tunnel]
1. pre-config done on seperate OS using local Java app.
2. pre-config done on seperate OS using local Python app.
3. pre-config done on seperate OS using local Perl/www/cgi apps.
4. pre-config done on seperate OS via server based www/cgi apps.
5. pre-config done on LEAF box using Red-Hat dynamic hardware inspection app.
5. pre-config be upgrade capable (can clone a running LEAF)
5. post-config done on separate OS via LEAF based perl/weblet/cgi apps.
6. post-config done on separate OS via local based perl/www/cgi apps.
7. post-config done on separate OS via local Java app.
8. post-config done on separate OS via local Python app.
9. post-config done on LEAF using terminal based ascii gui, like Oxygen.
10. Make pre-config and post-config into one app.
Well I'd appreciate it if you'd add to the laundry
list those ideas that I failed to include, not out
of malice, but from lack of understanding their scope.
Best,
Matthew
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
