At present, we are using the wiki to organize community laptop and server hardware testing (LaptopTesting and ServerTesting, respectively). We want to move away from the wiki and to a specialized web catalog that includes information both about Ubuntu-certified hardware, and about community testing.


Use cases


The hardware catalog will replace the current sets of hardware testing wiki pages.


The catalog provides two clearly separate databases: the certified hardware database, and the community-tested hardware database.

For servers, after running the on-CD burn-in test suite, the suite UI asks for a short server hardware ID (e.g. "Proliant DL380G3"), the user's Launchpad username and password (authenticated via Launchpad AuthServer), and posts the burn-in results via HTTPS to that account's "pending" queue in the catalog.

When logged into the catalog, a user can access test runs in his pending queue and supply complete details for the server, such as:

When satisfied, the user can post the complete server profile to the live catalog, which removes it from his pending queue. One week after posting a profile to the live catalog, the user loses the ability to make changes to it.

Additionally, pending profiles can be associated as "alternates" to existing profiles, to allow for different experiences with the same hardware by multiple users. Alternates are listed on every profile along with a summary, e.g. "17 succeeded installations, 3 failed".

A "create new profile" function exists for users performing no burn-in tests, only installation tests.

Remote compatibility test

It would be great to be able to connect to the website with a PC which could run (javascript or whatever sorry I am not sure about the details) an application collecting all the relevant information to see what will run or not with the current Ubuntu. In case of Laptops for example this could just look up for the model itself and then have an answer using the database, but for more "generic" PC it could check each component to give an answer for each of them (well at least with some degree of confidence). Just an idea...


The catalog will be a Python web application.


We will have the catalog ready for public use no later than Dapper+1.


HardwareTestingCatalog (last edited 2008-08-06 16:40:57 by localhost)