Browse Source

Add more slides

Signed-off-by: Florent Jacquet <florent.jacquet@free-electrons.com>
master
Skia 2 years ago
parent
commit
8b64f64287
4 changed files with 49 additions and 28 deletions
  1. +1
    -1
      Makefile
  2. BIN
      slides.pdf
  3. +48
    -7
      slides.tex
  4. +0
    -20
      slides.vrb

+ 1
- 1
Makefile View File

@@ -12,7 +12,7 @@ all: $(TARGET) clean
$(LATEX) --shell-escape $<

clean:
rm -f *.log *.nav *.snm *.aux *.out *.toc *.pyg
rm -f *.log *.nav *.snm *.aux *.out *.toc *.pyg *.vrb

distclean: clean
rm -f $(TARGET)

BIN
slides.pdf View File


+ 48
- 7
slides.tex View File

@@ -47,6 +47,7 @@

\begin{frame}[fragile]\frametitle{LAVA}
\begin{itemize}
\item \small{\url{https://www.linaro.org/initiatives/lava/}}
\item Runs jobs on devices.
\item Runs KernelCI jobs: only boot.
\item Provides an API to do many thing. Among them: sending jobs and
@@ -56,18 +57,23 @@

\begin{frame}[fragile]{Buildroot}
\begin{itemize}
\item \small{\url{https://github.com/free-electrons/buildroot-ci}}
\item Used to make only rootfs.
\item Is configured to provided the needed tools such as iperf,
bonnie++, etc...
\item Builds fresh rootfs every night for all the needed architectures:
ARMv4, ARMv5, ARMv7, ARMv8.
\item Stores them in a LAVA-accessible folder.
\item Stores them in a LAVA-accessible folder in the farm.
\end{itemize}
\end{frame}

\begin{frame}[fragile]{The custom test tool}
\begin{frame}[fragile]\frametitle{The custom test tool}
\begin{itemize}
\item Has jobs templates and knows how to send them.
\item \small{\url{https://github.com/free-electrons/custom_tests_tool}}
\item Has job templates and knows how to send them.
\item Has a list of devices in the \verb$boards.py$ file containing the
non-changing data
\item Can fetch latest builds URLs from KernelCI.
\item Can upload custom artifacts useable for tests.
\item Can ask LAVA to notify given emails addresses when the job ends.
\item Needs an access to the LAVA API, an SSH access to the LAVA server
@@ -79,9 +85,9 @@

\begin{frame}[fragile]{The test suite}
\begin{itemize}
\item \small{\url{https://github.com/free-electrons/test_suite}}
\item Is a bunch of shell scripts that will be run on the devices.
\item Also needs YAML files to interface with LAVA.
\item Leaves in one of our git repo on Github \footnote{\url{https://github.com/free-electrons/test_suite}}.
\end{itemize}
\end{frame}

@@ -146,18 +152,53 @@
\item After the board is booted:
\begin{itemize}
\item Runs each test described in the job definition.
\item For each call to the `lava-test-case` function, creates
the results objects.
\item For each call to the `lava-test-case` command, creates
the corresponding results objects. It's thus important to
call it at least once, or you'll have a job with no results,
apart from the log.
\end{itemize}
\end{itemize}
\end{frame}

\begin{frame}[fragile]\frametitle{Collecting the results}
\begin{itemize}
\item LAVA's notification system can send emails if asked. That's the
way results are reported when sending on demand jobs.
\item A daily cron job fetchs the results and aggregates them in an
personalized email to each address in the \verb$boards.py$ file of
the custom test tool.
\item A dashboard is hourly refreshed presenting the devices and the
tests in a table with colors and links to the jobs
\footnote{\url{http://farm:5000}}. \\
The code lives in the custom test tool repo, under the
\verb$./dashboard$ folder.
\end{itemize}
\end{frame}

\begin{frame}[fragile]{Sum up, improving, contributing...}
The READMEs should already explain much of what you'll need.
\begin{itemize}
\item To add more tools to the rootfs: \\
\small{\url{https://github.com/free-electrons/buildroot-ci}}
\item To add more boards once they are in LAVA, or add more tests to a
board, or to modify the job templates, or to improve the dashboard: \\
\small{\url{https://github.com/free-electrons/custom_tests_tool}}
\item To add more tests in the test suite: \\
\small{\url{https://github.com/free-electrons/test_suite}}
\end{itemize}
\end{frame}

\begin{frame}{Questions}

\begin{frame}[fragile]\frametitle{Questions}
\begin{center}
\alert{Question?}
\end{center}
\end{frame}

\begin{frame}[fragile]\frametitle{Demo time!}
\begin{center}
\alert{Demo time!}
\end{center}
\end{frame}

\end{document}

+ 0
- 20
slides.vrb View File

@@ -1,20 +0,0 @@
\frametitle{How do LAVA runs test?}
\begin{itemize}
\item Before bringing up the board, LAVA:
\begin{itemize}
\item Fetches the artifacts.
\item Applies the needed modifications (append DTB, mkimage,
modules, ...)
\item Also downloads the test suite and puts it in the rootfs.
This moment also makes some magic to provide some helpers
useable in the test scripts.
\item Finally connects itself and powers up the board.
\end{itemize}
\item After the board is booted:
\begin{itemize}
\item Runs each test described in the job definition.
\item For each call to the `lava-test-case` function, creates
the results objects.
\end{itemize}
\end{itemize}


Loading…
Cancel
Save