Ray Chen wrote:
Here are some questions when I read beaker docs or source codes.
1. how to use medusa-lab-control, and how does it work with
seems that the medusa system is on top of cobbler system if we can get
the beaker architecture overview. Considering test regression, we often
need to install/reinstall or setup machine environment. So, is the
medusa only responsible for configure the testing machine (I means OS)?
medusa-lab-controller is just some kickstarts and snippets that go on
top of cobbler.
Cobbler takes care of provisioning and power cycling machines.
Medusa-server talks to the lab controller via xmlrpc (direct to
cobbler). The server keeps track of who has access to what systems and
what systems are in use. Also keeps track of what distros a system is
capable of installing and what options are need for each distro.
2. what is this script used to?
I guess it's the interface between beaker-Schedule and beaker-rhts. In
that file, there are such line:
session = xmlrpclib.Server("http://%s:%
s/cgi-bin/rhts/scheduler_xmlrpc.cgi" % (server, port))
Here, I can't cheduler_xmlrpc.cgi in source code. what's
scheduler_xmlrpc.cgi used for?
This is used internally. I'll see about removing that from the code.
What is missing is the open scheduler to make this run tests. The code
under Logan is partially complete.
3.how to implement rhts library as a STAF service?
as we discussed before, we should make rhts library as STAF service. Is
there any requirement about this, such as use case or command line
I have not had time to look into STAF more yet. I have some time set
aside in a week or so to do just that.
Beaker-devel mailing list