Hi, I&#39;ve been playing around with this &quot;lava&quot; thing a bit :)<br>From the perspective of the QA team, I&#39;m currently interested in a very specific use case, but it&#39;s one that I think has some common things with what others want to do:<br>

We have test results for various {ubuntu, android} images. I&#39;d like to see a current snapshot of the results on those images.  I&#39;d also like to see the history for previous results on the same type of image.  This way, as we near release time, if we look at trying to figure out which build is likely to be the best one to use for release candidate testing, we can glance at the results and see where most of our automated tests passed.<br>

<br>So just looking at android as an example, because we already store data there about which image we are testing, which build number, which url.  It&#39;s pretty simple to pull all bundles in a stream.  It&#39;s also not too bad to look at a test_run in a bundle and get the fact that it has a certain attribute.  It&#39;s not so easy to say &quot;show me all the bundles that have this attribute&quot;.  Am I missing something?<br>

<br>I think I brought this up before, but I ran across a project (heck if I can find it now) that had a python library providing an API to make it convenient for finding your test data.  This is what the ORM *should* be providing, I know, but it&#39;s not always the most convenient for us as we&#39;ve all struggled with this in the past.<br>

<br>This is nothing new, just wanted to present another use case that highlights something we&#39;re trying to do, but doesn&#39;t seem to be too easy at the moment, and looking for suggestions about how to proceed.<br><br>

Thanks,<br>Paul Larson<br>