On Fri, Aug 18, 2017 at 10:45 AM, Jan Stancek <jstan...@redhat.com> wrote: > Hi, > > Jeff&I arrived to an idea how (maybe) we could start playing with > booting custom kernel/initrd today: > > We create a custom distro, for example we copy Fedora26 with different > name: "SKT26", and we place it somewhere where we have RW access to it. > Then we import it to Beaker manually. > > If my understanding of Beaker is correct, we can freely replace > kernel/initrd in our distro and Beaker will always copy latest > files to tftp when we run a job. > > Obviously the problem is concurrency and reproducibility of jobs, > but it would a quick way to allow us experimenting with custom > kernels/initrds today. > > Any comments/thoughts?
Yes I think this should work and would be a good workaround for the short term. We would just need to make sure that the new fake distro tree is not picked up by beaker-pxemenu to be included in the PXELINUX menu. If it is included in the menu, the kernel+initrd will be cached on the LC and beaker-provision will just re-use the cached images instead of re-downloading them each time. Excerpts from Hannes Frederic Sowa's message of 2017-08-19 18:49 -04:00: > What about synchronizing /lib/modules directory with initrd + vmlinuz? > In a lot of cases we depend on dynamically loaded modules even during > testing phase. Is this also possible with this schema? > > Thanks for looking into this, > Hannes This is a good point. I guess it is not enough to just replace pxeboot/vmlinuz and pxeboot/initrd.img, but also the kernel-related packages (and the Anaconda stage2.img as well?) -- almost an entire new compose in place each time. Which begs the question... if you are doing an entirely new compose each time, whys not just register each one in Beaker separately? Let's continue the discussion on the devel list (cc'ed) so others can see. Coincidentally Anwesha has just started working on proper support for "user-supplied distro trees" in bug 911515 so we should see some progress on that soon. -- Dan Callaghan <dcall...@redhat.com> Senior Software Engineer, Products & Technologies Operations Red Hat
signature.asc
Description: PGP signature
_______________________________________________ Beaker-devel mailing list -- beaker-devel@lists.fedorahosted.org To unsubscribe send an email to beaker-devel-le...@lists.fedorahosted.org
