This set of instructions assumes you have already deployed B@D. If that is not the case please go back to the B@D Virtual Machine Deployment wiki page.
This wiki page will guide you through the configuration process of the Virtual Machine (VM) that contains Kernel CI and LAVA. Kernel CI is used to build, boot and report results whereas LAVA is used to offer a robust automated testing language, a testing engine and the reporting of results.
1. Connect to the Virtual Machine
user@host:board-at-desk-single-dev$ vagrant ssh
Linux jessie 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2 (2017-04-30) x86_64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. You have new mail. Last login: Tue May 16 08:21:43 2017 from 10.0.2.2 vagrant@jessie:~$
2. If you downloaded and imported the
cip_board_at_desk_v0.9.1.box pre-provisioned VM box, please go to the Beaglebone Black Setup & Configuration wiki page to setup the Beaglebone Black for use with the B@D Virtual Machine since the rest of this page has already been done for you!
If you are building the VM from scratch using Vagrant, please continue to the next step.
3. Set up a Superuser for Lava Job maintenance.
vagrant@jessie:~$ sudo lava-server manage createsuperuser --username lavauser --firstname.lastname@example.org
Password (again): mylava1234
Superuser created successfully.
Note: Replace <lavauser> with your desired username and replace email@example.com with that user’s email address. Select a password and enter it twice.
4. On your host machine, open a web browser and enter the following in the address box:
5. The LAVA Home Page is displayed in your web browser. Log in to the web server as the superuser:
6. From the LAVA homepage, click on your username in the upper right-hand corner of the page. This displays a menu of actions.
7. Click on the qemu device type
8. Copy and paste the contents of the file
/vagrant/tests/qemu-health-check.yaml into the Health check job textbox. Unless you are using QEMU tests regularly we suggest that you change the pull down 'Initiate health checks by hours or by jobs.' to use 'jobs', as the health check incurs a heavy system load as well as using lots of disk space.
9. Click on the Save button in the lower right-hand corner of the page
Note: Once the health-check job is saved to the device type, the job is automatically started by LAVA.
10. Click on the bbb01 device type
11. Copy and paste the contents of the file
/vagrant/tests/bbb_debian_ramdisk_test.yaml into the Health check job textbox.
12. Click on the Save button in the lower right-hand corner of the page. Note that this health check, which will now run automatically, will fail - i.e. it will be marked as incomplete - because the Beaglebone Black has not yet been fully set up.
13. Once the health checks have completed we recommend a reboot of the vagrant instance to free resources used in the provision.
user@host:$ vagrant halt user@host:$ vagrant up
14. Next, go to the Beaglebone Black Setup & Configuration wiki page to setup the Beaglebone Black for use with the B@D Virtual Machine.
Back to the B@D Virtual Machine Deployment wiki page