[gentoo-kernel] Gentoo Kernel meeting

[gentoo-kernel] Gentoo Kernel meeting

[Alice Ferrazzi]

Hello everyone,

I would like to start the first Gentoo kernel meeting.
Please choose the time of the meeting [1]
If the time is not compatible we can also just discuss it by mail.

Please send any new agenda items as new threads to the gentoo-kernel list.

The current agenda is as follows.
- Gentoo kernel ci
    - Use Lava qemu for testing the kernel
    - Add kselftest
    - Start stabilizing with Gentoo kernel CI
    - Add ck-sources to the qemu test
- Stabilization
    - Automatize the stabilization process
    - keep up with upstream or use any other stabilization system
        current stabilization system is defined here [2]
        and here is the process to stabilize the kernel [3]
        As now we are working to automatize the process.

Please add any other topics, is also possible to discuss directly in
this thread.

[1] https://doodle.com/poll/6giztg2vuw8wz6kf
[2] https://wiki.gentoo.org/wiki/Project:Kernel#Kernel_stabilization
[3] https://wiki.gentoo.org/wiki/Package_testing#Kernel



-- 
Thanks,
Alice Ferrazzi

Gentoo Kernel Project Leader
Gentoo Foundation Vice-Secretary
Gentoo Google Summer of Code Administrator
Mail: Alice Ferrazzi <alicef@gentoo.org>
PGP: 2E4E 0856 461C 0585 1336 F496 5621 A6B2 8638 781A

Re: [gentoo-kernel] Gentoo Kernel meeting

[M. J. Everitt]

[-- Attachment #1.1: Type: text/plain, Size: 2259 bytes --]

On 05/07/18 06:16, Alice Ferrazzi wrote:
> Hello everyone,
>
> I would like to start the first Gentoo kernel meeting.
> Please choose the time of the meeting [1]
> If the time is not compatible we can also just discuss it by mail.
>
> Please send any new agenda items as new threads to the gentoo-kernel list.
>
> The current agenda is as follows.
> - Gentoo kernel ci
>     - Use Lava qemu for testing the kernel
>     - Add kselftest
>     - Start stabilizing with Gentoo kernel CI
>     - Add ck-sources to the qemu test
> - Stabilization
>     - Automatize the stabilization process
>     - keep up with upstream or use any other stabilization system
>         current stabilization system is defined here [2]
>         and here is the process to stabilize the kernel [3]
>         As now we are working to automatize the process.
>
> Please add any other topics, is also possible to discuss directly in
> this thread.
>
> [1] https://doodle.com/poll/6giztg2vuw8wz6kf
> [2] https://wiki.gentoo.org/wiki/Project:Kernel#Kernel_stabilization
> [3] https://wiki.gentoo.org/wiki/Package_testing#Kernel
>
I'll add my general availability in a separate thread, as well as
confirm via the Doodle - as updating nearly 200 slots is quite a slow
process!!

I'd like to discuss the possibility of harmonising the bumping and
stabilisation process across the currently maintained source packages,
so that, in principle, whilst they may not be fully supported via
Security Team (we already have disclaimers for this), users choosing to
opt for, eg. ck-sources, would know that because 90% of the code-base
has been 'approved' via gentoo-sources (upstream + gentoo patches) that
any discrepancy due to failure could be quickly narrowed down to the
patchset, and the relevant maintainer can choose to pursue with their
specific upstream. The extent to which this is feasible can be debated,
but if we can establish a basic procedure that is, eg. automated,
perhaps individual maintainers will want to 'pitch in' if the effort
required is minimal enough.
The objective would be to create a obvious 'choice' of "known-good"ish
kernels that any user could choose from, whilst preserving maintainer
workflow separation, etc.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: [gentoo-kernel] Gentoo Kernel meeting

[Alice Ferrazzi]

[-- Attachment #1: Type: text/plain, Size: 2743 bytes --]

Sent from my phone. Please excuse my brevity.

On Thu, 5 Jul 2018, 19:51 M. J. Everitt, <m.j.everitt@iee.org> wrote:

> On 05/07/18 06:16, Alice Ferrazzi wrote:
> > Hello everyone,
> >
> > I would like to start the first Gentoo kernel meeting.
> > Please choose the time of the meeting [1]
> > If the time is not compatible we can also just discuss it by mail.
> >
> > Please send any new agenda items as new threads to the gentoo-kernel
> list.
> >
> > The current agenda is as follows.
> > - Gentoo kernel ci
> >     - Use Lava qemu for testing the kernel
> >     - Add kselftest
> >     - Start stabilizing with Gentoo kernel CI
> >     - Add ck-sources to the qemu test
> > - Stabilization
> >     - Automatize the stabilization process
> >     - keep up with upstream or use any other stabilization system
> >         current stabilization system is defined here [2]
> >         and here is the process to stabilize the kernel [3]
> >         As now we are working to automatize the process.
> >
> > Please add any other topics, is also possible to discuss directly in
> > this thread.
> >
> > [1] https://doodle.com/poll/6giztg2vuw8wz6kf
> > [2] https://wiki.gentoo.org/wiki/Project:Kernel#Kernel_stabilization
> > [3] https://wiki.gentoo.org/wiki/Package_testing#Kernel
> >
> I'll add my general availability in a separate thread, as well as
> confirm via the Doodle - as updating nearly 200 slots is quite a slow
> process!!
>
> I'd like to discuss the possibility of harmonising the bumping and
> stabilisation process across the currently maintained source packages,
> so that, in principle, whilst they may not be fully supported via
> Security Team (we already have disclaimers for this), users choosing to
> opt for, eg. ck-sources, would know that because 90% of the code-base
> has been 'approved' via gentoo-sources (upstream + gentoo patches) that
> any discrepancy due to failure could be quickly narrowed down to the
> patchset, and the relevant maintainer can choose to pursue with their
> specific upstream. The extent to which this is feasible can be debated,
> but if we can establish a basic procedure that is, eg. automated,
> perhaps individual maintainers will want to 'pitch in' if the effort
> required is minimal enough.
> The objective would be to create a obvious 'choice' of "known-good"ish
> kernels that any user could choose from, whilst preserving maintainer
> workflow separation, etc.
>

not sure to have understand correctly.
you want to stabilize also ck-sources?
there is not only the new patchset but is also using different kernel
eclass function.
I think when we can do stabilization from the Gentoo kernel ci starting to
stabilize also other sources would be a path to consider.

thanks,
Alice

>

[-- Attachment #2: Type: text/html, Size: 4021 bytes --]

Re: [gentoo-kernel] Gentoo Kernel meeting

[kuzetsa]

On 07/05/2018 07:03 AM, Alice Ferrazzi wrote:
> Sent from my phone. Please excuse my brevity.
> 
> On Thu, 5 Jul 2018, 19:51 M. J. Everitt, <m.j.everitt@iee.org> wrote:
> 

{ ~pruned~ }

>> I'd like to discuss the possibility of harmonising the bumping and
>> stabilisation process across the currently maintained source packages,
>> so that, in principle, whilst they may not be fully supported via
>> Security Team (we already have disclaimers for this), users choosing to
>> opt for, eg. ck-sources, would know that because 90% of the code-base
>> has been 'approved' via gentoo-sources (upstream + gentoo patches) that
>> any discrepancy due to failure could be quickly narrowed down to the
>> patchset, and the relevant maintainer can choose to pursue with their
>> specific upstream. The extent to which this is feasible can be debated,
>> but if we can establish a basic procedure that is, eg. automated,
>> perhaps individual maintainers will want to 'pitch in' if the effort
>> required is minimal enough.
>> The objective would be to create a obvious 'choice' of "known-good"ish
>> kernels that any user could choose from, whilst preserving maintainer
>> workflow separation, etc.
>>
> 
> not sure to have understand correctly.
> you want to stabilize also ck-sources?
> there is not only the new patchset but is also using different kernel
> eclass function.
> I think when we can do stabilization from the Gentoo kernel ci starting to
> stabilize also other sources would be a path to consider.
> 
> thanks,
> Alice
> 


I'd prefer waiting until QA / CI is solid before any
discussion to stabilize sys-kernel/ck-sources. I'm not
opposed per-se, but there's only so much testing I can do
on my own (this is why I need to know the QA / CI tools
are working well for several months I think). If there's
sufficient testing (to know when things are stable) then
sure, I think it might be okay to try for in 1st or 2nd
quarter 2019.

3rd quarter 2018 I'm still "spread thin", and my
availability is limited this weekend. In the meantime I'll
do what I can to familiarize myself with lava. I'll be
using my own infrastructure for testing, and hope to have
some practical experience and ideas by the end of July.

-- kuza

Re: [gentoo-kernel] Gentoo Kernel meeting

[Richard Yao]

Even though I am more a kernel developer than a userlanf developer, I am not technically on the kernel team. I would be happy to attend the meeting though. I added my availability.

> On Jul 5, 2018, at 1:16 AM, Alice Ferrazzi <alicef@gentoo.org> wrote:
> 
> Hello everyone,
> 
> I would like to start the first Gentoo kernel meeting.
> Please choose the time of the meeting [1]
> If the time is not compatible we can also just discuss it by mail.
> 
> Please send any new agenda items as new threads to the gentoo-kernel list.
> 
> The current agenda is as follows.
> - Gentoo kernel ci
>    - Use Lava qemu for testing the kernel
>    - Add kselftest
>    - Start stabilizing with Gentoo kernel CI
>    - Add ck-sources to the qemu test
> - Stabilization
>    - Automatize the stabilization process
>    - keep up with upstream or use any other stabilization system
>        current stabilization system is defined here [2]
>        and here is the process to stabilize the kernel [3]
>        As now we are working to automatize the process.
> 
> Please add any other topics, is also possible to discuss directly in
> this thread.
> 
> [1] https://doodle.com/poll/6giztg2vuw8wz6kf
> [2] https://wiki.gentoo.org/wiki/Project:Kernel#Kernel_stabilization
> [3] https://wiki.gentoo.org/wiki/Package_testing#Kernel
> 
> 
> 
> -- 
> Thanks,
> Alice Ferrazzi
> 
> Gentoo Kernel Project Leader
> Gentoo Foundation Vice-Secretary
> Gentoo Google Summer of Code Administrator
> Mail: Alice Ferrazzi <alicef@gentoo.org>
> PGP: 2E4E 0856 461C 0585 1336 F496 5621 A6B2 8638 781A
> 

Re: [gentoo-kernel] Gentoo Kernel meeting

[Alice Ferrazzi]

Hello,

On Sat, Jul 7, 2018 at 10:14 AM, Richard Yao <ryao@gentoo.org> wrote:
> Even though I am more a kernel developer than a userlanf developer, I am not technically on the kernel team. I would be happy to attend the meeting though. I added my availability.

sure, feel free to join.

thanks,
Alice

-- 
Thanks,
Alice Ferrazzi

Gentoo Kernel Project Leader
Gentoo Foundation Vice-Secretary
Gentoo Google Summer of Code Administrator
Mail: Alice Ferrazzi <alicef@gentoo.org>
PGP: 2E4E 0856 461C 0585 1336 F496 5621 A6B2 8638 781A

[gentoo-kernel] Re: Gentoo Kernel meeting

[Alice Ferrazzi]

Hello everyone,

the first Gentoo kernel meeting will be held at July 20 Friday 11:00 UTC
in the #gentoo-kernel Freenode channel.
Agenda is here[0]
Feel free to add to it

[0] https://wiki.gentoo.org/wiki/Project:Kernel/meetings/2018_07_20

-- 
Thanks,
Alice Ferrazzi

Gentoo Kernel Project Leader
Gentoo Foundation Vice-Secretary
Gentoo Google Summer of Code Administrator
Mail: Alice Ferrazzi <alicef@gentoo.org>
PGP: 2E4E 0856 461C 0585 1336 F496 5621 A6B2 8638 781A

[gentoo-kernel] QA / CI improvement using stage3 images under qemu

[kuzetsa]

[-- Attachment #1.1: Type: text/plain, Size: 1229 bytes --]

On 07/05/2018 01:16 AM, Alice Ferrazzi wrote:
> Hello everyone,
> 
> I would like to start the first Gentoo kernel meeting.
> Please choose the time of the meeting [1]
> If the time is not compatible we can also just discuss it by mail.
> 
> Please send any new agenda items as new threads to the gentoo-kernel list.
>

{snip}

>
> Please add any other topics, is also possible to discuss directly in
> this thread.
> 
> 


There was some work done to set up the buildbot
for using stage4 "openstack" image which were
built by prometheanfire, I believe. At some point
there was breakage, and the workflow to produce
those images (iso) stopped working.

The new workflow, or a refresh of the old workflow
can be used to create ready-to-use stage4 images
which are in the qcow2 format, and bootable using
qemu (similar to earlier CI tester)

https://github.com/prometheanfire/gentoo-cloud-prep/issues/21

^ Among other things needing a refresh, 17.0 profiles
were not being used, so a few minor changes were needed
to bump. I talked with prometheanfire in the past 48
hours, and was told we're free to adapt and/or improve
the old tooling if it suits our needs for kernel testing.

-- kuza


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]