----- Original Message -----
> Excerpts from Jan Stancek's message of 2017-08-03 02:54 -04:00:
> > ----- Original Message -----
> > > https://bugzilla.redhat.com/show_bug.cgi?id=911515
> >
> > Can you elaborate on what would be required here? I'm currently imagining
> > this as "wget" that stores vmlinuz+initrd to tftpboot directory.
> >
> > [...]
> > Also I think it still makes sense to keep <distro> tag in jobs. Your
> > kernel/initrd is going to be based on existing distros, so it'd be nice
> > if beaker gave you machine that supports it, <distro> is useful for
> > excluded families. And there might be also specific options that need
> > to be passed on kernel command line for things to work.
>
> Right... So that is actually the hard part of bug 911515. Deciding what
> the new job XML bits -- and corresponding UI and database schema --
> should look like for this case. And then wiring it all up internally on
> the server side, where it is currently assuming it is working with rows
> from the distro_tree table.
I see. Bug 911515 appears to be larger in scope. It's not just about
using custom kernel+initrd but also about dealing with distro which is
not imported.
I was more in mindset of using existing imported distro and only
overriding kernel and initrd:
<recipe>
<distroRequires>
</distroRequires>
<netboot>
<kernel></kernel>
<initrd></initrd>
</netboot>
</recipe>
Regards,
Jan
_______________________________________________
Beaker-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
