From: "Nikolai Kondrashov" <Nikolai.Kondrashov@redhat.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: kernelci@groups.io,
"Guillaume Tucker" <guillaume.tucker@collabora.com>,
"Philip Li" <philip.li@intel.com>,
kernelci-members@groups.io, nkondras@redhat.com,
"Don Zickus" <dzickus@redhat.com>,
syzkaller <syzkaller@googlegroups.com>,
"Iñaki Malerba" <imalerba@redhat.com>
Subject: Re: [kernelci-members] Working with the KernelCI project
Date: Mon, 28 Sep 2020 16:15:21 +0300 [thread overview]
Message-ID: <d9919812-9763-9c02-3e5d-978fac8fe1f7@redhat.com> (raw)
In-Reply-To: <CACT4Y+a5spdA8TZNeaXFYj4QEw_=howfhu9YGsNm3rC8XPAJnA@mail.gmail.com>
Hi Dmitry,
On 9/28/20 3:48 PM, Dmitry Vyukov wrote:
> The examples are helpful. I think this should be doable. The ability
> to send everything in a single request is handy, and since we don't
> send bulky data (only links), should not cause any issues.
Awesome!
> I need an API key, right? How are they distributed? Could you send me
> one to my email privately?
Yep, just sent it.
> However, we don't use any Python and use of kcidb-submit will be
> problematic as the app is a Go App Engine app.
Do you mean you can't run executables, or that having the Python stack in
there as well is not possible/burdensome? Just curious.
> I looked what's the actual protocol and got to here:
> https://github.com/kernelci/kcidb/blob/master/kcidb/mq/__init__.py#L69
> and this "client" seems to come from google.cloud.pubsub.
>
> Go has https://pkg.go.dev/cloud.google.com/go/pubsub package as well,
> it would be much more practical for syzbot to use that directly. But
> what exactly is the protocol? I assume it's that JSON, but is it
> wrapped into some other layers? What's the topic name to publish? Is
> there description/example on this level?
There's no documentation available for this level, yet, just the code.
However, yes, it's just JSON submitted to a PubSub topic, currently, and the
schema is exactly as output by "kcidb-schema".
Please validate JSON fully before submitting to the PubSub topic
("kcidb-validate" could help you start). We don't have error reporting to
submitters from the server side yet, we'll have to read the logs to find out
what happened, if it breaks :)
I sent you the project/topic names in the message with the credentials.
Oh, and we would definitely appreciate a contribution of the Go submission
module, if you make one :)
> Also, how can I test things? Is there a test instance? Or if I push
> something, can I observe it on the KernelCI dashboard or something?
Yes, there's a "playground" instance, details are in the message with the
credentials. You can see the results on the "playground" dashboard, and query
them from the "playground" database with "kcidb-query".
> What would be the procedure for deploying it on the syzbot side?
Do you mean "deploying the dashboard"?
Excited to have you join the effort!
Nick
On 9/28/20 3:48 PM, Dmitry Vyukov wrote:
> On Fri, Aug 21, 2020 at 12:10 PM Nikolai Kondrashov
> <Nikolai.Kondrashov@redhat.com> wrote:
>>
>> Hi Dmitry,
>>
>> On 8/5/20 9:44 PM, Dmitry Vyukov wrote:
>> > On Mon, Aug 3, 2020 at 11:25 AM Nikolai Kondrashov
>> >> Did you have time to take a look at my mock-up? It probably looks like too
>> >> much text, but please don't hesitate to reach me with any questions or
>> >> suggestions you have as you look through it, if you haven't already.
>> >>
>> >> Please note that you don't have to start with sending all this data. In fact,
>> >> only a few structural fields are required and we can start with the absolute
>> >> minimum. The mock-up is showing what you *could* already send, but you don't
>> >> have to go that far.
>> >>
>> >> I'd like to schedule a hacking session at Plumbers where we go and try to get
>> >> some data out of participants' systems and into KCIDB. Would you be interested
>> >> to attend, perhaps?
>> >
>> > Hi Nick,
>> >
>> > I've seen your reply and seen that you provided an example of how to
>> > fill in the data. I was starred in my inbox, but I did not have time
>> > to look at the details yet (we have somewhat crazy intern season). I
>> > still want to do this.
>>
>> Glad to hear that, and I understand about the time.
>>
>> > I am not sure how a remote virtual hacking session is different from
>> > just doing this normally and some email exchange :)
>>
>> I would say the low response latency helps move faster :)
>>
>> We could have a video call in background and/or share a screen or a tmate
>> session, as we try to make things work. Even just having someone available in
>> an IRC chat for quick responses helps, I'd say.
>>
>> Everyone has their own preferences, of course, I'm just offering to be there
>> and discuss things and maybe work on something :)
>>
>> As I just wrote to Philip, I've finally published the schema introduction
>> article:
>>
>> https://foundation.kernelci.org/blog/2020/08/21/introducing-common-reporting/
>>
>> Here's our talk, same MC as yours, but later:
>>
>> https://linuxplumbersconf.org/event/7/contributions/730/
>>
>> and the BoF session next day:
>>
>> https://linuxplumbersconf.org/event/7/contributions/731/
>>
>> Will be glad to meet you there, even though we won't be able to do
>> much in the 45 minutes we were allocated.
>>
>> So please also drop by our "hallway chat", whenever you have time:
>>
>> https://chat.2020.linuxplumbersconf.org/channel/kcidb
>>
>> I'll be there every day of the conference, during Europe's working hours.
>
>
> Hi Nikolai,
>
> The examples are helpful. I think this should be doable. The ability
> to send everything in a single request is handy, and since we don't
> send bulky data (only links), should not cause any issues.
>
> I need an API key, right? How are they distributed? Could you send me
> one to my email privately?
>
> However, we don't use any Python and use of kcidb-submit will be
> problematic as the app is a Go App Engine app.
> I looked what's the actual protocol and got to here:
> https://github.com/kernelci/kcidb/blob/master/kcidb/mq/__init__.py#L69
> and this "client" seems to come from google.cloud.pubsub.
>
> Go has https://pkg.go.dev/cloud.google.com/go/pubsub package as well,
> it would be much more practical for syzbot to use that directly. But
> what exactly is the protocol? I assume it's that JSON, but is it
> wrapped into some other layers? What's the topic name to publish? Is
> there description/example on this level?
>
> Also, how can I test things? Is there a test instance? Or if I push
> something, can I observe it on the KernelCI dashboard or something?
> What would be the procedure for deploying it on the syzbot side?
>
> Thanks
>
next prev parent reply other threads:[~2020-09-28 13:15 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200707222342.scrz75265etaqlmd@redhat.com>
[not found] ` <42d15463-e4ee-4c0b-c63f-dce7acb05e35@collabora.com>
[not found] ` <CACT4Y+ZLoBLFWRM+RcKZJyR2Hh5az9W8_329ShM9JuSg6V4uVw@mail.gmail.com>
[not found] ` <bbeeb467-1571-5404-7408-9b112d64e928@redhat.com>
[not found] ` <CACT4Y+a1t-9sT7xz7d=Wmesnn_QoUqfipmoZXBu40_B+GQy=nQ@mail.gmail.com>
2020-07-17 12:22 ` [kernelci-members] Working with the KernelCI project Nikolai Kondrashov
2020-08-03 9:25 ` Nikolai Kondrashov
2020-08-05 18:44 ` Dmitry Vyukov
2020-08-21 10:10 ` Nikolai Kondrashov
2020-09-28 12:48 ` Dmitry Vyukov
2020-09-28 13:15 ` Nikolai Kondrashov [this message]
2020-09-28 15:23 ` Dmitry Vyukov
2020-09-28 16:09 ` Dmitry Vyukov
2020-09-28 16:24 ` Dmitry Vyukov
2020-09-28 17:16 ` Nikolai Kondrashov
2020-09-29 7:52 ` Dmitry Vyukov
2020-09-29 17:13 ` Nikolai Kondrashov
2020-09-30 7:07 ` Dmitry Vyukov
2020-10-01 8:30 ` Nikolai Kondrashov
2020-10-01 8:43 ` Dmitry Vyukov
2020-10-01 10:51 ` Nikolai Kondrashov
2020-09-30 7:21 ` Dmitry Vyukov
2020-10-01 8:53 ` Nikolai Kondrashov
2020-09-30 7:31 ` Dmitry Vyukov
2020-10-01 8:57 ` Nikolai Kondrashov
[not found] ` <16397F50C12D08DD.21243@groups.io>
2020-09-30 16:07 ` Dmitry Vyukov
2020-10-01 10:48 ` Nikolai Kondrashov
2020-10-01 13:32 ` Nikolai Kondrashov
2020-10-01 14:48 ` Dmitry Vyukov
2020-10-01 15:49 ` Nikolai Kondrashov
2020-10-01 15:51 ` Nikolai Kondrashov
2020-10-01 16:00 ` Dmitry Vyukov
2020-10-01 16:34 ` Nikolai Kondrashov
2020-10-01 17:02 ` Dmitry Vyukov
2020-10-02 7:52 ` Dmitry Vyukov
2020-10-02 8:12 ` Nikolai Kondrashov
2020-10-02 9:02 ` Dmitry Vyukov
2020-10-02 9:08 ` Nikolai Kondrashov
2020-10-02 10:39 ` Nikolai Kondrashov
2020-10-02 13:40 ` Dmitry Vyukov
2020-10-02 8:12 ` Nikolai Kondrashov
2020-10-01 15:01 ` Dmitry Vyukov
2020-10-01 15:11 ` Nikolai Kondrashov
2020-10-01 15:36 ` Dmitry Vyukov
2020-10-01 15:40 ` Dmitry Vyukov
2020-10-01 15:58 ` Nikolai Kondrashov
2020-10-01 15:55 ` Nikolai Kondrashov
2020-10-01 16:03 ` Dmitry Vyukov
2020-10-01 16:28 ` Nikolai Kondrashov
2020-09-28 16:50 ` Nikolai Kondrashov
2020-09-28 16:49 ` Nikolai Kondrashov
2020-09-28 17:09 ` Dmitry Vyukov
[not found] ` <20200709110029.GB27682@intel.com>
[not found] ` <69138572-7241-1636-8018-34cd380ec540@redhat.com>
[not found] ` <20200713001929.GA1812@intel.com>
2020-07-22 12:42 ` Nikolai Kondrashov
2020-08-03 9:11 ` Nikolai Kondrashov
2020-08-04 0:13 ` Philip Li
2020-08-09 2:25 ` Philip Li
2020-08-10 8:50 ` Nikolai Kondrashov
2020-08-21 9:50 ` Nikolai Kondrashov
2020-08-21 10:19 ` Nikolai Kondrashov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d9919812-9763-9c02-3e5d-978fac8fe1f7@redhat.com \
--to=nikolai.kondrashov@redhat.com \
--cc=dvyukov@google.com \
--cc=dzickus@redhat.com \
--cc=guillaume.tucker@collabora.com \
--cc=imalerba@redhat.com \
--cc=kernelci-members@groups.io \
--cc=kernelci@groups.io \
--cc=nkondras@redhat.com \
--cc=philip.li@intel.com \
--cc=syzkaller@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox