Hello autotesters,
I've published a simple proof of concept of an standalone library to
access an autotest RPC server at:
https://github.com/clebergnu/autotest-rpc-client
The idea is to have a set of library modules that will give easy access
to all data and functionality in an autotest server, through its RPC
interface.
Currently the two obvious ways to access an autotest server is via the
following two client apps:
* cli/autotest-rpc-client (AKA cli/atest)
* http://<server>/afe
But we feel that these two tools do fit every user or usage scenario.
So, we want to empower users, making the process to write scripts and
tools that can access all of autotest functionality.
I believe that the tasks required to accomplish this are roughly:
* Discuss the architectural changes to autotest main tree
- Should the rpc client code really live on a separate repo?
- Should the main autotest link to it as a submodule?
- Should the apps (such as the current cli/autotest-rpc-client) live
on yet another repo?
* Define the module granularity, general API look and feel, etc
* Write the complete set of API modules
* Rewrite the current cli/autotest-rpc-client tool to use the API
Please provide your thoughts on this!
Thanks,
CR.
_______________________________________________
Autotest mailing list
Autotest@test.kernel.org
http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
