Open Stack

Yes, I can create both jobs to keep testing what we consider experimental. Today experimental mean virtiofs kernel. I can rename it to be virtiofs experimental. And move that version freely even for more recent releases as will not break anything we depend on.  Sounds good ?

Experimental -> virtifos-experimental
-
Carlos

On 06/10/20 3:46, "Fabiano Fidêncio" <fidencio at redhat.com> wrote:

    Archana,

    [...]

    > In addition, we are using a 5.6 kernel with Dax patches by default for virtiofs for both qemu-virtiofs and cloud-hypervisor. I propose we instead switch to the LTS 5.4 upstream kernel that has all the bits for virtiofs except Dax. If some user wants to use dax, they can switch to the experimental 5.6 kernel instead.

    I agree with the suggestion. However, I'd like to know whether it'd be
    possible to have a jenkins job, running weekly or so, with a 5.6
    kernel with all the new bits enabled there, as with this we could:
    1. Ensure we don't break anything on the Kata side related to DAX;
    2. Ensure we do at least some test to early report issues to virtio-fs folks;

    Is this a reasonable and feasible approach?

    [...]

    Best Regards,
    -- 
    Fabiano Fidêncio


    _______________________________________________
    kata-dev mailing list
    kata-dev at lists.katacontainers.io
    http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev