[Fuego] [PATCH 09/10] kernel_build: implement kernel deployment

Daniel Sangorrin daniel.sangorrin at toshiba.co.jp
Wed Mar 28 00:08:52 UTC 2018



> -----Original Message-----
> From: Tim.Bird at sony.com [mailto:Tim.Bird at sony.com]
> Sent: Wednesday, March 28, 2018 6:46 AM
> To: daniel.sangorrin at toshiba.co.jp; fuego at lists.linuxfoundation.org
> Subject: RE: [Fuego] [PATCH 09/10] kernel_build: implement kernel deployment
> 
> 
> 
> > -----Original Message-----
> > From: fuego-bounces at lists.linuxfoundation.org [mailto:fuego-
> > bounces at lists.linuxfoundation.org] On Behalf Of Daniel Sangorrin
> > Sent: Tuesday, March 27, 2018 1:53 AM
> > To: fuego at lists.linuxfoundation.org
> > Subject: [Fuego] [PATCH 09/10] kernel_build: implement kernel deployment
> >
> > This does the next step after building the kernel, deploying
> > it to a folder (eg tftp server). By default, it uses the
> > LOGDIR.
> >
> > FIXTHIS: discuss about whether to export modules and dtbs
> > as well.
> >
> > Signed-off-by: Daniel Sangorrin <daniel.sangorrin at toshiba.co.jp>
> > ---
> >  engine/tests/Functional.kernel_build/fuego_test.sh | 10 +++++++---
> >  1 file changed, 7 insertions(+), 3 deletions(-)
> >
> > diff --git a/engine/tests/Functional.kernel_build/fuego_test.sh
> > b/engine/tests/Functional.kernel_build/fuego_test.sh
> > index c914c7a..0a04915 100755
> > --- a/engine/tests/Functional.kernel_build/fuego_test.sh
> > +++ b/engine/tests/Functional.kernel_build/fuego_test.sh
> > @@ -57,9 +57,13 @@ function test_run {
> >      # cat on target populates the testlog with build.log
> >      report "cat $WORKSPACE/$JOB_BUILD_DIR/build.log"
> >
> > -function test_deploy {
> > -    echo "Deploying kernel"
> > -    # FIXTHIS: copy to tftp folder for lava etc..
> > +    if [ -z "$FUNCTIONAL_KERNEL_DEPLOY" ]; then
> > +        FUNCTIONAL_KERNEL_DEPLOY="$LOGDIR"
> > +    fi
> > +
> > +    # FIXTHIS: output the modules and dtbs as well
> > +    echo "Deploying kernel to $FUNCTIONAL_KERNEL_DEPLOY"
> > +    cp
> > $WORKSPACE/$JOB_BUILD_DIR/arch/$FUNCTIONAL_KERNEL_BUILD_ARCH/
> > boot/*Image $FUNCTIONAL_KERNEL_DEPLOY
> 
> I reserve the right to come back and adjust this step when we add some
> generalized board provisioning in the future.  For now, looks good.

Yes, I am thinking about providing a ktest.pl like approach where we can
specify in the spec the board to install the kernel. Then docker would ssh into
the board, install the kernel/modules and reboot. The current approach
is passive. We just put the file in the tftp folder and we assume that
the board will be powered up and provisioned with the kernel in the tftp folder
(e.g.: using u-boot's tftpboot command).

Thanks,
Daniel




More information about the Fuego mailing list