Message-ID: <a8518d24-8b02-39f7-d4e3-82c28715191d@redhat.com>
Date:   Fri, 26 Feb 2021 13:21:57 +0200
From:   Nikolai Kondrashov <Nikolai.Kondrashov@...hat.com>
To:     Hanjun Guo <guohanjun@...wei.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Scott Branden <scott.branden@...adcom.com>
Cc:     Huxinwei <huxinwei@...wei.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Yanjin <yanjin.yan@...wei.com>,
        BCM Kernel Feedback <bcm-kernel-feedback-list@...adcom.com>,
        Zhaohongjiang <zhaohongjiang@...wei.com>,
        "Zhangdianfang (Dianfang, OS Lab)" <zhangdianfang@...wei.com>,
        PEIXIN HOU <PEIXIN.HOU@...wei.com>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        kernelci@...ups.io, Wei Yongjun <weiyongjun1@...wei.com>,
        Lijinyue <lijinyue@...wei.com>
Subject: Re: 5.10 LTS Kernel: 2 or 6 years?

Hi Hanjun,

On 2/26/21 10:03 AM, Hanjun Guo wrote:
 > On 2021/2/19 22:45, Nikolai Kondrashov wrote:
 >> Would you be interested in working with the Linux Foundation KernelCI project
 >> on submitting your build and test results to the common database - KCIDB?
 >
 > Yes, we are willing to sent the test results to KCIDB.

Wonderful!

 > For now, all the tests are inside the company, which blocks us to
 > directly sent the test results out of the test machine due to the
 > security policy, it takes us sometime to discuss how to send out
 > the test results, and we may need do the test in a public cloud.

I understand. We faced the same dilemma at Red Hat with the CKI project, where
I'm employed. In the end we just decided to publish the logs from the test
lab (most sensitive part, I suppose) as they are, but then Red Hat is already
a very open company.

Here's an example of all logs we publish for a revision:

     https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/02/22/624489

And here's that revision in KCIDB:

     https://staging.kernelci.org:3000/d/revision/revision?orgId=1&var-dataset=kernelci04&var-id=093ae67c90a629599a0cb2300c5686ec7d8bbdd0

Take your time, there is a range of solutions to choose from, starting from
isolating your test machines/boards, to running the test in the public cloud
as you mention. Although the latter lacks the benefit of testing your own
hardware, of course.

Please also note that we require the tested kernel's code to be publicly
available to accept results.

 >> We are working on aggregating results from various testing systems so we can
 >> provide a dashboard, and a single, aggregated e-mail report to subscribed
 >> maintainers and developers.
 >>
 >> We have a prototype dashboard at https://staging.kernelci.org:3000/ and are
 >> working hard on making the e-mail reports good enough to start reaching out to
 >> maintainers.
 >>
 >> We already have ARM, Google Syzbot, Gentoo GKernelCI, Red Hat CKI, and, of
 >> course, KernelCI native tests sending data to the database. Linaro Tuxsuite is
 >> starting sending today. We could use your data, and of course any development
 >> help you could spare :)
 >
 > How can we connect to the KCIDB? Can we send the test data out by email
 > first?

The simplest way would be using our "kcidb-submit" command-line tool.

Here's a minimal example of sending an empty report:

     echo '{"version":{"major":3,"minor":0}}' |
             kcidb-submit -p kernelci-production -t kernelci_new

Another way could be using our Python 3 library, which is a little more
involved. Here's an example sending the same empty report in Python:

     import kcidb
     client = kcidb.Client(project_id="kernelci-production",
                           topic_name="kernelci_new")
     client.submit({"version":{"major":3,"minor":0}})

Finally, you can send (validated) data using the Google Cloud Pub/Sub service
directly, using the library in one of the supported languages:

     https://cloud.google.com/pubsub/docs/tutorials

The latter would be the least stable option (change-wise), but something e.g.
Google Syzbot is already using.

See more details in our Submission HOWTO:

     https://github.com/kernelci/kcidb/blob/main/SUBMISSION_HOWTO.md

Although email submissions are theoretically possible (with due
authentication, setup, etc.), they're not currently supported, and we would
not put them at the top of our (rather large) priority list. Topmost item
being getting the data we already have to developers.

Would be excited to have you on board!
Nick

On 2/26/21 10:03 AM, Hanjun Guo wrote:
 > Hi Nick,
 >
 > Sorry for taking so long to reply you, we had discussions on how to
 > corporate with KCIDB, please see my comments inline.
 >
 > On 2021/2/19 22:45, Nikolai Kondrashov wrote:
 >> Hi Hanjun,
 >>
 >> On 2/19/21 10:54 AM, Hanjun Guo wrote:
 >>  > In specific, we will start from the testing work, using HULK robot
 >>  > (reports lots of bugs to mainline kernel) testing framework to test
 >>  > compile, reboot, functional testing, and will extend to basic
 >>  > performance regression testing in the future.
 >>
 >> I heard about Huawei ramping up kernel testing from someone at FOSDEM
 >> 2019. I wonder if it was you :) Nice to see your progress and the company
 >> stepping up to help with testing!
 >
 > I Cced Yongjun and Jinyue, they are the key persons :)
 >
 >>
 >> Would you be interested in working with the Linux Foundation KernelCI project
 >> on submitting your build and test results to the common database - KCIDB?
 >
 > Yes, we are willing to sent the test results to KCIDB.
 >
 > For now, all the tests are inside the company, which blocks us to
 > directly sent the test results out of the test machine due to the
 > security policy, it takes us sometime to discuss how to send out
 > the test results, and we may need do the test in a public cloud.
 >
 >>
 >> We are working on aggregating results from various testing systems so we can
 >> provide a dashboard, and a single, aggregated e-mail report to subscribed
 >> maintainers and developers.
 >>
 >> We have a prototype dashboard at https://staging.kernelci.org:3000/ and are
 >> working hard on making the e-mail reports good enough to start reaching out to
 >> maintainers.
 >>
 >> We already have ARM, Google Syzbot, Gentoo GKernelCI, Red Hat CKI, and, of
 >> course, KernelCI native tests sending data to the database. Linaro Tuxsuite is
 >> starting sending today. We could use your data, and of course any development
 >> help you could spare :)
 >
 > How can we connect to the KCIDB? Can we send the test data out by email
 > first?
 >
 >>
 >> I wish I could show you my today's KCIDB presentation at DevConf.cz, but the
 >> recording is not out yet. Meanwhile you can take a look at our presentation at
 >> last year's Linux Plumbers: https://youtu.be/y9Glc90WUN0?t=10739
 >>
 >> Or see our intro in an older blog post:
 >> https://foundation.kernelci.org/blog/2020/08/21/introducing-common-reporting/
 >>
 >> Anyone wishing to contribute to KCIDB gets credentials and permissions to
 >> submit to our "playground" setup where they can send their data, see it in a
 >> dashboard, experiment without worrying about breaking anything, and decide if
 >> they like it or n >
 >> If you're interested, take a look at our Submission HOWTO:
 >> https://github.com/kernelci/kcidb/blob/v8/SUBMISSION_HOWTO.md
 >> and send an email to kernelci@...ups.io (CC'd), or come over to the #kernelci
 >> channel on freenode.net!
 >
 > Thanks!
 > Hanjun

Powered by blists - more mailing lists