Diff for /wikisrc/projects/project/atf-sql-backend.mdwn between versions 1.2 and 1.3

version 1.2, 2015/02/19 19:45:45 version 1.3, 2015/03/02 07:39:12
Line 17  duration="3 months" Line 17  duration="3 months"
 description="""  description="""
 We are currently running various regular [tests](http://releng.netbsd.org/test-results.html), both on emulators and real hardware.  We are currently running various regular [tests](http://releng.netbsd.org/test-results.html), both on emulators and real hardware.
 The results are generated in ATF (or maybe sometime later in Kuya) raw XML output format and then transformed via xslt into html.  The results are generated in ATF (or maybe sometime later in Kuya) raw XML output format and then transformed via xslt into html.
 This is good enough to display single test run results, but does not provide any overview or comparison options accross different test runs or architectures.  This is good enough to display single test run results, but does not provide any overview or comparison options across different test runs or architectures.
   
 The target of this project is to provide a simmple 'upload' utility, that takes the xml input and inserts it into a remote PostgresSQL database.  The target of this project is to provide a simple 'upload' utility, that takes the xml input and inserts it into a remote PostgresSQL database.
 Creating a suitable database schema and the xml loader/upload tool is the first half.  Creating a suitable database schema and the xml loader/upload tool is the first half.
   
 Second part is using the collected results to display some nice web pages showing statistics and allowing dedicated queries, comparable  Second part is using the collected results to display some nice web pages showing statistics and allowing dedicated queries, comparable
Line 37  A huge set of ATF xml data will be provi Line 37  A huge set of ATF xml data will be provi
   
 The result is planed to be deployed on TNF servers later, so it is of direct use for the community.  The result is planed to be deployed on TNF servers later, so it is of direct use for the community.
 This deployment is not part of the GSoC timeline.  This deployment is not part of the GSoC timeline.
   
   Note that item (4) above needs proper evaluation before the database schema is created. Kuya already stores test results in a SQLite database, so the extract and upload utility likely will be simple, but the database schema is incompatible and a good migration plan is needed upfront.
   
   During GSoC, this project will ignore deployment issues, which will need broader discussion and maybe changes to the tools - for example the finally deployed upload utility has to be part of the base installation, so may not be able to depend on PostgresSQL libraries. A pkgsrc based solution for milestone (2) is good enough for this project.
 """  """
 ]]  ]]
   

Removed from v.1.2  
changed lines
  Added in v.1.3


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb