Hi guys,
Here are a few details we have agreed on in connection with development
of openussd.
Development Will Be In Modules
From the architecture diagram:
We can have different
teams/individuals tackle the following:
1. Pilot module
- Process creator
- config loader
- Process monitor to report to masteragent
- logging to logs/pilot.log
2a. masteragent module
- config loader
- request Listener/response pusher
- route config reader/loader
- infobase(an xml-rpc server which CLI and WebUI connect to for
information on the overall system)
- Log handler for all services. Logs are separated into
(cli.log,masteragent.log,pilot.log,routes.log,webui.log,infobase.log)
- Gateway Routes module
2b. infobase module
- A central module/db stored on memcache which offers live statuses and
all information in Pilot and Masteragent.
CLI is connected directly to infobase.
WebUI will access information from infobase over and xml-rpc server.
3. CLI module
- All
commands...getrunningconfig,getroutes,getconnectors,getnumrequests..etc.)
(I will send the CLI commands later on with exaplanation to what each
does.someone can code up the rest)
4. WebUI module
- Django UI to load info from infobase
-should include all the web app functionality(Login..etc.).
NB://
1. Config loader is being coded by Leonard.
2. Masteragent is being coded by Isaac.
So there is more to coding to be done...then documentation as usual :D
@Leonard- If I missed anything please add up.
I will be sending the link to the git repository so everyone can clone
the development directory structure.
Kindly ask questions. We love to have them and answer them.
BR
Isaac
--
Fedora Linux Security Labs
http://fedoraproject.org/wiki/Linuxthomass
IRC Nick:d3vnull
blog:http://d3vnulls.blogspot.com
Key ID: 0xAD9CB171
Key fingerprint: D475 DF35 3EC6 A7A8 0796 13DB ECA3 46B8 AD9C B171