Re: Kcidb access request

Gustavo Padovan <[email protected]>
Newsgroups dev.linux.lists.kernelci
Message-ID <[email protected]>

---- On Thu, 08 Aug 2024 14:56:12 -0300 Nikolai Kondrashov  wrote ---

 > Hi Bjorn, 
 >  
 > On 8/7/24 6:49 PM, Bjorn Andersson wrote: 
 > > I'm using api.kernelci.org for reporting test results from my kernelci 
 > > lab, as well as scraping test reports for Qualcomm boards for local 
 > > aggregation and presentation. 
 > > 
 > > As part of the transition to the new KernelCI APIs, I would like access 
 > > to KCIDB. 
 > > 
 > > 
 > > My (custom) test reporting tool today uses the LAVA callback interface, 
 > > and thereby follows this schema for the report, groups and cases. I can 
 > > continue to follow this schema, or change the schema as you prefer. 
 > > Please let me know. 
 >  
 > Sorry for the delay with the answer! 
 >  
 > Sure, you can get the access to the KCIDB database. 
 >  
 > However, we don't have APIs, just the direct access to PostgreSQL, which keeps 
 > six months of data. See the attached (abbreviated) schema dump. It largely 
 > mirrors the JSON I/O schema, which you can see here: 
 >  
 > https://github.com/kernelci/kcidb-io/blob/main/kcidb_io/schema/v04_03.py 
 >  
 > Here's some more human-oriented introductory docs: 
 >  
 > https://kernelci.org/docs/kcidb/submitter_guide/ 

This link is from before our recent domain switch...so it gives a 404.

See this content at https://docs.kernelci.org/kcidb/submitter_guide/

 >  
 > Note, that at the moment we have no way to query for "Qualcomm boards", but we 
 > have a schema change proposal being discussed to address that. 
 >  
 > Also, when fetching your data you will need to be considerate of traffic and load. 
 >  
 > You can explore the data on the dashboard (to be improved soon): 
 > https://kcidb.kernelci.org/ 
 >  
 > If none of the above stops you, I can give you credentials and permissions for 
 > querying. 
 >  
 > Nick
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.