This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
civilinfrastructureplatform:ciptestingboardatdesksingledevsetup [2018/06/11 10:20] rajmarshall [Vagrant Setup] missing open bracket |
civilinfrastructureplatform:ciptestingboardatdesksingledevsetup [2018/09/21 10:49] rajmarshall [Setting up notifications] add note about freenode and IRC notifications |
||
---|---|---|---|
Line 43: | Line 43: | ||
===== Configure the LAVA Health Check Jobs for your Devices ===== | ===== Configure the LAVA Health Check Jobs for your Devices ===== | ||
- | 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/ - // | + | 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 these yaml files 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 | vagrant@guest:~$ sudo cp /vagrant/tests/qemu-health-check.yaml /etc/lava-server/dispatcher-config/health-checks/qemu.yaml | ||
Line 52: | Line 52: | ||
| | ||
- | 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. | + | 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 page - [[ciptestingboardatdesksingledevsetup#setting-up-notifications|Setting up Notifications]] If you are using an earlier version of LAVA than 2018.4 then continue with point 5. |
| | ||
5. On your host machine, open a web browser and enter the following in the address box: | 5. On your host machine, open a web browser and enter the following in the address box: | ||
Line 80: | Line 80: | ||
// 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. // | ||
- | 11. 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 14). |
12. 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. | ||
Line 143: | Line 143: | ||
email: desiredRecipientEmailAddress | email: desiredRecipientEmailAddress | ||
- | If you don't wish to be notified via IRC then just remove that first //to:// section - but otherwise change the yourIRCHandle appropriately! | + | If you don't wish to be notified via IRC then just remove that first //to:// section - but otherwise change the yourIRCHandle appropriately! Note that, at the moment due to spam problems, IRC pinging on Freenode will not work. |
6. Note that the current version of LAVA used in B@D also supports ''finished'' as a status, so that an email will be received whatever the status of the health check. To be notified about failures change complete to incomplete. See [[http://localhost:8080/static/docs/v2/user-notifications.html|Help in B@D's VM]] for further information - for this link to work the VM needs to be running. | 6. Note that the current version of LAVA used in B@D also supports ''finished'' as a status, so that an email will be received whatever the status of the health check. To be notified about failures change complete to incomplete. See [[http://localhost:8080/static/docs/v2/user-notifications.html|Help in B@D's VM]] for further information - for this link to work the VM needs to be running. |