civilinfrastructureplatform:ciptestingboardatdesksingledevsetup
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
civilinfrastructureplatform:ciptestingboardatdesksingledevsetup [2018/04/27 14:25] rajmarshall better alternatives rather than assuming users want all 3 boards |
civilinfrastructureplatform:ciptestingboardatdesksingledevsetup [2018/05/09 14:03] rajmarshall better warning text for 2018.4 |
||
|---|---|---|---|
| Line 43: | Line 43: | ||
| ===== Configure the LAVA Health Check Jobs for your Devices ===== | ===== Configure the LAVA Health Check Jobs for your Devices ===== | ||
| - | 4. On your host machine, open a web browser and enter the following in the address box: | + | 4. // Note that (only) if you are using a recent provision of B@D from the git repos - and therefore LAVA v 2018.4 - you need to create health checks by copying the yaml to /etc/lava-server/dispatcher-config/health-checks/ - // |
| + | |||
| + | vagrant@guest:~$ sudo cp /vagrant/tests/qemu-health-check.yaml /etc/lava-server/dispatcher-config/health-checks/qemu.yaml | ||
| + | # if using a Beaglebone Black board | ||
| + | vagrant@guest:~$ sudo cp /vagrant/tests/bbb_debian_local.yaml /etc/lava-server/dispatcher-config/health-checks/beaglebone-black.yaml | ||
| + | # if using a Renesas iwg20m board | ||
| + | vagrant@guest:~$ sudo cp /vagrant/tests/iwg20m-test-ramdisk.yaml /etc/lava-server/dispatcher-config/health-checks/renesas-iwg20m.yaml | ||
| + | |||
| + | |||
| + | Once the files have been moved the health checks will automatically run and in all but the case of QEMU fail as other configuration is still necessary. You can then skip to the end of this section. | ||
| + | |||
| + | 5. On your host machine, open a web browser and enter the following in the address box: | ||
| ''<nowiki>http://localhost:8080</nowiki>'' | ''<nowiki>http://localhost:8080</nowiki>'' | ||
| - | 5. The LAVA Home Page is displayed in your web browser. Log in to the web server as the superuser: | + | 6. The LAVA Home Page is displayed in your web browser. Log in to the web server as the superuser: |
| * Click the login link in the upper right-hand corner of the Lava Server website | * Click the login link in the upper right-hand corner of the Lava Server website | ||
| Line 55: | Line 66: | ||
| * Enter the password: **mylava1234** | * Enter the password: **mylava1234** | ||
| - | 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. From the LAVA homepage, click on your username in the upper right-hand corner of the page. This displays a menu of actions. |
| * Click on Administration | * Click on Administration | ||
| Line 61: | Line 72: | ||
| * Scroll down to section labelled "LAVA_SCHEDULER_APP" and click on "Device types" | * Scroll down to section labelled "LAVA_SCHEDULER_APP" and click on "Device types" | ||
| - | 7. Click on the **qemu** device type | + | 8. 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. 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 | + | 10. 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. // | // Note: Once the health-check job is saved to the device type, the job is automatically started by LAVA. // | ||
| - | 10. If you have a Beaglebone Black, click on the **bbb01** device type (otherwise move to section 13). | + | 11. If you have a Beaglebone Black, click on the **bbb01** device type (otherwise move to section 13). |
| - | 11. Copy and paste the contents of the file ''/vagrant/tests/bbb_debian_local.yaml'' into the Health check job textbox. | + | 12. Copy and paste the contents of the file ''/vagrant/tests/bbb_debian_local.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, | + | 13. 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.// | 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. If you have a Renesas IWG20M board, click on the **iwg20m01** device type otherwise move to the end of this section. | + | 14. If you have a Renesas IWG20M board, click on the **iwg20m01** device type otherwise move to the end of this section. |
| - | 14. Copy and paste the contents of the file ''/vagrant/tests/iwg20m-test-ramdisk.yaml'' into the Health check job textbox. | + | 15. Copy and paste the contents of the file ''/vagrant/tests/iwg20m-test-ramdisk.yaml'' into the Health check job textbox. |
| - | 15. Click on the **Save** button in the lower right-hand corner of the page. //Note that this health check, | + | 16. 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 IWG20M has not yet been fully set up.// | which will now run automatically, will fail - i.e. it will be marked as incomplete - because the IWG20M has not yet been fully set up.// | ||
civilinfrastructureplatform/ciptestingboardatdesksingledevsetup.txt · Last modified: 2018/09/21 10:49 by rajmarshall
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
